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 as starting points:

| Preset | Typical use | What it locks down | | --- | --- | --- | | All On | Pilot groups, internal power users | Nothing — every feature enabled, for testing | | Kiosk | Shared/lobby devices, meeting-room-only accounts | No scheduling, minimal controls, join-only behaviour | | Restricted Anonymous Access | External-facing or regulated teams | Anonymous join and lobby bypass disabled entirely |

Starting from the closest preset and adjusting a handful of settings is usually faster and less error-prone than building a custom policy from the Global default line by line.

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.

Meeting policy vs meeting template vs meeting type

It's worth keeping three similarly-named things straight. A meeting policy (this page) controls capabilities — what a user is allowed to do. A meeting template controls defaults for a specific scenario (Town Hall, Webinar) — what a new meeting of that type looks like when created, layered on top of whatever the user's policy already permits. A meeting type (regular meeting, Webinar, Town Hall) determines which template and which subset of engagement features (registration, Q&A moderation, reporting) are even available at all — a regular Teams meeting can't retroactively become a webinar's registration-and-reporting experience just by changing policy settings; the organiser has to create it as that meeting type from the start.

Troubleshooting effective policy

The Teams admin center's per-user "effective policy" view is the fastest way to resolve a "why can't this user do X" ticket — it shows exactly which meeting policy applies to that specific user right now, after any group-based assignment, rather than requiring an admin to manually trace group memberships against policy assignments. Two things trip people up repeatedly: assignment order (a user can only have one meeting policy at a time; if they're in multiple groups with different policy assignments, Teams uses a defined precedence, not "most restrictive wins" or "most permissive wins" automatically), and propagation delay (a changed assignment can take several hours to reach the client, so testing immediately after a change and concluding it "didn't work" is a common false alarm). A third source of confusion is that some settings are genuinely locked to the meeting the moment it's scheduled — recording and transcription availability, in particular, reflect the policy in force at scheduling time for that specific meeting series, so a policy change doesn't retroactively apply to meetings already on the calendar; the organiser needs to reschedule or recreate the meeting for the new policy to take visible effect there.