Powershell Cmdlet Disable Meeting Recording Transcript Expiration Set To -1 [top] May 2026

Set-CsMeetingRecordingExpirationSetting -Identity "Global" -DaysToKeep 180

In the world of Microsoft Teams administration, data lifecycle management is a tightrope walk between compliance and convenience. By default, Teams meeting recordings are digital ephemera—scheduled for automatic deletion after a set period (typically 60 or 120 days). But every administrator eventually encounters a request that breaks this mold: "Preserve this recording forever. Do not expire it." Do not expire it

Set-CsMeetingRecordingExpirationSetting -Identity "Global" -DaysToKeep $null The -1 flag is not a bug or a hack—it’s a deliberate engineering choice for edge cases. Use it sparingly, document every -1 assignment in your change log, and pair it with a manual review schedule. Otherwise, your “forever” recordings become digital hoarding, buried under the weight of meetings no one will ever rewatch. Because in data governance, can you disable expiration

Because in data governance, can you disable expiration doesn’t always mean you should . But when you truly need it, -1 is the most powerful integer in the PowerShell lexicon. In most programming contexts

Get-CsMeetingRecordingExpirationSetting -Identity "Global"

Enter the command that feels like a backdoor in the space-time continuum of data governance:

At first glance, -1 looks like an error—a phantom parameter. In most programming contexts, negative numbers are invalid for time-based retention. Yet in the Microsoft Teams PowerShell module (specifically the Skype for Business Online Connector), The Anatomy of the Cmdlet The full command in context: