Teams bot not receiving messages — Azure Bot is healthy, Web Chat works, but no Teams activity logged

Hello YT (TFG),

Welcome to Microsoft Q&A .Thank you for reaching out.

The observed behavior indicates that the bot application and hosting endpoint are functioning correctly, as messages sent through Web Chat are successfully delivered and logged. However, messages sent from Microsoft Teams are not reaching the Azure Bot Service at all. This means the issue is occurring before any request reaches the bot endpoint, specifically within the Teams channel routing and authentication flow.

When a message is sent in Teams, the message is first accepted by the Teams client and service. Only after that does it get routed through the Bot Framework connector to Azure Bot Service and then to the bot’s messaging endpoint. In this scenario, Teams shows the message as sent, but the activity is not forwarded further. As a result, no activity appears in Azure Bot logs and the /api/messages endpoint is never called.

As asked if additional configuration required for Teams - No additional hidden configuration is required beyond the documented setup. However, Teams applies stricter validation rules than Web Chat. As a result, a configuration that works in Web Chat may still fail in Teams if any Teams‑specific requirement is not fully aligned.

The most common reasons for Teams messages not reaching Azure Bot Service include:

1. App ID mismatch between:
   • Azure Bot resource
   • Teams app manifest
   • Bot application configuration
2. Teams channel registration becoming stale or incomplete
3. Incorrect or missing Teams app manifest scopes
4. Authentication failure due to an invalid or outdated app secret
5. Tenant or Teams app policies blocking bot message routing
6. Bot being tested in a context or scope not supported by the manifest

Please check if the following trouble shooting steps help:

1. Validate Teams channel routing

• Open the Azure Bot resource.
• Navigate to Channels > Microsoft Teams.
• Use Open in Teams to test direct connectivity.
• If messages do not reach the bot using this option, the issue is confirmed at the channel routing layer.

Connect a Bot Framework bot to Microsoft Teams - Bot Service | Microsoft Learn

2. Verify Teams app manifest configuration

• Confirm the botId exactly matches the Azure Bot App ID.
• Ensure required scopes are included:
  • personal for 1:1 chats
  • groupchat for group chats
  • team for channel conversations
• Re‑package and re‑upload the app after any manifest change.

Microsoft 365 app manifest schema reference | Microsoft Learn

3. Confirm message context and usage

• In team channels or group chats, ensure the bot is explicitly @mentioned.
• In personal scope, messages can be sent directly without mention.

Conversations with a Bot - Teams | Microsoft Learn

4. Validate authentication configuration

• Confirm the App ID and secret configured in the bot application match the Azure Bot resource.
• Regenerate the app secret if needed and update the bot configuration.
• Ensure the app registration tenant configuration matches the Teams tenant.

Add authentication to a bot in Bot Framework SDK - Bot Service | Microsoft Learn

5. Recreate the Teams channel registration

• Remove the Teams channel from the Azure Bot resource.
• Save changes.
• Add the Teams channel again and save.
• Reinstall the Teams app.

Troubleshoot bot configuration issues - Bot Service | Microsoft Learn

6. Review logging and diagnostics

• Enable Application Insights for the bot.
• Check for incoming requests from msteams channel.
• Absence of such traffic confirms that Teams is not forwarding activities.

Thank you !

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the response was helpful. This will be benefitting other community members who face the same issue.

I think the break is when u never get that first teams conversationUpdate… without it the teams route never comes up, so flip the install scope once and check the token audience, that’s where these silent‑but‑healthy bots usually fail. If it still stays quiet, look at the tenant app‑permission policy blocking bot msgs.