Compliance

Retention labels

Microsoft Purview retention labels

Microsoft Purview retention labels are the mechanism within Microsoft Purview for applying records management and information lifecycle rules to content across Exchange Online, SharePoint, OneDrive, Teams, and Viva Engage.

Why Retention labels matters in a Microsoft estate

Retention labels matters because customers, resellers, and procurement teams need evidence that controls are defined, operated, and reviewable. A useful glossary definition should help a reader connect the term to audit preparation, policy work, or repeatable assurance activity.

How Retention labels shows up in practice

They determine how long that content must be retained before it can be deleted, and whether it should be automatically disposed of after a defined period. Where required, they can also mark content as a formal record subject to stricter controls that prevent it being edited, moved, or deleted even by users who would otherwise have permission to do so. A label can be configured to retain content only, to delete it after a defined retention period with no retention requirement, or to do both, retain then delete. The underlying trigger for that period can be based on when the content was created, when it was last modified, or, for more sophisticated scenarios, an event such as an employee's departure or a contract's end date.

This lets retention periods reflect genuinely event-driven business and regulatory requirements, rather than only fixed time windows from creation. Labels can be applied manually by end users, published as available options in Outlook and SharePoint, or applied automatically based on a retention label policy targeting specific locations. They can also be applied automatically based on trainable classifiers or sensitive information type matches that detect content meeting defined criteria, such as content containing particular regulatory-relevant data, without relying on users to remember to label it themselves.

Retention labels interact directly with eDiscovery and legal holds: content under an active hold is preserved regardless of what its retention label says. Purview generally resolves conflicting retention requirements by preserving content longer whenever multiple policies or holds disagree about disposition, which is a deliberate design choice to avoid content being deleted prematurely. For organisations building a records retention schedule to satisfy ISO/IEC 27001's records management expectations, UK GDPR's storage limitation principle, or sector-specific regulatory retention periods, retention labels are typically how that documented schedule is actually implemented in the tenant, rather than remaining a policy document with no operational effect.

Disposition review, where content reaching the end of its defined retention period is routed to a reviewer for a final delete-or-extend decision rather than deleted automatically, is a commonly used control for anything where an automatic irreversible deletion carries real risk. A frequent operational challenge is label sprawl and policy conflict. Taxonomies that grow to dozens of overlapping labels with unclear ownership become difficult for end users to apply correctly and difficult for administrators to audit. Because auto-apply policies and manual labels can coexist on the same content, unexpected retention outcomes are usually traceable to a policy precedence or scope conflict, which needs the tenant's overall label and policy set reviewed as a whole rather than treating any single symptom in isolation.

Glossary