Issue with Azure BOT communication with Teams

Question

Issue with Azure BOT communication with Teams

Biswarup Dutta 0

Hi Team,

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(TenantID REMOVED). APP Id of the BOT is TenantID REMOVED.
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 -[TenantID REMOVED]
Admin consent granted on Tenant B using the url - [https://login.microsoftonline.com/ [TOKEN HIDDEN]/adminconsent?client_id=TOKEN HIDDEN]&redirect_uri=https://token.botframework.com/.auth/web/redirect](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)
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

Answer recommended by moderator

1 additional answer

Your answer

Answer 1

Biswarup Dutta 0

Thanks **Nivedipa-MSFT...
**The issues was fixed. This was because of wrong initialization of Adapter for cross tenant communication using new SDK (cloudAdapter), this has been fixed now.

Answer 2

Yevhen Marynchak 0

Try enabling the Microsoft Teams channel in your Azure Bot Service and make sure its status shows healthy, confirm the bot’s messaging endpoint is correct and publicly reachable, check the app registration in Entra ID so the Microsoft App ID and secret or certificate are valid and admin consent is granted, verify the Teams app manifest contains the right botId and scopes, look at Bot Framework and Azure diagnostic logs and use the Bot Framework Emulator and the portal’s Open in Teams to reproduce errors, check for network, TLS or CORS issues that could block the endpoint, ensure the bot has the necessary roles and permissions in the target tenant, and if the problem continues gather request IDs, timestamps and example error messages and open a support case or post those details to Microsoft Q&A so the issue can be investigated.

Biswarup Dutta 0 Reputation points

2026-02-13T13:21:31.83+00:00

Thanks Yevhen,

I already enabled the Microsoft Teams channel in Azure Bot Service and its status shows healthy

The bot’s messaging endpoint is correct and publicly reachable, my team's message received by BOT. No issue in that.

The app registration and secret or certificate are valid and admin consent is granted (in tenant B)
The Teams app manifest contains the right botId and scopes, the manifest and icons were deployed in Team and using the APP in teams i am sending message to BOT

Bot Framework Emulator is working fine in my local machine

The following i could not figure out how to do:
check for network, TLS or CORS issues that could block the endpoint, ensure the bot has the necessary roles and permissions in the target tenant.

Sharing the BOT-Team communication log, if this can help identifying the issue Communication_Log_sample.txt

Anyway thanks for your prompt response.
Nivedipa-MSFT 3,986 Reputation points Microsoft External Staff Moderator

2026-02-18T09:00:56.6666667+00:00
Hello Biswarup Dutta,
Thank you for providing the log. The key lines indicate:

POST /amer/86dd60b0-86b8-4604-be2a-6d607879e676/v3/conversations/... HTTP/1.1" 401 61 ... {"message":"Authorization has been denied for this request."}

This shows that your bot successfully obtains an access token, but receives a 401 Unauthorized error when sending a message to Teams via the Bot Framework.

What’s happening:

Your bot authenticates with Azure AD and gets a token for the scope https://api.botframework.com/.default.

However, the Bot Framework or Teams service is not accepting this token for the operation.

Common causes and solutions:

App registration is not set to multi-tenant: Ensure the app registration in Azure AD is configured as multi-tenant, not single tenant, even if “multiple organizations” is selected.

Admin consent not granted in Tenant B: After making the app multi-tenant, re-grant admin consent in Tenant B using the admin consent URL.

Incorrect app ID or secret: Confirm that the app ID and secret or certificate in your bot code match the Azure AD registration.

Token audience mismatch: The token must have the audience set to https://api.botframework.com; using a different audience will cause it to fail.

Enterprise application disabled in Tenant B: In Azure AD under Enterprise Applications in Tenant B, verify that your bot is enabled and assigned to the correct users or groups.

Next steps:

Set the app registration in Azure Portal (Tenant A) to “Accounts in any organizational directory (Any Azure AD directory - Multitenant).”

Re-grant admin consent in Tenant B after updating the app registration.

Double-check that your bot code uses the correct app ID and secret.

Ensure the app is enabled and assigned to the right users/groups in Tenant B’s Enterprise Applications.

Restart your bot and test the process again.
SRILAKSHMI C 15,030 Reputation points Microsoft External Staff Moderator

2026-02-25T10:15:22.79+00:00

Hello Biswarup Dutta,

Did you get any chance to review the above response. Do let me know if you have any further queries.

Thank you!

Share via

Issue with Azure BOT communication with Teams

1 additional answer

Your answer