In the modern digital workplace, Microsoft Teams has become the central hub for collaboration. For IT administrators, managing the lifecycle of meeting recordings and transcripts is a critical governance task. While the Microsoft Teams admin center provides a graphical interface for policy management, the true power and granularity lie in PowerShell. Specifically, the cmdlet Set-CsTeamsMeetingPolicy offers a parameter that embodies a significant strategic decision: -RecordingsAndTranscriptsExpirationDays -1 . Using this command to disable the automatic expiration of meeting artifacts is not merely a technical action; it is a declaration of organizational memory policy, balancing the risks of data retention against the benefits of perpetual accessibility. Understanding the Cmdlet and Its Context The Set-CsTeamsMeetingPolicy cmdlet is part of the Skype for Business Online PowerShell module, which manages Teams settings. Among its many parameters—controlling everything from live captions to lobby behavior— -RecordingsAndTranscriptsExpirationDays stands out for its impact on data lifecycle management. By default, Teams recordings and transcripts are stored in OneDrive and SharePoint, where they are subject to automatic deletion after a set period (typically 120 days). This default aligns with data minimization principles, reducing storage costs and legal exposure from stale information. The Meaning of -1 When an administrator executes the command:
# Set expiration to 2 years instead of indefinite Set-CsTeamsMeetingPolicy -Identity "Global" -RecordingsAndTranscriptsExpirationDays 730 If an organization genuinely needs -1 for a subset of users, it should be applied to a custom policy assigned only to specific security groups (e.g., "ComplianceOfficers" or "LegalTeam"), not the Global policy. The PowerShell cmdlet parameter -RecordingsAndTranscriptsExpirationDays -1 is a sharp tool. It disables automatic expiration, effectively telling Microsoft Teams: “Never delete this meeting evidence.” While necessary in niche scenarios requiring perpetual access or awaiting formal retention policies, it should never be a default setting. Administrators who wield -1 must simultaneously implement alternative governance—storage quotas, manual review processes, or retention labels—to prevent their Teams environment from becoming an ungoverned archive. In the balance between data hoarding and data loss, -1 tips the scale completely to one side; use it with deliberation, not convenience. In the modern digital workplace, Microsoft Teams has
This will close in 0 seconds
