In Microsoft 365, Microsoft Teams meeting recordings (TMR) are automatically stored in Microsoft OneDrive (for 1:1 and private group meetings) or SharePoint Online (for channel meetings). To prevent runaway cloud storage consumption and satisfy organizational compliance lifecycle requirements, Microsoft Teams enforces an automated recording expiration policy. By default, new recordings expire after 60 or 120 days depending on tenant licensing. System administrators can customize, extend, or disable automatic expiration across the organization or per user group using the Microsoft Teams PowerShell module.
Understanding Teams Meeting Recording Expiration Architecture
Meeting recording expiration is managed under the CsTeamsMeetingPolicy policy schema. The behaviour is governed by two core attributes:
NewMeetingRecordingExpirationDays: An integer representing the retention lifespan in days before a recorded file is automatically moved to the user’s or SharePoint site’s Recycle Bin. Standard defaults range between 60 and 120 days, but can be set between 1 and 99,999 days, or set to-1.-1(Never Expire): Configuring this value completely disables automatic deletion for recordings initiated by users assigned to the policy.
Important Note: Microsoft Purview retention policies and legal hold configurations always take precedence over Teams meeting recording expiration settings. If a Purview retention lock is active, the recording remains preserved in the Preservation Hold library even after the Teams expiration date elapses.
Connecting to Microsoft Teams PowerShell
To inspect and configure tenant meeting recording policies, open an elevated PowerShell console and connect using administrative credentials:
Install-Module -Name MicrosoftTeams -Force -AllowClobber
Import-Module MicrosoftTeams
Connect-MicrosoftTeams
Auditing Existing Meeting Recording Expiration Policies
Before applying modifications, query your existing global (tenant-wide default) and custom meeting policies to evaluate current expiration rules:
Get-CsTeamsMeetingPolicy | Select-Object Identity, NewMeetingRecordingExpirationDays
To view the detailed configuration of the global policy alone:
Get-CsTeamsMeetingPolicy -Identity Global | Format-List Identity, Description, NewMeetingRecordingExpirationDays
Configuring Tenant-Wide Recording Expiration
1. Setting a Custom Expiration Window (e.g., 30 Days)
To reduce storage overhead and enforce a 30-day lifecycle for all standard tenant users under the Global policy:
Set-CsTeamsMeetingPolicy -Identity Global -NewMeetingRecordingExpirationDays 30
2. Disabling Expiration (Never Expire)
If your organization relies strictly on Microsoft Purview compliance labels and does not want Teams to execute automated deletion:
Set-CsTeamsMeetingPolicy -Identity Global -NewMeetingRecordingExpirationDays -1
Creating and Assigning Custom Expiration Policies
In enterprise scenarios, different business units require tailored retention terms. For example, executive or legal teams may require 180-day retention, while temporary contractors should have recordings expire after 14 days.
1. Create a New Policy for Extended Retention
New-CsTeamsMeetingPolicy -Identity "Executive-Extended-Retention" -NewMeetingRecordingExpirationDays 180 -Description "Retention policy for executive board recordings"
2. Assign the Policy to an Individual User
Grant-CsTeamsMeetingPolicy -Identity "[email protected]" -PolicyName "Executive-Extended-Retention"
3. Assign the Policy via Azure AD Group (Bulk Assignment)
$groupId = (Get-AzureADGroup -SearchString "Executive Leadership").ObjectId
New-CsGroupPolicyAssignment -GroupId $groupId -PolicyType TeamsMeetingPolicy -PolicyName "Executive-Extended-Retention" -Rank 1
Verifying User Policy Resolution
To confirm which recording expiration rule is effective for a specific employee, query their assigned policy state:
Get-CsUserPolicyAssignment -Identity "[email protected]" -PolicyType TeamsMeetingPolicy
End-User Experience and File Lifecycle Impact
When an expiration timeframe is reached:
- The meeting recording video file is automatically moved to the owner’s OneDrive or SharePoint Recycle Bin.
- The recording owner receives an automated email notification detailing the expiration, with a direct link to restore the file from the Recycle Bin if needed.
- Files remain in the Recycle Bin according to standard SharePoint/OneDrive retention rules (typically 93 days) before permanent purging.
Configuring meeting recording expiration through PowerShell ensures compliance with governance guidelines while preventing costly cloud storage overages across Microsoft 365 environments.