chore(kno-10437): Update MS Teams docs regarding multi-tenant bot deprecation#1243
chore(kno-10437): Update MS Teams docs regarding multi-tenant bot deprecation#1243
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| <br /> | ||
| If your bot is registered with Azure as a multi-tenant bot, select “Multi-tenant” in the “Bot type” dropdown. | ||
| Entering an “Entra tenant ID” is not required for multi-tenant bots. | ||
| Entering an “Entra tenant ID” is not required for multi-tenant bots. Note that this applies only to existing legacy multi-tenant bots. New Microsoft Teams bots must be registered as single-tenant in Azure. |
There was a problem hiding this comment.
I went back and forth on whether to include these additional sentences, since this section focuses on entering Teams details in the Knock channel configuration, not on registering the bot with Microsoft Teams. I ultimately included them to make it clear that this does not apply to newly created bots. Open to feedback on whether we should keep this here or remove it and leave the section as-is.
rachael-t
force-pushed
the
rt-kno-10437
branch
from
84c50c0 to
3042d29
Compare
scoti-knock
left a comment
scoti-knock
left a comment
There was a problem hiding this comment.
Added a couple comments. I think we should do something to differentiate the single vs multi-tenant instructions in step 2, but that could be done as a follow up.
| @@ -56,7 +62,7 @@ If you're using a Microsoft Teams bot, follow these steps to configure your bot | |||
| Entra tenant in which your bot is registered. | |||
| <br /> | |||
| If your bot is registered with Azure as a multi-tenant bot, select “Multi-tenant” in the “Bot type” dropdown. | |||
There was a problem hiding this comment.
What do you think about adding an accordion here to better differentiate the single vs multi instructions?
There was a problem hiding this comment.
@scoti-knock I pushed up a change for this, which included moving instructions and screenshot for locating this information in Azure to the top, then putting each type under an accordion. Let me know your thoughts on this update.
3 participants
Description
Updates the MS Teams documenation to call out that multi-tenant bot creation has been deprecated, and that newly created bots must be single-tenant. Clarifies that legacy multi-tenant bots will continue to be supported.
Tasks
KNO-10437