Share via

Azure Bot – Teams channel not forwarding user messages to webhook endpoint

CodeDobby 5 Reputation points
2026-05-05T12:11:45.99+00:00

Our Azure Bot Service receives messages fine via Web Chat (Test in Azure Portal), but when users reply in Microsoft Teams, nothing arrives at the messaging endpoint (n8n webhook). The bot can still proactively send messages to Teams – only incoming user messages are not forwarded.

What we checked:

  • App credentials valid and not expired
  • Teams channel active in Azure Portal
  • Messaging endpoint correct and reachable (HTTPS)
  • Bot is installed and visible in Teams
  • No changes on our end – this was working before

Others affected:

Is there a known issue with the Teams channel not forwarding user messages to the messaging endpoint? Any help appreciated.

Azure AI Bot Service
Azure AI Bot Service

An Azure service that provides an integrated environment for bot development.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anshika Varshney 11,225 Reputation points Microsoft External Staff Moderator
    2026-05-06T09:45:34.9166667+00:00

    Hi CodeDobby,

    I understand how frustrating this situation is, especially when your bot works perfectly in Web Chat, but Teams messages are not reaching your bot.

    This is a common scenario where the issue is not with your bot code but with the Teams channel flow.

    In Azure Bot Service, the message flow is different from Web Chat.

    When a user sends a message in Teams, it does not go directly to your bot. Instead, the message first goes to Azure Bot Service, which then validates and forwards it to your bot endpoint.

    If your bot works in Web Chat but not in Teams, it clearly means:

    • Your bot logic is working
    • Your messaging endpoint is reachable
    • The issue is happening before the request reaches your bot

    So, this points to a Teams channel specific issue.

    Web Chat is more flexible and may work even if some configurations are not perfect.

    Teams, on the other hand, has stricter validation rules. If anything is slightly mismatched, the request will not be forwarded at all.

    you need to can check below points:

    First, check authentication details Make sure your App ID, client secret, and tenant ID are correct and consistent across Azure Bot, app registration, and Teams app manifest

    Teams validates these values strictly, and any mismatch can block the request before forwarding

    Second, verify Teams channel configuration Go to your Azure Bot resource Open Channels Make sure Microsoft Teams channel is enabled and properly saved

    You can refer to this official documentation for channel setup: https://learn.microsoft.com/en-us/azure/bot-service/channel-connect-teams?view=azure-bot-service-4.0 [ai.azure.com]

    Third, review Teams app manifest Check that:

    • botId matches your Azure Bot App ID
    • Correct scopes are defined such as personal, team, or group chat

    Even if the app installs successfully, incorrect manifest settings can prevent message routing.

    Fourth, validate messaging endpoint behavior Your endpoint must be publicly accessible and respond properly

    If Web Chat works, it means your endpoint is likely correct but still confirm there are no network restrictions, firewall rules, or TLS issues blocking Teams requests.

    You can refer to this general troubleshooting guide: https://learn.microsoft.com/en-us/azure/bot-service/bot-service-troubleshoot-general-problems [learn.microsoft.com]

    how to troubleshoot Teams channel issues:

    Microsoft specifically mentions that if a bot works in Web Chat but fails in another channel like Teams, the issue is usually related to channel configuration or channel specific behavior. [learn.microsoft.com]

    In such cases, focus on:

    • Channel configuration settings
    • Authentication validation
    • Channel level differences and restrictions

    Additional step to try

    Sometimes the issue is due to stale channel registration.

    You can try:

    • Remove the Teams channel from Azure Bot
    • Add it again
    • Reinstall the Teams app

    This helps refresh the connection and often resolves silent routing issues

    Why this happens:

    This type of issue usually occurs because:

    • Teams applies strict authentication validation
    • Channel configuration is slightly mismatched
    • Tenant or policy restrictions block routing
    • Channel registration becomes outdated

    Hope this helps you move forward. If you can share any logs or error codes you are seeing, I can help you narrow it down further.

    Thankyou!

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.