microsoft / microsoft/BotFramework-WebChat
Azure BOT communication issue with Teams
Open
Nobody has claimed this yet.
Bot Services
customer-reported
question
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
I have a question
Sharing following communication details about a Azure BOT, which is deployed in Teams. But there are some issues in communication, please help.
- Azure Bot created in Tenant A(Tenant id - b6b9c2b3-3f92-4643-afb2-8e15275bf764). APP Id of the BOT is fc60af25-4922-4ab2-85b1-03810b7e6ea7.
- Bot Type- Single Tenant (this is only supported by Azure now)
- Supported account types - Multiple organizations (app registration - Authentication - Settings), did this because of requirement of cross tenant communication.
- BOT channel - Teams
- BOT deployed in teams (in Tenant B - tenant id -86dd60b0-86b8-4604-be2a-6d607879e676)
- Admin consent granted on Tenant B using the url - https://login.microsoftonline.com/86dd60b0-86b8-4604-be2a-6d607879e676/adminconsent?client_id=fc60af25-4922-4ab2-85b1-03810b7e6ea7&redirect_uri=https://token.botframework.com/.auth/web/redirect
- In BOT code using new SDK (4.17.1) (botbuilder-core==4.17.1, botbuilder-schema==4.17.1, botbuilder-integration-aiohttp==4.17.1, botframework-connector==4.17.1)
- Getting Unauthorized error in turn_context.send_activity (received the message successfully in on_message_activity)
- Sharing the Teams-BOT-Teams communication log. Please help me in resolving the issue.Communication_Log_sample.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the attached Communication_Log_sample.txt first, then trace the bot code path from on_message_activity to turn_context.send_activity. Done means identifying the cause of the Unauthorized response in the cross-tenant Teams setup and documenting a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- authentication, backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100