Skip to content

Conversation

@rachael-t
Copy link
Contributor

@rachael-t rachael-t commented Dec 30, 2025

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

@linear
Copy link

linear bot commented Dec 30, 2025

@vercel
Copy link

vercel bot commented Dec 30, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docs Ready Ready Preview, Comment Jan 13, 2026 7:10pm

<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.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

@scoti-knock scoti-knock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Then, in the “Entra tenant ID” text field, enter the ID of the Microsoft
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about adding an accordion here to better differentiate the single vs multi instructions?
Image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.
Screenshot 2026-01-13 at 1 34 28 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants