Teams channel delivers conversationUpdate events to our endpoint successfully but chat messages are never delivered. Web Chat channel works correctly end-to-end.

Question

CONFIRMED WORKING:

• Endpoint reachable from internet (TLS 1.2, Let's Encrypt cert)
• Web Chat messages hit endpoint and return 200 - conversationUpdate events from Teams hit endpoint and return 200
• Bot Framework IP [Moderator note: personal info removed] confirmed reaching VM via nginx logs
• Python listener on endpoint returns 200 for all POST requests including those with Authorization headers

CONFIRMED NOT WORKING:

• Teams chat messages never appear in nginx access logs
• MS diagnostics show: "Bot Service requests rejected as unauthorized, resulting in 502 errors returned to client"
• 401 source unknown — endpoint returns 200 for everything

NSG RULES:

• AzureBotService allowed on ports 443 and 3978
• AzureCloud.AustraliaEast allowed on port 443
• PowerPlatformInfra.AustraliaEast allowed on port 443

TIMELINE:

• Bot worked briefly on 5 April (messages delivered, dispatched)
• Stopped working after VM reboot
• Web Chat has worked consistently throughout
• Teams chat messages have never successfully delivered since reboot

Answer 1

Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Hi Nicolas Jarvisto

Based on the behavior described, particularly that Teams chat messages never reach your nginx logs while other events do, the issue may be related to authentication or request validation occurring at the Azure Bot Service or Bot Framework connector level, rather than at the bot endpoint itself.

As a first step, I recommend rechecking the bot authentication configuration and validating that it is correctly applied after the VM reboot. This includes confirming that the Microsoft App ID and associated credentials are present, correct, and still valid, as well as ensuring they are properly loaded by the running service.

If the issue persists after revalidating authentication, it would be appropriate to raise a support ticket with Microsoft Support via Services Hub for further investigation.

Please note that access to the Services Hub depends on your organization’s support agreement and may require a paid support plan. You can review the requirements and sign-in conditions in the Services Hub sign-in FAQs before submitting a request. 

In the meantime, you may also consider opening a new thread on the GitHub, where engineers and community contributors may help review the behavior and provide additional insights.

Reference: Participating in a discussion - GitHub Docs. 

Please note that this is a public peer-to-peer community forum. While moderators and community members can share guidance and experiences, we do not have access to backend systems or the necessary tools to investigate this further.

Thank you again for your understanding.

---

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.