Bot Services: Teams channel not calling endpoint

Stefan Grothkopp 0 Reputation points
2026-07-01T08:39:22.5833333+00:00

I have setup a bot that should communicate via the Teams channel.
It works when I test with web chat, teams channel says "healthy".

Another bot in our tenant works (to not a tenant wide bot message permission issue).
The endpoint works but is never called.

Azure AI Bot Service
Azure AI Bot Service

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

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Karnam Venkata Rajeswari 5,005 Reputation points Microsoft External Staff Moderator
    2026-07-01T08:56:02.8133333+00:00

    Hello @Stefan Grothkopp ,

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

    Based on the current behavior, the bot application appears to be functioning correctly because communication through Web Chat succeeds. This indicates that the bot runtime and messaging endpoint are operational.

    The most important step in isolating this issue is determining whether any Teams-generated request reaches the bot endpoint.

    If requests are visible in logs

    The troubleshooting needs to be focused on:

    • Authentication failures (App ID or JWT validation)
    • Bot runtime exceptions
    • Activity processing issues within the bot

    If no requests are visible , then

    The troubleshooting should primarily focus on:

    1. Bot identity alignment
    2. Teams channel registration and binding
    3. Teams application manifest configuration
    4. Routing or access restrictions between Teams and Bot Framework services

    This distinction helps determine whether the issue is occurring before or after request delivery to the application.

    Please check if the following helps-

    1. Validating Bot Identity Alignment A mismatch in identity configuration is one of the most common causes of this scenario. Please verify consistency across:
      • Azure Bot Resource > Microsoft App ID
      • Microsoft Entra ID App Registration > Application (Client) ID
      • Teams App Manifest > botId
      • Bot Runtime Configuration > MicrosoftAppId
      Additionally, please also confirm:
      • The App Registration is active and enabled.
      • Any client secret or certificate remains valid and unexpired.
      • Required admin consent has been granted.
      • The Enterprise Application is enabled.
      Even minor inconsistencies can prevent Teams activities from being delivered while the channel continues to report a healthy state.
    2. Performing an Independent Teams Validation As an additional isolation step, please launch the bot using the Open in Teams experience available from the Azure Bot resource. This helps determine whether:
      • Teams traffic can successfully reach the Azure Bot registration, or
      • The issue is specific to the Teams application package, installation scope, manifest configuration, or cached registration.
      It is also recommended to verify the scope being used during testing:
      • Personal Chat
      • Group Chat
      • Team Channel
      Differences in installation scope or bot configuration can affect activity delivery behavior.As an additional isolation step, please launch the bot using the Open in Teams experience available from the Azure Bot resource. This helps determine whether:
      • Teams traffic can successfully reach the Azure Bot registration, or
      • The issue is specific to the Teams application package, installation scope, manifest configuration, or cached registration.
      It is also recommended to verify the scope being used during testing:
      • Personal Chat
      • Group Chat
      • Team Channel
      Differences in installation scope or bot configuration can affect activity delivery behavior.
    3. Comparing Against the Working Bot Since another bot in the same tenant is functioning correctly, a side-by-side comparison can often reveal configuration drift. Please compare:
      • Bot App ID and identity type
      • Teams manifest configuration
      • Azure Bot channel configuration
      • App Registration settings
      • Authentication configuration
      • Hosting and deployment architecture
      • Network path differences (WAF, Front Door, APIM, proxy layers, etc.)
      Because the same endpoint has already been validated with a working bot, endpoint availability becomes a lower-priority concern, making configuration and registration differences a more likely focus area.
    4. Validating Telemetry and Request Flow Please review telemetry using:
      • Application Insights
      • App Service access logs
      • Container ingress logs
      • Gateway and WAF diagnostics
      The objective is to determine:
      • Whether any inbound request is received from Teams
      • Whether authentication or routing failures are occurring
      • Whether exceptions are being thrown during message processing
      Interpretation
      • No inbound requests observed - Focus on routing, identity, channel configuration, or registration.
      • Requests observed - Focus on authentication, authorization, or runtime processing.

    The following references might be helpful , please check them out

    Please let us know if the response was helpful

     

    Thank you

    Was this answer helpful?

    0 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.