Microsoft Teams: Recordings Expire Soon

Key insights

• Video context: This YouTube video answers a viewer question about using Teams recordings in the desktop app versus a browser view.
  It explains recent changes to how Microsoft handles meeting recording expiration and why some settings behave differently in the app.
• Default expiration: 120 days: Teams recordings save to OneDrive/SharePoint and, by default, expire after 120 days from the recording date.
  After expiration, the file is removed from active storage to help control storage growth.
• Admin controls and PowerShell: Admins can change or disable expiration from the Teams admin center or with PowerShell (for example: Set-CsTeamsMeetingPolicy -Identity Global -NewMeetingRecordingExpirationDays 99999).
  New settings apply to recordings created after the change; existing files keep their original dates unless updated.
• User-level control: Meeting organizers and co-organizers with edit rights can extend or remove expiration for recordings they own, or set specific dates (options often include 7, 30, or 60 day extensions).
  This gives teams flexibility without needing full admin changes.
• Retention policy precedence (Microsoft Purview): If an organization applies a retention policy via Microsoft Purview, that policy overrides Teams expiration settings and preserves recordings for the required period.
  This ensures legal or compliance needs take priority over automatic deletion.
• Edge cases and recovery: Recurring meetings and channel meetings may not inherit new expiration changes automatically, so admins may need to update them manually.
  Expired files typically move to the recycle bin and can be recovered for a limited window (commonly up to 90 days) depending on tenant settings.

In a recent YouTube video, Darrell Webster, who identifies himself as Modern Work Mentor, answers a viewer question about meeting recordings in Microsoft Teams. The viewer, credited in the video as JacquiQUINLAN, asked whether recordings can still be managed from the Teams app after her organization stopped allowing the web view. Consequently, Webster walks through how recordings are stored, how expiration works, and what administrators and users can do to control retention.

Overview of Teams Recording Storage

First, Webster explains that Teams meeting recordings are saved automatically to either OneDrive or SharePoint, depending on how the meeting is set up. By default, these recordings are set to expire after a set period to help organizations manage storage and data lifecycle. Furthermore, the video clarifies that expiration is a separate mechanism from retention policies, and that each serves a different purpose in governance and compliance.

In addition, the presenter stresses that expiration supports routine cleanup and cost control, while retention policies ensure legal or regulatory obligations are met. For users, this means an expired file can often be recovered from the recycle bin for a limited time, which reduces the risk of accidental permanent loss. However, Webster notes that the details of recovery windows depend on tenant settings and the underlying storage service.

How Expiration and Controls Work

Webster outlines the basics: Teams recordings typically expire after 120 days by default, but administrators can change that default in the Teams admin center or with PowerShell. Meeting organizers and co-organizers also have the ability to modify expiration dates for recordings they own when they have edit permissions in OneDrive or SharePoint. Moreover, administrators can set organization-wide defaults that apply to new recordings going forward.

He emphasizes that changes to a global default do not retroactively alter existing recordings, so organizations may need to update older files manually if they want a consistent policy across the tenant. Meanwhile, Webster highlights that Microsoft Purview retention policies take precedence over Teams expiration settings, which means retention rules can keep content for a mandated period even when expiration would otherwise remove it.

Recent Changes Highlighted in the Video

Importantly, Webster points out several recent updates that give both admins and users more control. Administrators can now set a global default expiration period for all new recordings and, as an extreme example, set expiration to a very high value to effectively disable it; this is achievable with a Teams meeting policy change. Likewise, recording owners can extend or remove expirations directly from the file page in OneDrive or SharePoint, choosing options such as adding days or setting a specific date.

Additionally, the video clarifies the precedence of retention policies, explaining that a Microsoft Purview retention rule will override Teams expiration, thereby ensuring compliance requirements are met. Webster also flags a practical wrinkle: recurring meetings and channel recordings sometimes do not automatically adopt new policy settings, and administrators may need to update those items individually. Consequently, tenants with many recurring or channel meetings should plan for extra administrative effort to harmonize settings.

Finally, Webster addresses the user experience when the Teams desktop or mobile app cannot open recordings in a browser view due to organizational controls. He walks viewers through how to manage recordings directly from the storage location, which remains accessible even when the web-based player is blocked, provided the user has appropriate permissions.

Tradeoffs and Operational Challenges

The video also explores tradeoffs that organizations face when adjusting expiration and retention. For example, increasing retention or disabling expiration reduces the risk of losing important content, but it raises storage costs and increases the volume of data to govern. Conversely, enforcing short expirations saves storage and simplifies housekeeping, yet it can frustrate users and complicate compliance if essential records are removed too soon.

Webster highlights operational challenges such as inconsistent settings across existing recordings, the need for PowerShell or admin center work to apply changes at scale, and the special-case behavior of recurring and channel meetings. Moreover, he points out how organizational restrictions on web views can make the user experience less intuitive, thereby increasing support requests and training needs. Therefore, tenants must weigh the administrative overhead against user productivity and legal obligations.

Practical Recommendations from the Video

To balance these factors, Webster recommends that organizations first audit their recording inventory and then align expiration and retention settings with business needs and compliance rules. He advises creating a clear policy that specifies default expiration, exceptions, and the process for extending or removing expiration on a recording-by-recording basis. Additionally, he suggests documenting any PowerShell commands or admin steps needed to update large numbers of files so that changes are repeatable and auditable.

Lastly, Webster encourages communication and user training so that meeting organizers understand how to manage their recordings and where to recover expired files when necessary. By combining thoughtful default settings, targeted retention rules through Microsoft Purview, and user education, organizations can reduce surprises while keeping control over data growth. In short, the video offers practical guidance that helps admins and users navigate the tradeoffs between storage efficiency, accessibility, and compliance.

Keywords

Microsoft Teams meeting recordings expire, Teams recording expiration, How long do Teams recordings last, Change Teams recording retention, Extend Teams meeting recordings, Prevent Teams recording deletion, Teams cloud recording retention policy, Microsoft Teams recording retention settings