Forum Discussion
Questions About Alternatives to Multi-Tenant Bots After July 31, 2025 Deprecation
Hello,
As the ability to create multi-tenant bots in Azure will be discontinued after July 31, 2025, I’d like to ask if there are any viable alternatives available now?
If I create a single-tenant bot and publish it to the Teams App Store, will users from other tenants still be able to interact with the bot? Additionally, will the bot be able to access their basic user profile information (only user name and aadObjectId) and conversation data?
From my understanding, access tokens obtained using the client ID and client secret are tenant-scoped, meaning they are not valid across other tenants. As a result, the bot cannot access user information such as profile photos or email addresses from users in other tenants — is that correct?
I'd really appreciate any clarification or recommended best practices on this.
Thank you!
2 Replies
After July 31, 2025, Azure will no longer support multi-tenant bots. A good workaround is to use a single-tenant bot and publish it to the Teams App Store users from other tenants can still interact with it. However, the bot will only have access to basic info like the user's name and aadObjectId, not things like profile photos or email addresses, unless the user signs in and gives consent. Since access tokens are tenant-specific, you’re right that they won’t work across tenants for deeper data. The best approach is to design with these limits in mind and use sign-in when more access is needed.
Prasad_Das-MSFTMicrosoft
You can create a single-tenant bot and publish it to the Teams App Store. When published, users from other tenants can interact with the bot. However, the bot will only have access to basic user profile information (e.g., aadObjectId and displayName) and conversation data if the bot is granted RSC permissions.
Thanks,
Prasad Das
------------------------------------------------------------------------------------------
If the response is helpful, please click "**Mark as Best Response**" and like it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.
