Setting up the Teams bot

The Teams bot lets people in Microsoft Teams use the classic agent commands and, once you turn it on, talk to Qubit. It is also how Qubit posts Q-Notice cards and routines into Teams. QuantumOps provides the bot registration for you. Your part is to name the bot, grant admin consent in your Microsoft 365 directory, and install the app package in Teams.

Before you start:

• You need the Administrator or Q-Director Configuration role to use the Messaging tab. Turning Qubit on, and the Grant admin consent (Entra) button on the Channel Assistant page, need the Administrator role. With only the Q-Director Configuration role, use Open Consent URL on the Messaging tab.
• A Microsoft 365 administrator must grant consent. That can be you or someone you ask.
• Your Microsoft 365 setup must allow people to upload custom apps in Teams.
• On Configuration → Q-Director Config → Messaging, choose Microsoft Teams under Select Communication Platform and select Save Platform Selection. See Q-Director: Slack, Teams and agent mapping.

Why consent comes first

The bot is registered once by QuantumOps, and your Microsoft 365 directory has to authorise it. Uploading the app package alone does not create that authorisation. Consent also lets QuantumOps read your directory, which fills the Teams user list used for agent mapping and lets people be linked to Qubit automatically. So grant consent before you upload the package.

Name the bot and add an alert webhook

On the Messaging tab with Microsoft Teams selected, save a Bot Name and an Alert Webhook under Your Configuration, then select Save Configuration. The fields are described in Q-Director: Slack, Teams and agent mapping.

The badges at the top of Microsoft Teams Setup show your progress:

Grant admin consent

1. In Deploy Bot to Teams, find step 1, Grant Admin Consent FIRST, and select Open Consent URL. You can also use Grant admin consent (Entra) on the Teams card of the Channel Assistant page.
2. Microsoft's sign-in page opens in a new tab. A Microsoft 365 administrator signs in, reviews the permissions and accepts them.
3. Microsoft returns you to the Messaging tab. A message confirms that admin consent was granted, and the Admin Consent badge is ticked.

Open Consent URL and Download are greyed out until you have saved Microsoft Teams as the platform. Select it under Select Communication Platform and select Save Platform Selection. If they stay greyed out, contact support.

Things to know:

• The consent link works for 20 minutes and only once. If it expires or has been used, the tab shows "The consent link is invalid, expired, or has already been used. Start again from Settings." Select Open Consent URL again.
• Before it records consent, QuantumOps checks that the app can sign in to your directory. If it cannot, you see "Consent completed but the app could not sign in to tenant", followed by the reason.
• A failure shows as "Admin consent failed:" followed by Microsoft's reason. Closing the consent page without accepting records nothing.
• If the bot has a name but consent is missing, a Re-Authorization Required banner asks you to grant consent so QuantumOps can connect to your user directory.

Download the app package and upload it to Teams

1. In Deploy Bot to Teams, step 2 is Download ZIP. Select Download. The file is a ZIP whose name starts with TeamsApp_ and your bot name.
2. In Teams, follow step 3, Upload to Teams: Profile > Manage apps > Upload custom app > Select ZIP.

What the package calls the bot

Look for these names when you upload it:

The bot works in personal chats and in teams. Its command menu lists help, online, offline, lunch, brb, back and status. The package also asks Teams for permission to read channel messages and members of a team and to send activity notifications, which you approve when you add the app to a team.

Add the bot to a channel and test it

Step 4 is Add to Channel & Test: in the channel choose + > search for the bot > Add. Then mention the bot and type help, for example @qops help.

• While Qubit is off for Teams, the bot answers with the classic commands.
• Once Qubit is on, the bot answers with Qubit's own help.

The bot answers only messages addressed to it: any message in a personal chat, a mention of the bot, or a message that names it, such as @qops. Other channel messages are ignored.

What happens when the bot is installed

When someone installs the bot, and only while Qubit is on for Teams, it posts a welcome card:

Hi, I'm Bot Name. Mention me in a channel or message me directly and ask anything about your tickets, clients and tools. Type link to connect your QuantumOps account, model to pick a model, routine add … to schedule posts, help for everything else.

With Qubit off, the bot posts no welcome card.

Qubit can post routines, Q-Notice cards and direct messages only into chats where the bot was installed or where it has been mentioned. A channel that nobody has mentioned the bot in cannot be a destination yet, so mention the bot once in any channel you want to use. See Channel Assistant settings, Routines and How Q-Notices are delivered.

Turn on Qubit in Teams

Installing the bot does not switch Qubit on. Open Configuration → Channel Assistant, tick the Teams box named "Enable the Qubit assistant in Teams" and save it. Only an Administrator can do this. Before you do, tell your team that the classic commands in Agent status commands stop working at that point, because every message then goes to Qubit.

When something does not work

Related pages

• Channel Assistant settings: turn Qubit on for Teams and see the messaging endpoint.
• Q-Director: Slack, Teams and agent mapping: the Messaging tab, the bot name and the agent mapping.
• Agent status commands: the classic commands the bot answers while Qubit is off.
• Qubit in Slack and Teams: how people ask Qubit once it is on.