Microsoft Teams meeting policies

Meeting policies in Microsoft Teams are the admin controls that govern what happens before, during, and after a meeting. They're assigned per user (or via group assignment) from the Teams admin center, and they're the right lever for almost any "can we lock down…" question.

What a meeting policy controls

A single meeting policy aggregates dozens of settings. The main groups:

• General — Meet Now in channels, scheduling permissions, channel meeting scheduling, Outlook add-in.
• Audio & video — IP audio and video, transcription, recording (cloud), live captions, language interpretation.
• Content sharing — screen sharing mode (entire screen vs window only), PowerPoint Live, whiteboard, shared notes, external participants giving control.
• Participants & guests — anonymous join, anonymous starting a meeting, "who can present" defaults, who can bypass the lobby, chat in meetings.
• Engagement — Q&A, reactions, polls.
• Watermarking — adds a watermark to shared content for confidential meetings (Teams Premium).

Default policies and overrides

Every tenant has a Global (Org-wide default) meeting policy that applies to everyone unless overridden. Custom policies can be created and assigned to individual users or groups. Microsoft ships several preset policies — Kiosk, Restricted Anonymous Access, All On — as starting points.

Settings vs policies

Don't confuse Meeting policies (per-user, what users can do) with Meeting settings (tenant-wide, defaults for things like anonymous join domains, customisable meeting URL, QoS markers). Both live in the same admin nav and both affect meetings, but they apply at different scopes.

Practical baselines

A reasonable baseline for most organisations:

• Cloud recording on for everyone, with retention via a Purview policy.
• Transcription on (required for Copilot meeting recap).
• Anonymous join on, but anonymous users must wait in the lobby unless explicitly admitted.
• Who can present default to specific people, not "Everyone."
• Chat in meetings enabled with history retained for the meeting only.

Adjust from there for high-security teams (executives, regulated functions) with a stricter custom policy.

Setting these once and forgetting them is one of the highest-leverage things an admin can do — every meeting in the tenant benefits forever.