Deprecation of multi-tenant bots and the Bot Framework REST API

[mattmikolay]

With the upcoming deprecation of multi-tenant bots, I’m wondering how the Bot Framework REST API (i.e. Bot Connector Service) is affected.

I have a single-tenant bot registered with Azure that I intend to submit to the Microsoft Teams Store so that external tenants can use it. Separately, I have a backend that uses the Bot Framework REST API to send messages as the bot to existing MS Teams conversations.

My bot is not multi-tenant, so I cannot use the multi-tenant login URL (https://login.microsoftonline.com/botframework.com/oauth2/v2.0/token) to request an access token for use with the Bot Framework REST API.

Instead, if I request a new access token using the single-tenant login URL (https://login.microsoftonline.com/MICROSOFT-TENANT-ID/oauth2/v2.0/token) for every tenant that has installed my bot in Microsoft Teams, will I be able to utilize the Bot Framework REST API from my backend to send messages to different tenants’ MS Teams conversations?

If there is a better place than this repository to ask my question, please let me know. Thank you.

[kunsinghms]

Hi @mattmikolay If you created single tenant bot then you must have provided a tenant id during the creation of Bot resource. The same tenant id you will have to use while you are asking for token instead of using botframework.com tenant.