Forum Discussion
What is the recommended bot type for multi-tenant bots?
According to this https://learn.microsoft.com/en-us/azure/bot-service/bot-service-quickstart-registration?view=azure-bot-service-4.0&tabs=multitenant#bot-identity-information multi-tenant bots cannot be created after July 31, 2025.
Another option to reach tenants other than ours is to use incoming webhooks. However, according to this https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet, incoming webhooks will be deprecated at the end of 2025.
I would like to create a bot that can be deployed to any Microsoft Teams outside our organization. What is the recommended approach?
Thank you.
The recommended and future-proof approach is to:
✅ Use a Teams App with an Azure AD Single-Tenant Bot and Publish it to AppSource
Here’s why and how:
- Multi-tenant bot registration is deprecated: As per Microsoft's roadmap, starting July 31, 2025, you can no longer create bots with multi-tenant Azure AD apps.
- Incoming webhooks are also deprecated by end of 2025.
- AppSource distribution supports cross-tenant deployment:
- Even if your bot is single-tenant, publishing your Teams app (with the bot) to the Microsoft Teams Store / AppSource allows external tenants to install and use it.
- This is the supported method to reach tenants beyond your organization after multi-tenant support ends.
Steps (short):
- Create a single-tenant Azure AD bot in the Azure portal.
- Package it in a Teams app manifest (manifest.json).
- Ensure your bot supports tenant-specific behavior and handles tenantId in the activity payload.
- Submit the app to Microsoft AppSource (requires validation & approval).
- Tenants outside your org can install from the Teams App Store.
This is the long-term, compliant path supported by Microsoft for cross-tenant bot usage.
Thanks,
Ayush
If the response is helpful, please click "**Accept Answer**" and upvote it. You can share your feedback via [Microsoft Teams Developer Feedback](https://aka.ms/DevSupportFeedback) link. Click [here](https://aka.ms/DevCommunityEscalationForm) to escalate.
4 Replies
Ayush2001Microsoft
The recommended and future-proof approach is to:
✅ Use a Teams App with an Azure AD Single-Tenant Bot and Publish it to AppSource
Here’s why and how:
- Multi-tenant bot registration is deprecated: As per Microsoft's roadmap, starting July 31, 2025, you can no longer create bots with multi-tenant Azure AD apps.
- Incoming webhooks are also deprecated by end of 2025.
- AppSource distribution supports cross-tenant deployment:
- Even if your bot is single-tenant, publishing your Teams app (with the bot) to the Microsoft Teams Store / AppSource allows external tenants to install and use it.
- This is the supported method to reach tenants beyond your organization after multi-tenant support ends.
Steps (short):
- Create a single-tenant Azure AD bot in the Azure portal.
- Package it in a Teams app manifest (manifest.json).
- Ensure your bot supports tenant-specific behavior and handles tenantId in the activity payload.
- Submit the app to Microsoft AppSource (requires validation & approval).
- Tenants outside your org can install from the Teams App Store.
This is the long-term, compliant path supported by Microsoft for cross-tenant bot usage.
Thanks,
Ayush
If the response is helpful, please click "**Accept Answer**" and upvote it. You can share your feedback via [Microsoft Teams Developer Feedback](https://aka.ms/DevSupportFeedback) link. Click [here](https://aka.ms/DevCommunityEscalationForm) to escalate.Hi Ayush2001, Thank you for the detailed information. We are currently using the Bot Framework with both C# and Python to build a customized conversational bot. However, we’ve encountered issues with single-tenant authentication earlier stages, as the Bot Framework appears to support tenant-based authentication only in multi-tenant environments. Could you please advise on how we can overcome this limitation or implement a workaround that allows single-tenant/user-assigned authentication to function correctly?
What does it mean when it's stated that "Incoming webhooks are also deprecated by the end of 2025"? Does this imply that our existing multi-tenant Bot Framework application will stop functioning after that? If these changes impact existing multi-tenant bots built using the Bot Framework, it could create a significant issue for us. We need to understand the potential consequences and plan accordingly.
We have the same question - having already built our bot integration. It seemed like quite a sudden change with pretty minimal communication!
I totally agree, renrutsirhc . I did not see this either in the https://learn.microsoft.com/en-us/microsoftteams/platform/whats-new?pivots=ga-feature section in the docs, or in the Teams blog. Maybe Pete_Daderko could help in the next What's new blog entry. It would be appreciated. There are so many outdated docs that refer to non-existent features. One such example is the documentation about https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-outgoing-webhook?tabs=urljsonpayload%2Cdotnet#create-outgoing-webhooks-1. Also, broken links - for example, the https://dev.teams.microsoft.com/appvalidation.html service page has a "quick survey link" that is just broken. I wanted to provide feedback, but I could not. There are also ton of "preview" / "beta" features - it is no surprise that it is hard to find what is supported and what is not. Another example here is the Azure CLI's support for Teams: full of preview (see screenshots).
