Retention labels vs retention policies

A Microsoft Purview retention policy applies a keep-or-delete rule to whole locations (all mailboxes, all SharePoint sites, a set of Teams chats), while a retention label applies a rule to one individual item and travels with it. The decision rule: if the rule is the same for everything in a location, use a policy; if different items in the same place need different treatment, or the item must be a record, use a label. Both can apply to the same item, and when they overlap, retention beats deletion and the longest retention period wins.

Policy or label: the decision table

Microsoft Learn describes the same split: retention policies manage the content of locations, and retention labels manage individual items. Behind the label there is a second object that exam questions like to hide: a label does nothing until it is included in a retention label policy that publishes it to locations, or in an auto-apply policy that applies it for you. This mirrors sensitivity labels, which also need a policy. See sensitivity labels explained for that side.

An item can have only one retention label at a time, but it can sit under several retention policies at once. That asymmetry is the source of most of the conflict questions.

What a retention rule can do

Both objects offer the same building blocks. The rule can retain content for a period, delete it after a period, or retain and then delete. The period can start when the item is created or, for files, when it was last modified; labels add two more options, when the item was labeled and when an event happens (for example an employee leaving). Learn also notes that a label can be set to take no action at all and serve only as a text label, or be used as a condition in a DLP policy for SharePoint documents, which links this topic to DLP explained.

Scope matters for policies. A static scope lists specific instances (these mailboxes, those sites). An adaptive scope uses a query that runs daily against attributes such as a Microsoft Entra job title, so membership follows the people and sites automatically. Learn lists two locations, Skype for Business and Exchange public folders, that do not support adaptive scopes.

Records change the rules

A label can mark an item as a record. Learn separates standard labels from labels that mark items as a record or a regulatory record. Record labels restrict what users can do with the item; for a regulatory record, even admins cannot manually change or remove the label. Because those restrictions are irreversible, the regulatory record option is hidden until it is enabled with PowerShell, and regulatory record labels cannot be auto-applied, only published for manual use. At the policy level, Preservation Lock locks a retention policy or retention label policy so that no one, including an administrator, can turn it off, delete it or make it less restrictive. Learn cites SEC Rule 17a-4 as the kind of regulation that needs this, and notes that adaptive scopes do not support Preservation Lock. Priority cleanup, used to expedite deletion in exceptional cases such as data spillage, is not supported for items marked as records.

Worked example: two rules, one contract

Contoso has a retention policy on all SharePoint sites: retain for 10 years from creation, then delete. Legal publishes a label “Contract” (retain 7 years from creation, then delete) and users apply it to a contract in the Legal site.

1. Retention wins over deletion: the label retains the file to year 7 and the policy to year 10, so neither delete action can permanently remove it while a retention period is still running.
2. The longest retention period wins: the file is kept for 10 years.
3. Explicit wins over implicit: the label is explicit on the item, the policy only implicit from the container. The label’s delete action takes precedence, so after year 10 the file is deleted by the label. Learn’s matching example says the item is not moved to the Preservation Hold Library.
4. The fourth principle, the shortest deletion period wins, only breaks ties that remain between rules of equal explicitness.

Had the same pair applied to an email in Exchange with a 7-year label and a 10-year mailbox policy, Learn says the label moves the item to the Recoverable Items folder at year 7 and it stays there until the 10 years end, after which it is permanently deleted.

An eDiscovery hold ranks above all of this. Held items cannot be permanently deleted by a policy or label until the hold is released.

Which exams test this

SC-401 also asks you to configure audit retention policies, in its risks, alerts, and activities domain: Alerts and activities explained.

How the questions are built

• “Different documents in the same library need different periods” points to labels, since a policy gives the whole site one rule.
• “Without any user action, for all mailboxes” points to a policy.
• “Must not be editable or deletable, even by admins” points to a regulatory record label.
• “Which period applies when several rules overlap” needs the four principles in order: retain first, then longest retention, then explicit over implicit, then shortest deletion.
• A label exists but users cannot see it: it has not been published in a label policy.
• Employees leave and retention must start then: the event-based period.

The usual trap is to answer “the shortest period wins” because deletion sounds like the main action. Retention is resolved first, and only then deletion.

Go deeper

• Learn about retention policies and labels (Microsoft Learn, includes the principles of retention)
• Records management overview (Microsoft Learn)
• Related topics: sensitivity labels explained, data classification, DLP explained
• How to study for certification exams