Microsoft Teams messaging channel
Use this guide to deploy an agent to Microsoft Teams.
Before you start
Make sure you have:
- A Microsoft 365 tenant with Teams access
- An Azure app registration for your bot
- A live agent with an AI model connected
- Access to Agents -> your agent -> Deployment
Configure Microsoft Teams in Budibase
- Open your agent in Agents
- Go to Deployment
- In Messaging channels, click Manage for Microsoft Teams
- Enter:
- App ID (client ID)
- Client secret (value)
- Directory (tenant) ID (Azure AD tenant ID)
- Idle timeout (minutes) (optional)
- Click Save channel
- Copy the generated Messaging endpoint URL
Configure your Teams bot endpoint
In your Azure bot configuration, set the bot messaging endpoint to the Budibase Messaging endpoint URL.
Use a single-tenant setup that matches your tenant ID.
Enable and verify
- In Budibase Deployment, toggle Microsoft Teams to Enabled
- Open Teams and message the bot
- Run
linkor/link, then complete the Budibase account linking flow - Test commands:
ask <message>to continue the current conversationnew <message>to start a new conversation
Plain text messages are treated as ask.
If you send a normal message before linking, Budibase sends a private link prompt.
Troubleshooting
Not configuredin Budibase: confirm App ID, Client secret, and Tenant ID are saved.- Teams cannot deliver messages: verify the bot messaging endpoint matches the Budibase URL exactly.
- Authentication failures from Teams: check bot credentials and tenant alignment.
- Teams prompts to link before answering: run
linkor/linkand complete the account link handoff. - Webhook route errors: use the exact Budibase-generated endpoint URL from Deployment.
Related guides
Updated 6 days ago