The settingWhat we hold this to
CreativeTechs minimum
Meeting policy: Who can bypass the lobby = People who were invited (or more restrictive). Anonymous users can start a meeting = Off. External participants can give or request control = Off. Chat with unmanaged Teams users = Off.
Benchmark position
CIS M365 8.5.3 (L1) — recommended state 'People who were invited' or more restrictive. Our minimum is exactly the CIS figure.
Where the switch is
Teams admin centre → Meetings → Meeting policies → Global (Org-wide default) → Participants & guests.
How to verify
Get-CsTeamsMeetingPolicy -Identity Global | fl AutoAdmittedUsers,AllowAnonymousUsersToStartMeeting,AllowExternalParticipantGiveRequestControl
- Why it matters
- Lobby bypass, anonymous meeting starts and unmanaged external chat are the Teams-side equivalent of anonymous sharing links — an open door that doesn't look like one.
- How we check
- Huntress carries a dozen of these across the Teams category. CIS.M365.8.5.3 · L1, Maester MT.1042 / 1046 / 1047.
- Fix — M365
- Teams admin → meeting policies: only org members bypass the lobby, anonymous users can't start meetings, external participants can't request control; restrict chat with unmanaged Teams users.
- Fix — Google
- Meet host management settings.
- User notices
- External guests wait in a lobby until admitted.
- Expected pushback
- Moderate at agencies running client calls all day — the lobby is the friction point. Consider letting trusted federated domains through rather than switching it off.
