meeting policies

Microsoft Teams administrators should treat the retirement of the old CAPTCHA policy as a workflow-design deadline, not a cosmetic policy cleanup: any unattended third-party meeting assistant that is detected as an external bot can now be held in the lobby until a person admits it. Before the...

Microsoft Teams administrators should place most organizers on RequireApprovalWhenDetected, use BlockDetectedBots for organizers of sensitive meetings, and grant AllowAllBots only as a reviewed exception for unattended workflows. WindowsForum reports on the rollout describe the practical change...

Microsoft Teams is rolling out an admin-controlled external bot detection system in 2026 that routes suspected third-party meeting bots into the lobby, requires explicit organizer approval, and begins replacing CAPTCHA-based join verification across Teams meetings. The change is not just another...

Microsoft Teams now lets admins manage detected external meeting bots by policy, placing suspected bots in the lobby for organizer approval even when the meeting’s normal lobby setting would otherwise allow bypass. Before enabling or expanding the protection, admins should test legitimate...