Teams now lets admins send suspected bots to a separate lobby
Reviewed by Helen Jones
Microsoft added a new policy in the Teams admin center. Suspected bots are routed to their own lobby and require explicit organizer approval before joining. The change targets meetings where external or anonymous participants are common. It does not replace existing lobby settings. Configuration sits in the meeting policies section. No additional licensing is required.
Before this update, organizers had one lobby setting that treated every external or unknown participant the same. Admins could not distinguish automated accounts from real guests without watching the participant list in real time. Now a second filter exists that can separate probable bots. The practical effect is limited unless meeting policies are already reviewed regularly and organizers know how to handle extra lobby prompts without creating new support tickets.
Analysis
This is a trap to avoid until you know which Teams already use strict lobby settings and who actually owns them. Audit your current meeting policies first, then decide whether adding another lobby queue reduces risk or just adds friction.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Teams now lets admins send suspected bots to a separate lobby", Collab365 Spaces. 1 source referenced.