Forum Discussion
What is the recommended bot type for multi-tenant bots?
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.
MicrosoftThe 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.
