Forum Discussion
Teams won't talk to Azure Bot Messaging endpoint
The "Web Chat" channel works fine, but the "Microsoft Teams" doesn't. A few clues as to what might be going on...
1) If I point to an ngrok tunnel that goes directly to the https service (haproxy) it works fine.
2) I'm seeing the occasional portal.azure.com pre-flight (OPTIONS) request logged against the service, but nothing else.
So, Teams/Azure Bot can reach the service, and it would seem that it's pretending to be a browser and doing CORS stuff. I've permitted and exposed all the headers the pre-flight is asking for. I also respond with the required specific Origin -> https://portal.azure.com header and allow authentication (because Azure Bot sends an authorization header).
Any ideas about what could be going on?
nexus-steve - these are the cipher suites that SMBA supports:
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
12 Replies
stephenmdyoung : Hey are you trying to run bot from local or have you deployed it on app service?
Also, the endpoint you are giving should be publicly accessible and in channels, it should be connected to Teams.
Please have a look at this: Connect a bot to Microsoft Teams- Thanks HunaidHanfee-MSFT - but yes, the endpoint is publicly available and the bot has both the Teams and Web Chat channels. What's more, the relevant Microsoft services must be seeing the relevant settings or we wouldn't be seeing the OPTIONS request at the endpoint.
Steve- As I understand from the question app is working when pointed to ngrok. You are facing problem when you are giving some other endpoint.
If you doing it locally make sure that bot is running and ngrok or other endpoint should point to the same port on which local bot is running.
Also, you should check on Teams web client and look console for errors. Please make sure that you have given the correct botId in the manifest.
Could you please share bot Id and timestamp when you faced this issue so that we can check at our end what is wrong?
