Microsoft Teams Manifest: can contentBotId be of different tenant

Viewed 51
2 Answers

Before creating the MS bot, using ML Studio, create multi-tenant bot for perfect App registration.

Follow the procedure to create the bot and register the application.

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

By mentioning all the required. Check the manifest file for the required ContentBotId. Test the URL after app registration into multi-Tenant.

If still the error occurs. We need to setup the connection settings under configurations.

enter image description here

enter image description here

By adding Oauth connection settings we will get some kind of authentication for different clients for the same authentication URL (website URL).

Able to resolve the issue.

Yes it can be from different tenant.

when we use existing AAD instead of creating from Azure bot template, this issue occurs. Seems like MS Teams is not able to find this AAD/ or Bot Handle.

Root Cause (Might be): Manually created AAD have email address of user who have created this in Owners section (screenshot 1), while AAD created from Azure bot template have "Bot Framework Dev Portal" user (Screenshot 2). And I am unable to add this user by searching.

Screnshot 1 Screenshot1- Manfully created AAD

Screenshot2 Screenshot2

Related