An Azure service that provides an integrated environment for bot development.
If the bot works in Test in Web Chat but not in Teams, the issue is typically channel-specific rather than in the bot code itself.
Use this troubleshooting path:
- Confirm the bot works in Web Chat first In the Azure portal, open the bot resource and use Test in Web Chat. If it responds there, the bot endpoint is reachable and the problem is likely with the Teams channel or Teams app setup.
- Verify the messaging endpoint is reachable
In the bot resource Overview pane, copy the Messaging endpoint and open it in a browser.
- If it returns HTTP 404 or 405, the bot is reachable.
- If it returns a browser error such as "This site can't be reached", redeploy or fix endpoint availability.
- Check Teams channel configuration If Web Chat works but Teams does not, remove and reconfigure the Teams channel. Channel configuration issues are a common cause when one channel works and another does not.
- Validate Teams app packaging and install method Bots in production should be added to Teams as part of a Teams app. Adding a bot by GUID is only recommended for testing and severely limits bot functionality.
- Check Teams prerequisites
Make sure the environment has:
- a bot published to Azure
- a Teams developer tenant with custom app uploading or sideloading enabled
- a valid Teams app package
- Check for channel-specific behavior Some features behave differently by channel. A bot can work in Web Chat but still fail or behave differently in Teams because channel capabilities differ.
- Test end-to-end in Teams after channel setup Open the Teams app package in Teams and interact with the bot there. If the bot appears as a contact but messages still do not flow, the remaining issue is in Teams channel configuration or channel-specific behavior.
- Check HTTPS and bot configuration if cloud testing fails
For cloud-connected bots, verify:
- the Messaging endpoint includes the correct path such as
/api/messages - the endpoint uses HTTPS
- the app ID and password are valid
- the Messaging endpoint includes the correct path such as
A practical conclusion from similar cases is that when Web Chat succeeds and Teams does not, focus on:
- Teams channel configuration
- Teams app manifest/package setup
- HTTPS endpoint correctness
- channel-specific behavior in Teams
References: