Microsoft Teams

Registering an Azure Bot, pointing Teams at this workspace, and where ticket activity is posted.

Microsoft Teams is a two-way channel. A Teams message to the bot becomes a ticket, and your reply is posted straight back into the conversation. Everything Teams needs is on one page, Channels, Teams: the Azure registration at the top, the activity-feed destination underneath. Editing either needs admin.

One page, not two

/integrations/teams redirects to /channels/teams, for the same reason Slack's does. The credential and the routing changed for different reasons but are set up in one sitting, so they share a screen.

Registering the bot

Teams is not an OAuth round trip. You create an Azure Bot yourself and paste its credentials here. The page carries the whole recipe, because a bot pointed at the wrong messaging endpoint, or missing the Teams channel, fails in a way you cannot diagnose from this side.

Create a resource of type Azure Bot in the Azure portal. Choose Multi Tenant unless your organisation requires single-tenant.

Copy the Microsoft App ID from the bot's Configuration blade and paste it into App ID here. It is the identity every message is verified against.

Create a client secret on the app registration and copy its value immediately, because Azure shows it once. Paste it into App password.

Set the bot's Messaging endpoint to the address shown on this page. Copy it with the button rather than by hand.

Add the Microsoft Teams channel on the bot's Channels blade. Without it the bot can be messaged nowhere.

Install the bot in Teams using an app manifest that references this App ID with the team, group chat and personal scopes. The page will build a manifest.json for you to download.

The app password is required every time you save, including on an update: the runtime keeps the stored secret only if it is re-sent. You can also record the Azure AD tenant id and a bot name, and pause the connection without disconnecting it.

Activity feed

Below the registration you choose which Teams channel receives the live ticket activity feed, and which events are posted to it. This is a routing decision about a connection that already exists, so it appears only once Teams is connected.

Registering the bot

Activity feed

Next

On this page