Teams meeting recording management

When Teams meetings are recorded, the recordings are video files stored in Microsoft 365 — not in a separate "Stream" system anymore. Knowing where they live, who can see them, how long they're kept, and how to find them later matters for compliance, governance, and discovery.

Where recordings live

Recording storage depends on meeting type:

• Non-channel meetings (scheduled or ad-hoc, not in a Teams channel) — saved to the organiser's OneDrive, in a Recordings folder.
• Channel meetings (held in a Teams channel) — saved to the channel's SharePoint site, in a Recordings folder in the channel's files area.

Permissions inherit from the storage location:

• Non-channel meeting recording → meeting attendees and the organiser can access (with sharing links automatically set up).
• Channel meeting recording → channel members can access.

What's saved

• The video file (.mp4).
• An accompanying transcript (if transcription was enabled).
• Closed-caption files.
• Chapters / table-of-contents metadata.
• AI-generated meeting recap content (if Microsoft 365 Copilot was active).

The transcript is critical for searchability and for Microsoft 365 Copilot's meeting recap functionality. Without transcription, Copilot can't summarise post-meeting.

Retention

By default, meeting recordings have no retention policy — they stay until explicitly deleted. This produces accumulation problems for organisations with high meeting volume.

Configure retention via Microsoft Purview retention policies targeting the storage locations:

• OneDrive retention for non-channel meeting recordings.
• SharePoint site retention for channel meeting recordings.
• Specific Teams meeting message retention for in-meeting chat (separately).

A typical baseline: retain meeting recordings 60–90 days, then auto-delete. For specific compliance scenarios (financial services regulated calls), retain 7+ years.

Alternative: OneDrive admin centre's auto-delete for meeting recordings — a simpler setting if your only requirement is "delete recordings after N days."

Discovery and search

Recorded meetings appear in Microsoft Search results like any file. Users can search:

• By meeting title.
• By content within the transcript — search for specific phrases said during the meeting.
• By speaker — find meetings where specific people spoke (limited support).
• By participant — meetings the user attended.

For analysts or compliance officers needing systematic recording review, the Defender XDR / Purview interfaces can aggregate.

Compliance scenarios

For regulated industries needing call recording beyond ad-hoc meeting recording:

• Compliance recording via Teams certified partners (Verint, NICE, Theta Lake, others) captures all Teams voice and video for specific users (traders, advisors). Different mechanism from meeting recording.
• Information protection — sensitivity labels applied to meetings can govern recording behaviour and access.

End-user behaviour

The meeting recording capability surfaces to users as:

• A Record button during the meeting.
• Automatic recording start if the meeting policy requires it.
• A recording-started notification for all attendees.
• A recording link posted to the meeting chat after the meeting ends.

Educate users that:

• Recordings show in their chat history for easy access.
• The recording link is also in their or the organiser's OneDrive / SharePoint.
• They can rename, download, share, or delete the recording.

Admin controls

In the Teams admin centre → Meeting policies:

• Allow cloud recording — on / off, per user policy.
• Allow transcription — on / off (essential for Copilot meeting recap).
• Automatic transcription — start transcription automatically for all meetings.
• Storage location — fixed by meeting type, but admin can verify settings.

In the Microsoft 365 admin centre:

• OneDrive defaults including auto-delete for meeting recordings.
• SharePoint defaults for channel meeting storage.

Common operational issues

• Recordings filling OneDrive storage — without retention, organiser quotas grow unboundedly.
• Lost recordings after employee departure — recordings in the departed employee's OneDrive may be inaccessible unless ownership transferred.
• Sensitivity label inheritance — labels on the underlying meeting affect the recording.
• Channel recording orphaned — if the team is deleted, recordings go with it.

For organisations running Teams as a meeting platform at scale, recording governance is one of those "obvious in hindsight" investments. Set retention policies; communicate to users; audit periodically.