Teams Bot Identification Program

Introduction

AI note-taking and meeting-assistant tools are becoming a familiar part of the Microsoft Teams meeting experience, helping people capture important details while staying present in the conversation. At the same time, organizations need confidence that only intended people and tools are joining their meetings.

To help admins and organizers manage this more effectively, Microsoft Teams is introducing smarter bot protection for meetings. The Teams admin policy, Manage external bots and their access to meetings, helps detect potential external bots, place them in the lobby, clearly identify them for organizers, and require explicit organizer approval before they can join.

This experience gives organizations more visibility and control over automated meeting participants. Even when a meeting allows participants to bypass the lobby, detected bots still require organizer approval before joining. Additional safeguards, such as confirmation prompts and warnings when admitting multiple participants, help reduce accidental bot admission and make bot participation more intentional.

Microsoft Teams Bot Identification Program (coming soon)

Microsoft is also introducing the Teams Bot Identification Program to support independent software vendors (ISVs) that build meeting bot experiences for Teams.

Through this program, eligible bot providers can register with Microsoft and include a self-identification marker in their meeting join requests. When Teams recognizes this marker, it can identify the bot as a known and compliant participant, helping organizers make more informed admission decisions.

The program is designed to create a clearer path for trusted meeting bot experiences while improving transparency for customers. ISVs that build Teams meeting experiences can learn more about the registration and validation process and apply through the public intake page (coming soon).

Support boundaries

Microsoft doesn't provide direct support for ISV-owned bot solutions. If you experience an issue with a third-party bot, contact the ISV first for troubleshooting and support.

If the issue requires Microsoft involvement, the ISV can engage Microsoft through the appropriate partner support channels.