Azure AI Bot Service
An Azure service that provides an integrated environment for bot development.
Same symptons. Removing and re-adding the Teams channel on the Bot Service is what fixed it for me.
Thanks @Karnam Venkata Rajeswari
Teams bot not receiving messages — Azure Bot is healthy, Web Chat works, but no Teams activity logged
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 45%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYT%3C/text%3E%3C/svg%3E)
YT (TFG)
0
Reputation points
Hi,
I’m using an Azure Bot with the Teams channel enabled. The bot deploys successfully, the messaging endpoint is reachable, and the Azure Bot resource shows Healthy.
When I test the bot using Web Chat, everything works — Azure Bot logs show incoming activity, and my /api/messages endpoint receives the messages.
However, when I send a message to the bot in Microsoft Teams, nothing appears in the Azure Bot logs, and my endpoint is never called. Teams shows the message as sent with a checkmark, and there are no errors in the Teams client or Azure.
What I’ve verified:
• Azure Bot → Healthy
• Teams channel → Enabled
• Messaging endpoint → reachable
• Web Chat → working
• Manifest uses the correct Microsoft App ID
• App installs cleanly in Teams
• Reinstalling the app or readding the team channel in Azure Bot didn't resolve the issue.
• No errors anywhere
The issue:
Teams messages never reach Azure Bot Service, even though Web Chat does. Because of this, Azure Bot logs remain empty for Teams traffic.
My question:
Is there any additional configuration required for an Azure Bot to receive messages from Teams, or any known routing issues where Teams shows messages as sent but Azure Bot never receives them?
How do I start troubleshooting this issue?
Azure AI Bot Service
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 51%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKV%3C/text%3E%3C/svg%3E)
Karnam Venkata Rajeswari 2,890 Reputation points Microsoft External Staff Moderator2026-03-31T17:57:38.22+00:00 Hello YT (TFG),
Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful.
Thank you
-
Karnam Venkata Rajeswari 2,890 Reputation points Microsoft External Staff Moderator
2026-04-08T07:54:48.4733333+00:00 Hello YT (TFG),
Just checking in to see if you have got a chance to see my response to your question in resolving the issue.
Looking forward to your response and appreciate your time on this.
If the query has been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.
Thank you!
Sign in to comment
3 answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 12%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERJ%3C/text%3E%3C/svg%3E)
Russ James 0 Reputation points2026-05-07T14:53:15.83+00:00 -
Karnam Venkata Rajeswari 2,890 Reputation points Microsoft External Staff Moderator
2026-05-07T16:59:51.4033333+00:00 Hello @Russ James ,
Thank you for taking time and confirming the solution.
Could you please take a moment to accept the answer with an upvote.This helps others in the community with the same question find the solution more easily.
Thank you!
Sign in to comment -
-
Karnam Venkata Rajeswari 2,890 Reputation points Microsoft External Staff Moderator
2026-03-30T17:10:21.05+00:00 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:
- App ID mismatch between:
- Azure Bot resource
- Teams app manifest
- Bot application configuration
- Teams channel registration becoming stale or incomplete
- Incorrect or missing Teams app manifest scopes
- Authentication failure due to an invalid or outdated app secret
- Tenant or Teams app policies blocking bot message routing
- Bot being tested in a context or scope not supported by the manifest
Please check if the following trouble shooting steps help:
- 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
- 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
- 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
- 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
- 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
- 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.
-
YT (TFG) 0 Reputation points
2026-04-08T12:53:16.7933333+00:00 Hi Karnam,
Thank you for your extensive trobleshooting steps. Unfortunately, I have done all of the steps you mentioned prior posting the questions here. The issue I am having is I don't even get any message in the AzureBot coming from Teams itself, however teams doesn't indicate any error.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 15%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAV%3C/text%3E%3C/svg%3E)
Anshika Varshney 11,225 Reputation points Microsoft External Staff Moderator2026-05-06T06:52:24.34+00:00 Hi YT,
I understand how frustrating this situation is, especially since everything appears to be working correctly in Web Chat but not in Teams.
From what you described, your bot and endpoint setup are working fine. Since Web Chat is able to send messages and your endpoint is receiving them, we can safely say the issue is not with your bot code or hosting.
In your case, the problem is happening before the request reaches your bot. Microsoft Teams is accepting the message, but it is not forwarding it to Azure Bot Service, which is why you do not see any logs or activity at your endpoint. [Data, priv...soft Learn | Learn.Microsoft.com]
This usually points to Teams specific routing or validation behavior rather than a general bot issue.
Here are a few focused checks that can help narrow this down:
- Try using the Open in Teams option from the Azure Bot resource under Channels. This helps confirm whether the Teams channel is correctly routing messages. If messages still do not reach your bot from there, then the issue is at the channel routing level.
- Check whether your bot is receiving the initial conversation update event. In some cases, if this first handshake does not happen, Teams may show messages as sent but will not forward them to the bot at all. This can result in exactly the behavior you are seeing.
- Review your Teams app manifest and try reinstalling the app after making a small change. For example, switching the scope once and reinstalling can sometimes refresh the routing internally.
- Check tenant level app permission or messaging policies in Teams. Sometimes policies allow the app to be installed but silently block message routing, which makes the bot appear healthy but inactive.
- Try removing and adding the Teams channel again in Azure Bot Service, then reinstall the app in Teams. This can help if the channel registration has become stale.
Overall, your setup looks correct, and this kind of issue is usually related to Teams side routing or policy validation rather than your bot implementation.
Hope this helps you move forward. Let me know what you observe after trying these steps.
Thankyou!
Sign in to comment - App ID mismatch between:
-
kagiyama yutaka 3,080 Reputation points2026-03-28T07:28:15.87+00:00 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.
-
YT (TFG) 0 Reputation points
2026-04-08T12:54:52.2366667+00:00 Hi Yutaka_K_JP,
Thank you for your response. I don't event get any message from Teams to AzureBot, not even the conversationUpdate, when I open the bot the first time. It seems like all communication from Teams to Azure drops silently.
-
kagiyama yutaka 3,080 Reputation points
2026-04-08T23:20:47.2733333+00:00 Hi YT (TFG), yeah… if convUpdate never shows, that’s Teams dropping you at the edge. Check the aud — api://<appId> vs api://botid-<appId> is a silent kill in BF. If the aud’s clean, it’s the tenant policy blocking bot traffic… same dead‑air. nothing else in this stack dies this quietly.
Sign in to comment -