Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs
Start by isolating whether the issue is with the bot itself or only with the Teams channel:
- In Azure portal, open the bot resource.
- Open Test in Web Chat.
- Send the bot a message.
If the bot also fails in Web Chat, check whether the bot endpoint is reachable:
- In the bot resource, open Overview.
- Copy the Messaging endpoint.
- Paste it into a browser.
Expected result:
- HTTP 404 or 405 means the bot is reachable.
- A browser error such as This site can't be reached means the bot is down and needs to be redeployed.
If the bot works in Web Chat but not in Teams, the problem is likely Teams-specific. Check these common causes:
- In channel conversations, the bot must be @mentioned. Bots in Teams channels only receive messages when explicitly @mentioned.
- Strip the bot mention from incoming text before command parsing. In channel messages, the bot name is included in the text.
- If testing the bot locally through a dev tunnel and Teams messages stopped arriving even though the tunnel looks healthy, restart the Microsoft Teams channel for the bot in Azure portal, then send a test message again.
Important: if restarting the Teams channel is needed, restart it rather than deleting and re-adding it. Deleting the Teams channel regenerates keys and can invalidate stored conversation IDs used for proactive messaging.
If the issue is only that recent chat messages are not appearing in Teams, also try:
- Quit and restart Teams fully.
- Check the internet connection.
- Try Teams on the web.
- Sign out of Teams and sign back in.