Purview priority cleanup: who approves a deletion that overrides a hold

Priority cleanup in Microsoft Purview deletes content that retention settings or eDiscovery holds would otherwise keep. It works on Exchange mailboxes and on SharePoint and OneDrive files. The feature is enabled at tenant level by default, and in some configurations it overrides Preservation Lock. Those two facts are why it needs owners before anyone builds the first policy.

Microsoft wraps it in safeguards: a dedicated admin role, approvals from other people, mandatory simulation for files, and an audit trail. They only hold if the right people have the roles. Our rule: the records owner and counsel approve the purpose of each priority cleanup policy in writing, and every approver is a named person who knows what they're approving.

What it won't touch

Items marked as a record or regulatory record are out of scope. Content already copied into an eDiscovery review set stays there until an eDiscovery admin deletes the case. When an item matches more than one priority cleanup policy, the newest one wins.

Under the covers it uses auto-applied retention labels that supersede the normal principles of retention. Users see this. A file picked up by a policy shows a retention label with the policy's name, and if someone removes it, the policy puts it back. In Outlook, a flagged email shows a retention message bar with the policy name and "(-1 days)". So the policy name is public. The description field is visible only to priority cleanup admins and the policy's approvers, and that's where the detail belongs.

Mailboxes: rare, and three approvals

Learn's mailbox examples are a data spillage, such as an employee emailing details of a planned acquisition, and a privacy request to remove a former employee's personal information while every mailbox is under two-year retention. Learn's comparison table lists typical mailbox use as rare. For mailboxes the feature is still rolling out in preview, and the roadmap gives general availability as October CY2026 (ID 392838).

Every item needs three approvals beyond the policy's author: a priority cleanup admin, a retention manager and an eDiscovery admin. Learn says the first should be someone other than the author, but the tool doesn't enforce it, so your process has to. Approvers must be individual users, not mail-enabled groups, and each needs the right roles before the policy is created or creation fails. After the last approval the item is permanently deleted and can't be restored by users, admins or Microsoft. Simulation is optional for mailboxes. We'd run it anyway.

Files: continual, and a second admin at the switch

For SharePoint and OneDrive, Learn names two typical uses.

The first is Teams meeting recordings and transcripts, which the Copilot in Teams recap feature draws on. A Teams recording expiration setting can't delete a recording that a Purview retention policy is still keeping, so recordings outlast their expiration date. Learn describes these files as typically large and of little business value after one to three months. A policy with the query ProgID:Media AND ProgID:Meeting can run continuously and remove them.

The second is the leaver. A OneDrive can't be deleted while anything in its Preservation Hold library has an unexpired retention period. A policy using ParentLink:PreservationHoldLibrary clears those files so the account can go. It's the step after last Friday's leaver post, and it needs the same records sign-off. Files kept under a hold also keep their version history, as Wednesday's version limits post explained.

The rules for files differ. Simulation is mandatory, and has to be rerun after any change other than the description. A second priority cleanup admin reviews the results and turns the policy on, because the last person to edit a policy can't enable it. After that, only content under an eDiscovery hold needs another approval, from an eDiscovery admin. Learn states that separate approval from a retention admin isn't required to override retention settings. That's the gap a records owner should close by process, since the tool won't.

Standard cleanup moves files to the second-stage recycle bin. A permanent deletion option, with public preview rollout from 24 August 2026, skips the recycle bins entirely, after which the content is no longer discoverable in SharePoint search, Microsoft 365 Copilot or eDiscovery. For files, Preservation Lock is overridden only when the policy is delete-only.

When an approver says no

Declining isn't a separate action. An approver who disagrees has to relabel the item with an existing retention label. Approvals never happen automatically after a set time, and approvers can't add other approvers. Give each approver a short list of the labels that mean "keep this", or the safe choice becomes the awkward one.

Audit, and the off switch

Turn on auditing at least a day before the first policy runs. Every policy gets a cleanup ID; search the audit log for it, and look for PriorityCleanupTagApplied, then PriorityCleanupDelete for mail, PriorityCleanupFileRecycled for files, or PriorityCleanupFileDeleted for permanent file deletion.

An organization that doesn't want the capability can turn it off under Priority cleanup settings, which covers Exchange, SharePoint and OneDrive together. Existing policies keep running and can be deleted, but can't be modified. Turning it off is a decision to take before policies exist. Afterwards, it freezes the existing ones as they are, still running.