Microsoft 365 Retention Policies Licensing: Complete Enterprise Guide

Retention policy licensing is one of the most frequently misconfigured areas of Microsoft 365 compliance deployments. Organisations routinely either over-licence — paying for E5 features when E3 retention policies cover their regulatory requirements — or under-licence, deploying retention labels at scale without validating that every user in scope holds a qualifying licence. The consequences of under-licensing emerged sharply in 2024 when Microsoft's compliance audit team identified retention label deployments where the downstream eDiscovery Premium holds were unlicensed, creating defensibility gaps in active litigation. This guide maps every retention capability to its licence tier and tells you exactly when to upgrade.

Retention Capability Licensing Matrix

Retention Policies vs Retention Labels: The Licensing Distinction

Microsoft Purview offers two distinct mechanisms for retention governance. Understanding the licensing boundary between them prevents the most common deployment errors.

Retention Policies (Container-Level)

Retention policies apply at the workload container level: an Exchange mailbox, a SharePoint site, a OneDrive account, a Teams channel, or a Viva Engage community. Every item within the container inherits the same retention or deletion rule. Retention policies are available at E1 (basic) and full-featured at E3. They are the correct tool for: blanket 7-year email retention for all employees, 3-year retention for all SharePoint content, or Teams channel message deletion after 2 years.

The E3 limitation: retention policies use static scopes — you define the exact mailboxes, sites, or groups at policy creation time. When users are added or leave, the policy must be manually updated. For large, dynamic organisations this creates operational overhead and compliance gaps.

Retention Labels (Item-Level) and Adaptive Scopes

Retention labels are applied at the document or message level, enabling differential retention within a single container. Example: a SharePoint site containing both contract documents (retain 7 years after contract end) and general project files (retain 2 years after project close) cannot be managed with a single policy — it requires labels. Auto-application of labels based on Sensitive Information Types (SITs) or keywords is an E3 feature. Auto-application using trainable classifiers (ML models) requires E5 or E5 Compliance.

Adaptive scopes — the E5-exclusive feature that dynamically targets retention policies based on user attributes (department, location, job title) or site attributes — eliminate the manual overhead of static policy management. For a 10,000-user organisation with 50+ departments each having different retention schedules, the operational value of adaptive scopes is significant: estimated 0.25 FTE reduction in compliance administration, roughly $25,000–$40,000/year in saved staff time.

Litigation Hold: Licensing Requirements and Common Mistakes

Litigation hold preserves all mailbox content for the duration of a legal matter, regardless of user deletion. It is a core eDiscovery preservation mechanism — not a records management tool. Litigation hold requires Exchange Online Plan 2 (standalone: $8/user/month) or Microsoft 365 E3 and above ($36/user/month). It is not available on E1 or Exchange Online Plan 1.

Litigation Hold vs In-Place Hold vs eDiscovery Hold

The most common and costly mistake: organisations running eDiscovery Premium workflows (custodian holds, legal hold notifications) without licencing all custodians for E5 Compliance. Each custodian placed under an eDiscovery Premium hold requires an E5 Compliance licence. In a 50-custodian litigation matter, unlicensed custodians create both compliance risk and potential spoliation exposure. The licence cost per custodian ($144/year) is trivial compared to the legal cost of defensibility challenges.

MRM vs Purview Retention: When to Use Each

Messaging Records Management (MRM) is the legacy Exchange retention system, using retention tags and retention policies applied to mailboxes or folders. Purview retention policies and labels are the current strategic path. Running both simultaneously in the same tenant is common during migrations but creates priority conflicts that require careful management.

Priority Rules When Both Are Active

When MRM and Purview retention both apply to mailbox content, Purview always wins on retention (keep-wins-over-delete). If Purview says retain for 5 years and MRM says delete after 3 years, the content is retained for 5 years. After the Purview retention period expires, MRM deletion actions will apply if the content hasn't been relabelled. This interaction means running both systems during migration creates a predictable behaviour — but decommissioning MRM policies before Purview coverage is complete creates deletion gaps.

Teams Retention: The Compliance Gap Most Organisations Miss

Teams retention requires specific policy configuration that differs from Exchange retention. Teams chat messages are stored in Exchange mailboxes (hidden SubstrateHolds folder) but are managed through Teams-specific retention policies in Purview — Exchange retention policies do not apply to Teams messages. Teams channel messages are stored in SharePoint group mailboxes. Shared channel messages require separate retention policies from standard channel messages. Private channel messages have their own retention policy scope.

The practical implication: an organisation with comprehensive Exchange retention policies covering mailboxes has zero Teams message retention coverage unless Teams-specific policies are separately configured in Purview. Given Teams now processes 300 million daily active users globally and has become the primary communication medium for most enterprise workers, unretained Teams conversations represent a material compliance gap for eDiscovery and regulatory purposes.

Regulatory Records: The Immutable Archive Requirement

The E5-exclusive regulatory records classification makes labelled content immutable from point of application — administrators cannot delete it, and users cannot remove the regulatory label once applied. This classification exists specifically for SEC Rule 17a-4(f) compliance, which requires broker-dealers to maintain electronic records in a non-rewritable, non-erasable format (WORM). Microsoft's third-party assessment from Cohasset Associates confirms that Purview regulatory records meet this requirement for Exchange Online, SharePoint Online, and OneDrive for Business content.

For non-financial-services organisations, regulatory records are appropriate for: documented board resolutions, executed contracts with post-expiry litigation risk, HR disciplinary records with statutory retention requirements, and tax documentation with 7+ year mandatory retention. The operational overhead of regulatory records is significant — once classified, the content cannot be deleted under any circumstance — so careful scoping at policy design stage is essential.

Frequently Asked Questions

What licence is required for Microsoft 365 retention policies?

Basic retention policies (E3 tier) are included with Microsoft 365 E1/E3 and Office 365 E1/E3. Retention labels with advanced features (adaptive scopes, regulatory records, file plan) require E5 or the E5 Compliance add-on. Litigation hold requires E3 and above.

What is the difference between retention policies and retention labels?

Retention policies apply at the container level (mailbox, site, Teams channel) and cannot be applied to individual items. Retention labels apply at the item level, support event-based retention triggers, can be applied by users or automatically, and support disposition review. Labels require E3+; advanced label features require E5.

Do I need E5 for litigation hold?

No. Litigation hold requires Exchange Online Plan 2 or Microsoft 365 E3 and above. eDiscovery Premium (E5) is needed for advanced custodian management and TAR, not for the hold itself.

What are regulatory records and when are they required?

Regulatory records are a Purview retention label classification that makes content immutable — it cannot be deleted even by a global administrator. They require E5 or E5 Compliance. They are required for SEC 17a-4(f) WORM compliance and recommended for content with strict litigation hold requirements.

Can MRM (Exchange Messaging Records Management) replace Purview retention?

MRM handles Exchange mailbox retention only. Purview retention handles multi-workload retention across Exchange, SharePoint, OneDrive, Teams, and Viva Engage. For multi-workload retention governance, Purview is the strategic path. MRM is legacy for Exchange-only scenarios.

What happens if a retention policy and a label conflict?

Retention wins over deletion. If a retention policy says keep for 5 years and a label says delete after 1 year, the content is retained for 5 years. Where two retain-then-delete policies apply, the longer retention period takes precedence.

Are adaptive scopes included in E3?

No. Adaptive scopes require E5 or the E5 Compliance add-on. E3 tenants are limited to static scopes — specific locations, mailboxes, or sites defined at policy creation time.