Teams channel messages not reaching Azure Bot Service messaging endpoint (Web Chat works)

Hi @Avula Ragavendra 

Thank you for sharing details about your situation. 

First, you may want to review the response from the Q&A Assist to see whether it offers any helpful insight. 

I would also like to clarify upfront that Microsoft Q&A is a user-to-user discussion forum. Its primary purpose is to share official documentation references and insights from other users, and it is not intended for advanced or in-depth troubleshooting scenarios. 

Regarding your question about known issues related to Teams channel routing or regional traffic in the India region, including cases where Teams messages are not forwarded even though the channel appears healthy, I’m sorry to say that I was not able to find any official documentation confirming such issues. 

With that in mind, and based on the nature of your request, I would recommend reaching out to the Microsoft Support Azure team by submitting a support request through the Microsoft Azure Support Ticket | Microsoft Azure. This will allow you to receive more specialized and targeted assistance for your environment. 

I’m sorry that I’m not able to provide further insight at this time, but I hope this helps point you in a helpful direction. 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Given that Web Chat works but Teams does not, the issue is most likely channel-specific rather than with the bot core or endpoint.

Use the following checks and diagnostics focused on Teams and channel connectivity:

1. Validate Teams channel configuration and registration

• When Web Chat works but another channel does not, this typically indicates a channel configuration issue.
• Reopen the bot resource in Azure and:
  • Confirm the Microsoft Teams channel is enabled and configured for the correct bot ID and tenant.
  • If there is any doubt about the configuration, remove the Teams channel and re-add it. This is the recommended fix when external configuration (for example, app registration, page, or tenant settings) may have changed.
  • After re-adding, reinstall the Teams app and start a fresh conversation.

2. Check for Teams-specific behavior and scope

• Ensure the bot is correctly installed in the intended scope:
  • Personal chat, group chat, or channel.
• For channel or group chat conversations, users must @mention the bot; otherwise, the bot may not receive messages.
• Confirm that messages being tested are in a scope where the bot is actually part of the conversation.

3. Verify Teams → bot network connectivity

• Since Web Chat reaches the endpoint, basic reachability is proven, but Teams traffic may still be blocked or misrouted.
• From the bot’s App Service (if using Azure App Service as the bot host) use Kudu to test connectivity from bot to channel, and also verify DNS and HTTP connectivity:
  • Open Azure portal → bot App Service → Development Tools → Advanced Tools → Go → Debug console → CMD.
  • Run:
    • nslookup directline.botframework.com to confirm DNS resolution.
    • curl -I directline.botframework.com and confirm an HTTP 301 is returned, indicating connectivity.
• Use the IP addresses obtained (for example via WHOIS tools) to check whether any firewall or network rules on the AWS side or intermediate network devices are blocking traffic from Bot Framework/Teams to the API Gateway.

4. Test for channel outage or regional issue

• When a bot works in Web Chat but fails in a specific channel, a channel outage is a possible cause.
• To isolate this:
  • Create a simple test bot (for example, an Echo bot) in the same region and enable the Teams channel.
  • If the test bot receives Teams messages while the production bot does not, the issue is with the production bot’s configuration.
  • If neither bot receives Teams messages, this points to a broader Teams channel or regional issue.

5. Handle Teams API status codes and retry logic

• If any responses from Teams APIs are visible (for example, via logs or diagnostics), pay attention to status codes:
  • 401 (BotNotRegistered): indicates a registration issue; verify bot ID and password and ensure the bot is registered with Teams channel enabled.
  • 403 (BotDisabledByAdmin or BotNotInConversationRoster): indicates admin blocking or the bot not being part of the conversation; the app may need to be reinstalled or allowed by admin policies.
  • 5xx (502, 503, 504): transient issues; implement exponential backoff retries.
• Use the Teams Developer tools (Network tab, filter for invoke) to inspect error responses if using message extensions or other Teams APIs.

6. Confirm cross-tenant and authentication alignment (if applicable)

• If the bot is used cross-tenant, ensure:
  • The bot registration and app registration authentication settings (single-tenant vs multi-tenant) are aligned.
  • The adapter (for example, CloudAdapter) is initialized correctly for the target tenant; misconfiguration can cause Unauthorized when sending activities.
• Misaligned tenant configuration can result in Teams messages not being successfully forwarded to the backend even though the channel appears healthy.

7. If all checks pass but issue persists

• After validating channel configuration, connectivity, and tenant alignment, and after testing with a simple Echo bot, if Teams still does not forward messages:
  • Treat this as a potential Teams channel or service-side issue.
  • Collect logs and tests (including the Echo bot behavior and any HTTP status codes) and escalate via Microsoft Teams product support or developer community channels.

References:

• Troubleshoot bot configuration issues
• General troubleshooting for Azure AI Bot Service bots
• Send and receive messages
• Channel and Group chat conversations with a Microsoft Teams bot
• Send and receive messages with the Bot Connector API
• Troubleshoot your Microsoft Teams app
• Issue with Azure BOT communication with Teams - Microsoft Q&A
• Teams App / Bot 'Unauthorized' error when responding to an activity - Microsoft Q&A
• Cannot be added to TEAMS CHANNELS - Microsoft Q&A
• Microsoft Foundry publish to Teams Bot service error - Microsoft Q&A
• Microsoft Teams presence status shows "Unknown" on both Desktop and Web (Cloud) - Microsoft Q&A