This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 65%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Hello Team,
We have created a new multi-tenant Microsoft Teams bot application in last week. and deployed it successfully on Microsoft Azure.
Current issue:
When we send a message from our backend server to the bot, and the bot tries to send the message to a Teams channel, we receive the following error:
"Authorization has been denied for this request."
We are able to successfully obtain the access token, but the message sending fails with this authorization error.
Question 1:
From online articles and discussions, we understand that multi-tenant bot creation has been deprecated after July 31, 2025.
However:
At that time, it was working correctly.
It has now started failing with the authorization error.
Could you please confirm:
Question 2:
If the issue is due to multi-tenant deprecation and we need to switch to a single-tenant model:
How can we support users from other tenants?
Is it possible to distribute a custom Teams app package directly to specific tenants (without publishing to the Teams App Store)?
In a single-tenant bot setup, what is the recommended approach to support cross-tenant customers while maintaining proper service-to-service authentication?
We would appreciate clarification on the recommended architecture going forward.
Thank you.
An Azure service that provides an integrated environment for bot development.
If this issue is due to the deprecation of multi-tenant bots and we switch to a single-tenant configuration, will the bot continue to work normally between Microsoft Teams and our backend server (both incoming and outgoing messages)?
and will it still work for users in other tenants if we distribute a custom Teams app package to them instead of publishing it to the Teams App Store?
I have been waiting for the last 3 days. Please provide an update at the earliest.
I have been waiting for the last 3 days. Please provide an update at the earliest.
I think that… single‑tenant won’t break ur backend↔Teams flow at all, and cross‑tenant still works if u drop the bot once into the target channel so Teams rebuilds the serviceUrl then just allow the RSC.
Thanks for the clarification.
Also, one question from our side:
Is it still possible for us to create a new multi-tenant bot app now? We understand that multi-tenant bot registration is deprecated, but we had created few earlier in September 2025, and that setup is still working correctly. Because of that, we wanted to check whether creating a new multi-tenant bot is still technically possible or if it is now completely blocked.
Could you please confirm this?