Microsoft Teams
Connect an agent to Microsoft Teams so users chat with it like any other person. Teams is connected per agent in the Channels tab of the agent builder, backed by an Azure Bot resource.
Prerequisites
- A saved agent (the Channels tab is locked until the agent is saved).
- An Azure Bot resource created in the Azure portal.
- Its Microsoft App ID and App Password (client secret).
What you’ll need from Azure
| Field | Where to find it | Required |
|---|---|---|
| Microsoft App ID | Azure Bot resource → Configuration | Yes |
| App Password (client secret) | Azure → App registration → Certificates & secrets | Yes |
| Tenant ID | Azure AD overview — single-tenant bots only; leave blank for multi-tenant | No |
| Bot Display Name | Any label | No |
How to connect
- Create an Azure BotIn the Azure portal, create an Azure Bot resource and a client secret for it.
- Enter credentials in TeamMateIn the agent’s Channels tab, open Microsoft Teams → Configure, and paste the App ID and App Password.
- Set the messaging endpointCopy TeamMate’s Messaging Endpoint and paste it into the Azure Bot’s Messaging endpoint field. Enable the Microsoft Teams channel on that bot.
- Verify the credentialsClick Test connection. TeamMate acquires a Bot Framework token to confirm the App ID and App Password are valid (no message is sent).
- Download the Teams app packageSave the integration first, then download the .zip app package.
- Install the appIn Teams, go to Apps → Manage your apps → Upload an app for a single user, or hand the .zip to a Teams admin to publish to your tenant’s app catalog (org-wide install).
The Messaging Endpoint is https://tmmate.ai/api/webhook/teams/<agentId>.
What the agent can do
- Receive and reply to Teams direct messages.
- Appear in each user’s chat list and search once installed.
Linking Teams users to members
So the agent recognizes who is messaging, a workspace member’s Microsoft AAD Object ID can be linked to their account. See Linked accounts.
Troubleshooting
- Test connection fails. Re-check the App ID and App Password; a single-tenant bot also needs the correct Tenant ID.
- “Save the integration first” when downloading the package. The app package is built from a saved integration — save, then download.
- No replies in Teams. Confirm the messaging endpoint is set on the Azure Bot and the Microsoft Teams channel is enabled there.