14.3 Retention Precedence and Policy Lookup

The same email or document can be in scope for several location-wide retention policies and still have a retention label. Microsoft is explicit that the outcome is not which single policy or label object wins. You calculate how long the item is retained (if applicable) and when the item is permanently deleted (if applicable) as two independent actions, using every retain setting and every delete setting that applies. The principles of retention are the tie-breakers. Apply them in order and stop when the conflict is resolved.

Priority cleanup can expedite permanent deletion in exceptional cases and sits outside this default model. Unless a question names priority cleanup, use the four principles. eDiscovery holds also prevent permanent deletion; they belong with the first principle until an administrator releases the hold. Creating location-wide retention policies and recovering copies from Preservation Hold or Recoverable Items is the next chapter—this section is how to interpret conflicts and how to find which policies apply.

Item-level labels versus location policies

Because a label targets the item, Microsoft treats a delete action from a retention label as explicit compared with a delete action from a retention policy. That is principle 3 for deletions. It is not a reason to ignore a longer retain action that still applies from a policy—principles 1 and 2 run first.

Unlike sensitivity labels, you cannot configure a priority order for retention labels. Before you apply the principles, you must know which one label is on the item. A label can arrive from manual apply, auto-apply, a Syntex model, a SharePoint or Outlook default, an Outlook rule, or the Power Automate action Apply a retention label on the item. For standard labels (not records or regulatory records), admins and end users can change or remove the label. Auto-apply, Syntex, and Outlook rules do not replace an existing label. Power Automate Apply a retention label does replace. Default labels can replace other default-applied standard labels in the SharePoint and Outlook cases documented in the publish section. Record and regulatory labels are not silently swapped during their retention period; regulatory records cannot be removed by those automatic paths.

The four principles, top to bottom

Microsoft's flow uses each level as a tie-breaker. If the first level fully decides the outcome, do not invent a later rule to override it.

1. Retention wins over deletion. Content is not permanently deleted while it also has retention settings to retain it. A user or system delete can still remove the item from the main view; permanent deletion is suspended. Example: an Exchange retention policy deletes three years after created, and a label retains five years after created. The message is retained for five years because retention takes precedence. At the end of those five years the suspended delete can complete.

2. The longest retention period wins. If several settings retain for different lengths, the item is retained until the end of the longest retention period for that item. The number in the wizard is not always the longest clock. A five-year period that starts from last modified can outlast a seven-year period that starts from created if the file keeps being edited. Retention labels can also start from when labeled or from an event. Example: one policy retains all SharePoint sites for five years after created; a second policy retains specific sites for 10 years after created. Documents on the Marketing site are retained for 10 years.

3. Explicit wins over implicit for deletions. After retain conflicts are resolved, only delete conflicts remain.

• A retention label—however it was applied—is explicit compared with retention policies. A delete action from a retention label always takes precedence over a delete action from any retention policy. Example: two policies would delete at five years and 10 years, and a label deletes at seven years. Permanent deletion is at seven years because the label delete wins. Another Microsoft example: a policy retains all SharePoint sites for 10 years after created, and a label specifies delete after seven years. The document is still retained for 10 years (longest retain). Because the label delete takes precedence, the document is permanently deleted after those 10 years; Microsoft notes that in this SharePoint example the item is not moved to the Preservation Hold library. For Exchange, Microsoft documents a parallel: retain 10 years from a policy plus a label delete at seven years keeps the item 10 years; after seven years the label causes the item to move to Recoverable Items, where it remains until the 10-year retain expires.
• When only retention policies apply: a policy that uses an adaptive scope, or a static scope that includes specific instances (specific users, specific sites), takes precedence for deletion over a static org-wide policy (All mailboxes, All sites). Two policies that are both scoped to specific instances have equal precedence at this level, so you continue to principle 4. Example: an unscoped (org-wide) policy deletes after 10 years; a mailbox-scoped policy deletes after five years. Permanent deletion is at five years because the scoped delete wins.

1. The shortest deletion period wins. Use this only when delete conflicts among equally scoped retention policies were not resolved above. Content is permanently deleted at the end of the shortest retention period for the item from those policies. Start-of-period settings can again reverse a naive comparison of the year values. Example: two OneDrive-scoped policies delete at 10 years and seven years after created. Permanent deletion is at seven years.

Worked combination from Microsoft: delete-only policy at five years; retain-three-then-delete policy; label retain-only seven years. Outcome: retain seven years (longest retain; retain beats delete). Then permanently delete because of the policies' delete actions, which could not run before the longest retain ended.

Second published combination: org-wide delete-only at 10 years; scoped policy retains five years then deletes; label retains three years then deletes. Outcome: longest retain is five years. At the end of that retain, the label's delete (configured at three years) takes precedence over both policy deletes, so the item is permanently deleted at five years. Microsoft states that in this example all conflicts are resolved by the third level.

Policy lookup

You can configure multiple retention policies for Microsoft 365 locations, plus multiple retention label policies that you publish or auto-apply. Guessing from policy names is how tenants miss a static include. Use Policy lookup from Data lifecycle management or Records management in the Microsoft Purview portal to find the policies for retention assigned to specific users, sites, and Microsoft 365 groups.

Microsoft's matching rules are strict:

• User: the exact email address
• Site: the exact URL (this option includes OneDrive accounts; you must use the real OneDrive URL, not a display name or a guessed path)
• Microsoft 365 group: the exact group email address

You cannot use wildcards or partial matches. If lookup returns nothing, the usual causes are a typo, an unprovisioned OneDrive URL (OneDrive URLs are often created only when the user first accesses OneDrive, and they change if the UPN changes), or searching a display name instead of SMTP.

Policy lookup answers which policies apply to that user, site, or group. It lists both location retention policies and label policies (publish and auto-apply). It does not run the four principles for a single file, and it does not enumerate every item-level label on every document. After you have the policy set, confirm which one label is on the item (details pane, Outlook Assign Policy, content explorer, or a content search on the Retention label condition), then apply the principles.

Exam-style uses:

• A mailbox seems to delete too soon: look up the exact SMTP address and compare org-wide Exchange policies, scoped mailbox policies, and any publish or auto-apply label policies for that user.
• A SharePoint site keeps files that a delete-only policy should remove: look up the exact site URL and check for a longer retain policy or a label policy that publishes or auto-applies a retain label.
• A Microsoft 365 group: look up the exact group email. Remember that published labels on the Groups location affect the SharePoint team site, not group mailbox clients.

Lookup is a discovery tool. Changing who is in scope still means editing the policy (static includes and excludes, or adaptive queries). Do not treat lookup as a way to recover deleted content; recovery of retained copies is the next chapter.