The KUDO bot joins Microsoft Teams meetings as an external guest. Your organization's Teams meeting policies decide whether the bot waits in the lobby until someone admits it. Use this guide to check how your policies treat the KUDO bot.

This guide is for Microsoft Teams administrators.

What KUDO needs in Teams

• App approval: If your organization requires apps to be approved, approve the KUDO app before hosts can add it to meetings. See Why do I need to validate the KUDO app in Teams before first use?
• No tenant permissions for the bot: The KUDO bot doesn't require Microsoft tenant-level permissions. Teams detects it as an external bot, and your external-bot policy decides whether it must be admitted from the lobby.

Review your external-bot policy

1. In the Teams admin center, open the meeting policy that applies to your meeting organizers.
2. Go to the Meeting join and lobby section.
3. Find Manage external bots and their access to meetings and review the selected option.

You can also change this setting in PowerShell with the -ExternalBotAccessMode parameter. Use RequireApprovalWhenDetected for the default behavior or AllowBots to turn off bot detection. For the current cmdlet and Microsoft's recommendations, see Manage external bots and their access to meetings.

Note: Microsoft recommends keeping the default setting and allowing only organizers and co-organizers to admit people from the lobby.

If you keep the default policy

Hosts must admit the KUDO bot from the lobby before each meeting. Make sure the people who run KUDO meetings can admit people from the lobby. The admission steps for hosts are in Set up a Teams meeting with the KUDO bot.

Related content

• Set up a Teams meeting with the KUDO bot
• Why do I need to validate the KUDO app in Teams before first use?
• Manage external bots and their access to meetings (Microsoft)