Bot Services: Teams channel not calling endpoint

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

• Troubleshooting Azure AI Bot Service bots - Bot Service | Microsoft Learn
• Configure an Azure AI Bot Service bot to run on one or more channels - Bot Service | Microsoft Learn
• Connect a Bot Framework bot to Microsoft Teams - Bot Service | Microsoft Learn
• Authenticate requests with the Bot Connector API - Bot Service | Microsoft Learn

Please let us know if the response was helpful

Thank you

What I tried so far:

• removing / readding the teams channel
• decommissioning and redeploying the whole bot
• adapting the manifest for teams to match the working bot
• changing the endpoint of the non-working bot to the endpoint of the working bot
  none of this helped.