---
name: Teams Meeting Policy and Recording Governance Audit
description: Audits Microsoft Teams meeting policies for recording permissions, transcription settings, sensitivity label inheritance, and compliance-recording coverage to reduce data exposure from uncontrolled meeting recordings.
---

# Teams Meeting Policy and Recording Governance Audit

> **TL;DR:** This skill audits Microsoft Teams meeting policies to surface recording permission gaps, transcription compliance issues, missing sensitivity label inheritance, and absent compliance-recording coverage, producing a ranked findings table for governance remediation.

## What does the Teams meeting policy and recording governance audit examine?

Microsoft Teams meetings generate significant data-governance risk: recordings stored in OneDrive and SharePoint often land without sensitivity labels, transcription may expose confidential discussions to over-broad audiences, and compliance recording may not capture the regulated conversations it was configured to cover. The 2025-2026 expansion of Teams premium features — including meeting sensitivity labels, intelligent recap, and AI-generated summaries — has widened the governance surface. This skill audits the complete Teams meeting policy configuration, maps each policy to its assigned user groups, identifies gaps in recording permissions, transcription settings, and sensitivity label inheritance, and cross-references against the Microsoft Purview compliance recording configuration to confirm regulated roles are covered.

## When should you run this skill?

- "Audit Teams meeting recording policies"
- "Review who can record Teams meetings"
- "Check if Teams transcriptions are being labelled"
- "Find out if compliance recording is covering our financial advisers"
- "Audit Teams meeting governance before a Copilot rollout"
- "Check sensitivity label inheritance for Teams meetings"

## How this skill works, step by step

1. Connect to Microsoft Teams PowerShell: `Connect-MicrosoftTeams`
2. Enumerate all meeting policies: `Get-CsTeamsMeetingPolicy | Select-Object Identity, AllowCloudRecording, AllowTranscription, AllowRecordingStorageOutsideMicrosoft, RecordingStorageMode, AllowCartCaptionsScheduling, AllowMeetingCoach`
3. For each policy, capture: AllowCloudRecording, AllowTranscription, recording storage location (OneDrive/SharePoint vs third-party), allowed-recording initiators (organiser only vs attendees)
4. Check sensitivity label configuration for Teams meetings: `Get-CsTeamsMeetingConfiguration` — confirm MeetingSensitivityLabelEnabled and DefaultLabelForMeetings
5. Identify policies assigned to regulated-role user groups (financial services, government, legal) and confirm compliance recording policies cover those groups via `Get-CsComplianceRecordingPolicy`
6. Flag gaps:
   - AllowCloudRecording = $true with no sensitivity label enforcement
   - RecordingStorageMode = stream (legacy storage — governance risk)
   - Compliance recording policy not assigned to required regulated roles
   - AllowTranscription = $true with no DLP policy covering transcription output
7. Compute risk per gap: High (regulated role with no compliance recording or no label enforcement), Medium (broad AllowCloudRecording with no label), Low (limited scope policy without transcription controls)
8. Produce the policy table and summary below

## Output format

| Policy Name | Assigned To | Recording Allowed | Recording Storage | Sensitivity Label | Transcription | Compliance Recording | Risk |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Global (default) | All users | Yes | OneDrive | None | Yes | Not assigned | High |
| FinancePolicy | Finance group | Yes | OneDrive | Enforced | Yes | Assigned | Low |

Summary:

- Total meeting policies: N
- Policies with recording enabled: N
- Policies missing sensitivity label enforcement: N
- Regulated roles without compliance recording: N
- Legacy stream storage in use: Yes/No

## Scope and safety

Read-only — this skill does NOT:

- Change meeting policy settings
- Delete or modify recordings
- Enable or configure compliance recording policies

## Licensing and permissions

### Licences and add-ons

| Capability used | Minimum licence |
| --- | --- |
| Teams meeting policy read and enumeration | Microsoft 365 E3 or E5 |
| Compliance recording policy review | Microsoft Teams Premium or Microsoft 365 E5 Compliance |
| Sensitivity label enforcement for Teams meetings | Microsoft 365 E5 Compliance or Microsoft Purview add-on |

### Least-privilege roles

- Teams Administrator (read Teams meeting and compliance recording policies)
- Global Reader (read-only tenant-wide review including policy assignments)

### Microsoft Graph permissions (read-only)

- Teams meeting policies are read via Microsoft Teams PowerShell (`Get-CsTeamsMeetingPolicy`, `Get-CsComplianceRecordingPolicy`)
- `Policy.Read.All` — read policy assignments to users and groups via Microsoft Graph
- `Group.Read.All` — resolve which groups are assigned to each meeting policy

## Sources and compliance

- [Manage meeting policies in Microsoft Teams (Microsoft Learn)](https://learn.microsoft.com/en-us/microsoftteams/meeting-policies-overview)
- [Configure compliance recording in Microsoft Teams (Microsoft Learn)](https://learn.microsoft.com/en-us/microsoftteams/teams-recording-policy)
- [Sensitivity labels for Microsoft Teams meetings (Microsoft Learn)](https://learn.microsoft.com/en-us/purview/sensitivity-labels-meetings)
- Supports Essential Eight ML2 evidence for Control 7 (user application hardening — meeting recording governance)
- Aligns with APRA CPS 234 and ASIC requirements for recording and retaining regulated financial communications
- Pair with Teams Meeting Label Inheritance Check for a complete Teams data-governance picture
- Output in Australian English