> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/modules/secure/teams/meeting-policies.md).

# Meeting policies

A **Meeting policy** controls what happens before, during, and after a Teams meeting for the users it's assigned to — who can schedule, who can get in, what they can do once they're in, and what gets recorded. It's one of the five Teams policy types on the **Policies** tab; see Teams for the tab layout, assignment precedence, and template/baseline workflow shared by every policy type.

{% hint style="info" %}
Teams is a licensed feature. If a client isn't authorized for it, the page shows a notice asking you to contact **<sales@augmentt.com>** instead of the usual controls.
{% endhint %}

## Configuration surface

Selecting a meeting policy opens its detail view broken into the same sections as the Teams admin center:

### Policy details

* **Description**

### Scheduling

* **Private meeting scheduling** — whether users can schedule private (1:1 organizer) meetings.
* **Meet now in private meetings**
* **Channel meeting scheduling** — whether users can schedule meetings in a channel.
* **Meet now in channel meetings**
* **Outlook add-in**
* **Meeting registration** — whether registration pages can be turned on for a meeting.
* **Who can register** — *Everyone* or *People in my organization*.
* **Attendance and engagement report**
* **Include attendees in the report** — Always / Never / attendee opt-out or opt-in variants.
* **Attendee information** — *Show everything* or *Only show who attended*.

### Meeting join and lobby

* **Anonymous users can join a meeting**
* **Anonymous users and dial-in callers can start a meeting**
* **Who can bypass the lobby** — Everyone / People in my org and guests / People in my org, trusted orgs, and guests / People in my org / Organizers, co-organizers, and presenters / Organizers and co-organizers only, and related variants.
* **People dialing in can bypass the lobby**
* **People can join external meetings hosted by** — Any org / Trusted orgs and guests / No other orgs.
* **Blocked anonymous join client types**

### Meeting engagement

* **Meeting chat** — On for everyone / On for everyone but anonymous users / In-meeting only (for everyone, or except anonymous users) / Off.
* **Lobby chat** — only selectable when meeting chat isn't off or in-meeting-only (see validation note below).
* **External meeting chat**
* **Q\&A**
* **Reactions**
* **Streaming attendee mode**
* **Attendee identity masking** — Distinguish speakers / Attribute speakers.

### Content sharing

* **Who can present** — Everyone / Everyone but organizers can change this / People in my org / Only organizers and co-organizers / Organizers, co-organizers, and presenters.
* **Screen sharing** — Entire screen / Single application / Not enabled.
* **Participants can give or request control**
* **External participants can give or request control**
* **PowerPoint Live**
* **Whiteboard**
* **Collaborative annotations**
* **Live Share** (document collaboration)
* **Shared notes**
* **Restrict copying or forwarding meeting chat messages**
* **Participants can share content in external meetings hosted by** — same Any org / Trusted orgs and guests / No other orgs set as join.
* **Meeting coach**

### Meeting protection

* **Watermark videos** (camera video watermarking)
* **Watermark shared content** (screen-sharing watermarking)

### Recording and transcription

* **Meeting recording** — cloud recording on/off; this is also a dependency gate (see below).
* **Require participant agreement for recording and transcription**
* **Default recording expiration (days)**
* **Store recordings outside of your country or region** — only selectable when meeting recording is on.
* **Transcription**
* **Live captions**
* **Copilot**
* **Channel recording download**
* **CART captions scheduling**
* **User enrollment override**
* **Live interpretation**
* **Meeting invite languages** — a large fixed list of locale codes (e.g. `en-US`, `fr-CA`, `ja-JP`, `zh-CN`) plus "No second language."
* **Speaker attribution**
* **Room attribute override**

### Audio and video

* **Mode for IP audio** / **Mode for IP video**
* **Video conferencing** (IP video)
* **Broadcast production with NDI and SDI hardware**
* **Media bit rate (Kbps)**
* **Network configuration lookup**
* **Participants can use video effects** — Only background blur / Only background blur and default backgrounds / All video effects / Not enabled.
* **Live streaming**
* **Allowed streaming media input**
* **Breakout rooms**
* **Preferred meeting provider** (Islands mode)
* **Far-end camera controls** (PTZ)
* **Voice isolation**

{% hint style="info" %}
This list matches Microsoft's meeting-policy reference and is deliberately curated — the Teams cmdlet returns additional internal and legacy fields Augmentt doesn't surface. A handful of newer fields (Copilot auto-start, external bot access, synthetic media detection, CAPTCHA verification, real-time text, and similar) exist in Augmentt's write schema but aren't yet exposed in this section layout.
{% endhint %}

{% hint style="warning" %}
Two settings are validated against each other before a save is accepted: **Lobby chat** can't be On when Meeting chat is Off or limited to during the meeting, and **Store recordings outside of your country or region** can't be On when Meeting recording is Off.
{% endhint %}

## Built-in and default policies

Microsoft ships six built-in meeting policies that a tenant already has before Augmentt ever writes to it — `AllOff`, `AllOn`, `Default`, `Kiosk`, `RestrictedAnonymousAccess`, and `RestrictedAnonymousNoRecording`. Augmentt recognizes all six as Microsoft-managed: they show up in the Policies list like any other policy, but **Edit** and **Delete** are disabled with an explanation instead of being sent to Microsoft and failing. `Global` is the tenant's baseline custom policy and also can't be deleted.

Augmentt itself doesn't ship any preset meeting policy content of its own — there's no seed/migration data defining an Augmentt-authored meeting policy template. Every **Policy Template** you see in the Templates tab is one an MSP created by picking an existing tenant policy (a Microsoft built-in or a custom one) and saving its settings under a name — see Templates and Baselines.

## Posture-check resolution

There's no dedicated posture/compliance check that maps to Teams meeting-policy settings specifically. The one Teams-related item in Augmentt's Secure Score / Compliance Audit catalog is **Teams Default External/Guest Options** (`teamsdefaultexternaloptions`), which evaluates the tenant-wide **External access** and **guest** configuration (federation, guest meeting/messaging/calling permissions) — not per-policy meeting settings. See External access and Settings for where that check's target fields live. Meeting-policy content like recording consent, watermarking, or lobby behavior isn't currently scored by any Secure Score, CIS, CMMC, or Maester check Augmentt evaluates.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.augmentt.com/modules/secure/teams/meeting-policies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.