Study guide
16.2 Retention Labels & Policies
Microsoft 365 Administrator Expert MS-102
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 MS-102 Exam Facts & Blueprint 1.2 Registration, Retake & Renewal 1.3 Study Strategy & Using This Guide
2 Tenant Setup, Domains & Org Settings
2.1 Creating a Microsoft 365 Tenant 2.2 Implementing and Managing Domains 2.3 Configuring Org Settings: Security, Privacy & Profile
3 Service Health, Network & Software Updates
3.1 Monitoring Service Health & Notifications 3.2 Network Connectivity Insights 3.3 Configuring & Monitoring Software Updates
4 Adoption, Usage & Microsoft 365 Backup
4.1 Monitoring Adoption & Usage 4.2 Configuring & Managing Microsoft 365 Backup
5 Users, Contacts, Groups & Shared Mailboxes
5.1 Creating & Managing Users Including External Users 5.2 Creating & Managing Contacts 5.3 Managing Microsoft 365 Groups & Shared Mailboxes
6 Licensing & Bulk User Management
6.1 Managing & Monitoring Microsoft 365 Licenses 6.2 Bulk User Management with Graph & Entra PowerShell
7 Roles, Admin Units & Privileged Identity Management
7.1 Implementing & Managing Roles in M365 & Entra ID 7.2 Managing Permissions for Defender XDR, Purview & Workloads 7.3 Managing Delegation with Administrative Units 7.4 Managing Entra ID Roles in PIM
8 Identity Synchronization with Entra Connect
8.1 Preparing for Identity Synchronization & IdFix 8.2 Directory Sync with Entra Connect Sync & Cloud Sync 8.3 Monitoring Sync with Entra Connect Health 8.4 Troubleshooting Synchronization
9 Authentication, SSPR & Password Protection
9.1 Implementing & Managing Authentication Methods 9.2 Self-Service Password Reset (SSPR) 9.3 Microsoft Entra Password Protection 9.4 Investigating & Resolving Authentication Issues
10 Identity Protection, Conditional Access & MFA
10.1 Planning for Identity Protection 10.2 Implementing Entra Identity Protection 10.3 Planning & Implementing Conditional Access Policies 10.4 Managing MFA with Conditional Access
11 Defender XDR Posture, Incidents & Threat Intelligence
11.1 Security Exposure Management & Secure Score 11.2 Incidents, Alerts & Advanced Hunting 11.3 Reviewing Defender XDR Reports 11.4 Defender Threat Intelligence
12 Defender for Office 365: Policies, Alerts & Investigation
12.1 Threat Policies & Rules in Defender for Office 365 12.2 Configuring Alert Policies 12.3 Investigating & Responding to Email Threats
13 Attack Simulation & Restricted Entities
13.1 Managing Attack Simulations & Training 13.2 Managing Restricted Entities & Blocked Users
14 Defender for Endpoint
14.1 Onboarding Devices to Defender for Endpoint 14.2 Configuring Endpoint Settings 14.3 Defender Vulnerability Management Dashboard
15 Defender for Cloud Apps
15.1 Configuring the App Connector for Microsoft 365 15.2 Defender for Cloud Apps Policies & Alerts 15.3 Interpreting the Activity Log 15.4 Cloud App Discovery
16 Purview Information Protection & Data Lifecycle
16.1 Sensitive Information Types 16.2 Retention Labels & Policies 16.3 Sensitivity Labels & Policies 16.4 Monitoring Label Usage: Content & Activity Explorer
17 Purview Data Loss Prevention
17.1 DLP Policies for Microsoft 365 Workloads 17.2 Configuring Endpoint DLP 17.3 Reviewing & Responding to DLP Alerts, Events & Reports
18 Final Review & Exam Strategy
18.1 Exam-Day Strategy & Question Handling 18.2 Final Review Checklist & Next Steps
16.2 Retention Labels & Policies
Key Takeaways Explain This Topic AI
Retention policies apply at the container/location level (all Exchange mailboxes, all SharePoint sites, all OneDrive, all Teams chats) while retention labels apply per-item
Retention settings are retain-then-delete, delete-only, and retain-only; the retention period and end-of-retention action (delete, disposition review, or move to archive) are configured per policy or label
Auto-apply retention label policies use conditions including sensitive info types, trainable classifiers, keywords/KQL queries, and cloud attachments
Disposition reviews let a reviewer decide whether to permanently delete, extend, or relabel items at the end of the retention period
Retention governs how long content is kept and deleted; sensitivity labels govern protection and classification — the two are separate Purview features that can apply to the same item
Last updated: August 2026
Quick Answer: Retention in Microsoft Purview is delivered through two objects: retention policies that apply at the location level (all Exchange mailboxes, all SharePoint sites, all OneDrive accounts, all Teams chats) and retention labels that apply per-item, either manually or automatically. Retention settings determine whether content is retained then deleted, deleted only, or retained only, and what happens at the end of the retention period.
Data Lifecycle Management in Purview
Data lifecycle management is the Purview discipline that governs how long content is kept and when it is deleted. Most organizations face two opposing pressures: legal and regulatory requirements to keep content for a minimum period, and risk-reduction goals to delete content when it is no longer needed. Retention policies and retention labels operationalize both goals.
Retention Policy vs Retention Label vs Label Policy
These three objects are easy to confuse on the MS-102 exam. The table below distinguishes them.
Object Scope How applied Typical use
Retention policy Container/location Automatically to an entire location (all Exchange mailboxes, all SharePoint sites, all OneDrive, Teams chats/channel messages) Broad baseline retention, e.g., keep all Teams chats for 3 years then delete
Retention label Per-item Manual by users in Outlook/Word/SharePoint, or automatic via an auto-apply policy Specific retention for a class of content, e.g., keep employee contracts 7 years
Retention label policy Users/groups or locations Publishes labels so users see them, or auto-applies labels based on conditions The delivery mechanism for retention labels; a label has no effect until published through a policy
A retention label by itself is just a definition. The label must be published through a retention label policy for users to apply it manually, or through an auto-apply retention label policy for Purview to apply it automatically based on conditions.
Retention Settings
Retention policies and retention labels both offer the same retention settings:
Retain-then-delete — keep the content for a specified period, then delete it. The most common setting for compliance-driven content.
Delete-only — delete the content after a specified age; no retention guarantee. Useful for routine content that should age out.
Retain-only — keep the content indefinitely or for a specified period without deleting it; the user cannot delete it during the retention period.
When you configure retain-then-delete, you also choose what happens at the end of the retention period :
Delete automatically — Purview deletes the item.
Disposition review — a designated reviewer inspects the item and chooses to permanently delete, extend the retention, or relabel it.
Move to archive — for Exchange mailboxes, the item is moved to the archive mailbox at the end of the period.
Adaptive vs Org-Wide Scope
Retention policies can be org-wide (apply to all instances of a location, such as all Exchange mailboxes) or scoped to specific recipients. Adaptive policy scopes use attributes and properties to define the scope dynamically, so that new mailboxes, sites, or users that match the attributes are added automatically without you editing the policy. For example, an adaptive scope can target all users whose department attribute equals "Engineering". Adaptive scopes require Azure AD (Entra ID) attributes or SharePoint site properties to filter on.
Auto-Apply Retention Label Conditions
An auto-apply retention label policy applies a retention label to content that matches conditions you define. The supported conditions are:
Sensitive info types — apply the label when content contains a SIT match (e.g., a credit card SIT triggers a 7-year retention label)
Trainable classifiers — apply the label when content matches a trainable classifier such as Source Code, HR documents, or Legal documents
Keywords or KQL queries — apply the label based on a keyword query or Keyword Query Language expression
Cloud attachments — apply the label when files are shared as cloud attachments in Exchange or Teams (a relatively recent addition that addresses shared-file lifecycle)
Auto-apply policies run in the background; labeling is not instantaneous. Content is typically labeled within a day of matching the conditions, though large tenants may take longer.
Disposition Reviews
When a retention label or policy is configured with a disposition review at end of retention, Purview surfaces the items in the Disposition page of the Purview compliance portal. A reviewer can:
- Permanently delete the item
- Extend the retention period
- Relabel the item with a different retention label
- Export the list of items for offline review
Disposition reviews provide a human check before destructive deletion, which is important for legal-hold scenarios and for content where the retention period may need extension.
Retention vs Sensitivity Labels
Retention labels and sensitivity labels are often confused because both are labels and both live in Purview. They serve different purposes:
Retention label Sensitivity label
Purpose How long to keep content and when to delete it How to protect and classify content (encryption, watermarks)
- Typical values Retain 7 years then delete Confidential, Highly Confidential
- Effect Controls lifecycle (keep/delete) Controls access (encryption) and marking (watermark/header/footer)
A single item can carry both a retention label and a sensitivity label at the same time; the two are independent.
Exam Tip
For the MS-102 exam, remember the three-object distinction (policy, label, label policy), the four auto-apply conditions (SITs, trainable classifiers, keywords/KQL, cloud attachments), and the three end-of-retention actions (delete, disposition review, archive). A common scenario question asks which object to use when legal needs content kept for 7 years — the answer is a retention label published via a label policy, not a sensitivity label.