Skip to main content
Microsoft Teams sends your bot an activity for every message, mention, conversation update and card action. Point your bot’s messaging endpoint at Nango and Nango verifies each activity, routes it to the right connection and forwards it to your app. This page covers both the Microsoft Teams Bot and Microsoft Teams integrations. They route webhooks the same way.

​
How it works

  1. Teams sends the activity to your bot’s messaging endpoint, which is your Nango webhook URL, through the Bot Framework connector.
  2. Nango verifies the Bot Framework token in the Authorization header. The token must be signed by Microsoft, issued by https://api.botframework.com, issued to your bot’s Microsoft App ID, and match the activity’s serviceUrl.
  3. Nango routes the activity to the connection whose tenantId matches the activity’s channelData.tenant.id.
Nango checks the token’s audience against the client ID of your Nango integration. Your integration’s client ID must be your bot’s Microsoft App ID. With the Microsoft Teams integration, that means the bot has to use the same Microsoft Entra app as the integration. If it uses a different app, Nango rejects every activity.

​
Setup

​
1. Get your Nango webhook URL

In the Nango dashboard, open your Microsoft Teams Bot or Microsoft Teams integration and copy the Webhook URL.

​
2. Set it as the bot’s messaging endpoint

  1. In the Azure portal, open your Azure Bot resource.
  2. Go to Settings > Configuration.
  3. Paste your Nango webhook URL in Messaging endpoint and select Apply.

​
3. Check the client ID

On the same Configuration page, compare the Microsoft App ID with the client ID of your Nango integration. They must be the same value. See How to register your own Microsoft Teams Bot.

​
4. Send a test message

Message the bot in Teams, then open the Logs tab in Nango. The activity shows up there once something consumes it, either webhook forwarding or a sync subscribed to its type (see Handle the webhook). Nango rejects an activity that fails verification with a 401, so it never reaches your app or Logs. If activities don’t show up, check the client ID first (step 3).

​
Handle the webhook

Once routed, you have two options:
  • Forward it to your app: Nango forwards the activity to your webhook URL with connection attribution. See External webhook forwarding.
  • Process it in a sync: run a sync when the activity arrives using webhookSubscriptions and onWebhook. See Real-time syncs.
Subscriptions match the activity’s type, for example message, conversationUpdate, messageReaction or invoke. Use ['*'] to receive every type. For the activity schema, see Microsoft’s Bot Framework activity reference.

​
Rollback strategy

To stop deliveries through Nango, clear the Messaging endpoint on the Azure Bot’s Configuration page, or point it back at your own bot service.
Need help getting started? Join us in the community.