Meeting Bot Detection in Microsoft Teams

Microsoft is rolling out an update to detect external meeting assistant bots attempting to join Teams meetings hosted by the organization.

  • Meeting participants must now complete a second approval step to allow detected bots to join the meeting, improving awareness.
  • Team administrators can configure a new meeting policy setting to update bot access tenant-wide or per user.

This update applies to meeting assistant bots joining from outside the hosting tenant and does not affect internally managed bots or Entra ID applications registered within your own organization’s tenant.

Timeline

The rollout should be completed in June 2026.

How does this affect your users?

Microsoft is introducing bot detection for Teams meetings. When an external meeting bot (primarily an AI assistant) attempts to join a meeting hosted by the organization, Teams should detect it and label the bot as a threat in the meeting lobby. Previously, such a bot was labeled as a normal meeting participant.

A meeting bot is now labeled a threat
A meeting bot is now labeled a threat

When a participant wants to approve the bot from the lobby, Teams now requires an additional confirmation step before the bot is admitted. This should give users more awareness it’s a bot that may record sensitive meeting information.

Approve the bot attendance
Approve the bot attendance

An approved bot remains marked as an unverified participant after being admitted from the lobby.

Remains marked as an unverified participant
Remains marked as an unverified participant

Users are also encouraged to report bots that Microsoft has not yet identified as such. Undetected, external bots can be reported directly from the participants’ panel, which should help improve detection accuracy over time.

How does this affect your Teams administrators?

Bot detection is enabled by default for all tenants. A Teams administrator can update the ExternalBotAccessMode setting in meeting policies, including the option to block all detected bots from joining meetings entirely.

RequireApprovalWhenDetected is the default value
RequireApprovalWhenDetected is the default value

ExternalBotAccessMode
Controls how external third-party automated bots and meeting assistants are handled when they attempt to join meetings. This policy provides predictable behavior and helps organizers apply intentional control for bot participation.

Possible Values:

  • AllowAllBots: Don’t detect bots; allow them to join meetings directly.
  • RequireApprovalWhenDetected: When detected, require approval before joining by routing detected bots to the meeting lobby. This is the default value.
  • BlockDetectedBots: Block detected bots from joining meetings.
PowerShell
Set-CsTeamsMeetingPolicy -Identity "Global" -ExternalBotAccessMode <AllowAllBots | RequireApprovalWhenDetected | BlockDetectedBots>
Share
Avatar photo

Tobias Asböck

Tobias is a Senior System Engineer with more than 10 years of professional experience with Microsoft 365 products such as SharePoint Online, SharePoint Premium, OneDrive for Business, Teams Collaboration, Entra ID, Information Protection, Universal Print, and Microsoft 365 Licensing. He also has 15+ years of experience planning, administering, and operating SharePoint Server environments. Tobias is a PowerShell Scripter with certifications for Microsoft 365 products. In his spare time, Tobias is busy with updates in the Microsoft 365 world or on the road with his road bike and other sports activities. If you have additional questions, please contact me via LinkedIn or [email protected].

Leave a Reply

Your email address will not be published. Required fields are marked *