Configure VirtuBot for customer organizations

Use Account > VirtuBot to enable VirtuBot for the selected package and manage its Microsoft Teams app options for each customer organization in that package.

Before you begin

• Select the account and package whose settings you want to change.
• Confirm that the customer organization has a working Microsoft 365 connection.
• Use an MSPControl account with access to the VirtuBot settings page.
• Review tenant-consent and Teams-app changes before enabling them for all users.

Review organization status

When Enable VirtuBot Service is selected, MSPControl lists the organizations available to the selected account. Each organization shows:

• Is Bot Installed — whether MSPControl detects the Teams app for that organization.
• Installed Version — the detected installed app version.
• Local Version — the app version available from the current MSPControl installation.
• Need Update — whether the installed and local versions differ.

These values are status indicators. This page does not provide a separate update action.

Configure Teams deployment

For an organization where the bot is already installed, you can configure:

• Install VirtuBot for All Users — when changed from off to on and saved, MSPControl starts the organization-wide Teams app installation workflow for existing users.
• Consent VirtuBot App for All Users — when changed from off to on and saved, MSPControl starts the organization-wide consent workflow.
• Install VirtuBot for New Users — saves the preference used when MSPControl later provisions or enables Microsoft Teams for a user.

Select Save Changes after reviewing every organization shown on the page.

Turning an option off is not an uninstall

The current settings workflow persists the new option values, but the reviewed implementation does not run an organization-wide uninstall or consent-revocation operation when one of these options is turned off. Verify the tenant directly before assuming an existing Teams app installation or consent grant has been removed.

Understand the service switch

Enable VirtuBot Service is stored at the selected package level. Turning it off hides the organization settings on this page and disables the package setting. It does not, by itself, prove that an already-installed Teams app was uninstalled or that previously granted consent was revoked.

Troubleshooting

• If no organizations appear, verify the selected account, package, and organization assignments.
• If an organization does not show the expected installation status, verify its Microsoft 365 connection and inspect the tenant’s Teams app state.
• If a version update is indicated, use the supported VirtuBot deployment process for the current MSPControl release; this page only reports the version comparison.
• If a bulk install or consent operation fails for some users, review the MSPControl task log and the affected Microsoft 365 user records.

Related configuration

• Use VirtuBot Policies to configure ticket-processing and integration behavior.
• Use Errors and Agent Models to configure completion and embedding endpoints and error notifications.

MCP Servers policy

Settings > Policies > VirtuBot > MCP Servers registers the Model Context Protocol servers VirtuBot may call. Each entry defines one server available to the assistant.

Turn the policy on with Enabled, then add the required servers.

Field	Meaning
Name	Display label for the server
Transport	How VirtuBot connects to it
Endpoint (HTTP)	Server address
Agents	Comma-separated agents that may use it, such as conversational, background, or security
Service API Key	Credential VirtuBot presents to the server
Allowed Tools	Comma-separated tool allow-list
Read-Only Tools	Tools exposed without write access
Enabled	Whether the server entry is active
Per-User Identity	Call the server as the signed-in user instead of the service identity
All Tools Read-Only	Force every exposed tool into read-only mode

Blank Agents and Allowed Tools are not restrictions

An empty Agents or Allowed Tools value means no restriction for that field. Define both fields explicitly when a server should be limited to selected agents or tools.

Save the policy after editing the list

Adding or editing an entry changes the list shown in the browser. Select Save Changes at the bottom of the policy page to persist those changes.

Prefer Per-User Identity when the target server supports user identity and per-user authorization. Otherwise, requests use the configured service identity and the downstream audit trail may not distinguish individual technicians.