Priority Cleanup: when Copilot hygiene meets legal hold

Copilot finds everything a user has access to. That includes three-year-old Teams recordings and transcripts that nobody ever wanted to keep. The data protection side wants them gone. Legal may have a hold on the very same mailboxes and sites. Both are right. This is exactly the situation Priority Cleanup in Microsoft Purview was built for, and with MC1261587 the tool now gets a much sharper blade.

First, a correction of expectations: Priority Cleanup is not a janitor that tidies away meeting recordings on its own. It is a deliberately designed policy workflow. That is better than it sounds. But it comes with duties that many tenants have not met yet.

What Priority Cleanup really does

Priority Cleanup sits in Microsoft Purview under Data Lifecycle Management. You define a policy for specific content, and that content gets deleted, even if retention policies, retention labels or eDiscovery holds would normally protect it. Under the hood, the feature works with auto-applied retention labels that override the usual principles of retention.

For SharePoint and OneDrive, Microsoft names two typical use cases:

• Stale Teams recordings and transcripts that Copilot uses for recaps. According to Microsoft, they often have little business value after one to three months. Here the policy runs continuously, and the matching query is ProgID:Media AND ProgID:Meeting.
• The Preservation Hold library of people who left the company. As long as items with an unexpired retention period sit there, the OneDrive cannot be deleted. Priority Cleanup clears them so you get the storage back.

Two modes: recycle bin or final

This is where the real news is.

	Existing mode	New: “Delete data permanently”
What happens?	Items move to the second-stage recycle bin and go through the normal time periods	Items are hard deleted, the recycle bins are skipped
Findable afterwards?	Recoverable until the recycle bin period ends	No longer in SharePoint search, Copilot and eDiscovery
Status	Available	Rolling out, completion by mid-November 2026 according to MC1261587
Activation	Part of every policy	Must be chosen explicitly in the policy

The new option is not on by default. You choose it consciously in the policy settings. But once you choose it, there is no way back.

The tension

From a Copilot point of view: less legacy content means better answers and fewer surprises.

From a records point of view: what is deleted is gone. If a legal case comes up later, part of the evidence you once had in your own hands may be missing.

Microsoft does not solve this by picking a side. Microsoft builds in friction:

• Simulation is mandatory. For SharePoint and OneDrive, you must test every policy in a dry run first, the first time and after every change.
• Two-person rule. A second Priority Cleanup Admin reviews the simulation. Whoever last edited the policy cannot turn it on themselves.
• eDiscovery approval for holds. If an item is under an eDiscovery hold, an eDiscovery admin must also approve. Anyone who does not want to approve must assign an existing retention label to the item.
• Audit. Every step lands in the Purview audit log, with dedicated events for SharePoint and OneDrive.

That is good design. But it only works if the roles are filled consciously. If nobody can approve, nothing happens. If too many people can approve, you have a different kind of problem.

⚠️ Attention
According to Microsoft, Priority Cleanup is enabled by default at tenant level. And the Priority Cleanup Admin role is automatically part of the Organization Management role group. If you have never touched these roles, check now who already holds them.

What Priority Cleanup cannot do

• Items marked as a record or regulatory record stay untouched.
• If data has already been copied to an eDiscovery review set, it stays there until the case is deleted.
• For SharePoint and OneDrive, Priority Cleanup only overrides Preservation Lock if retention is set to delete-only.
• Deleting a policy does not stop everything: if the approval is already complete, items may still be deleted.

The admin checklist before first use

1. Inventory roles. Who has Priority Cleanup Admin, who has eDiscovery Admin? Check the Organization Management role group in particular, because its members get the cleanup role automatically.
2. Name approvers. You need at least two Priority Cleanup Admins, otherwise the two-person rule does not work. Add eDiscovery approvers for holds. Approvers must be individual people, groups are not supported. Plan deputies for vacation and sick leave.
3. Clarify the legal hold process. Who tells IT that a hold is active? If legal knows and IT does not, you have a communication problem, not a tool problem.
4. Define exceptions. Which sites and accounts are off limits, for example the board, ongoing cases, the works council and HR? Put that in writing before the first policy is created.
5. Keep the scope narrow. Start with one clearly defined content type, for example old meeting recordings. Not with “everything older than X”.
6. Choose neutral policy names. Users see the name as a retention label on their files. Details belong in the description, which only admins and approvers can see.
7. Decide on hard delete consciously. Start in recycle bin mode. Use “Delete data permanently” only once the process works and legal has agreed.
8. Take simulation seriously. Have someone from the business look at the samples, not just IT.
9. Prepare auditing. Turn on auditing at least one day before. Clarify who analyzes the logs and how long they are kept.
10. Document. One sentence per policy on reason, scope and approvers. In a year, someone will ask why the data is missing.

A word on compliance

Whether a deletion despite a hold is legally allowed is not decided by Purview. The tool makes it technically possible, not legally right. Only delete content where data protection or confidentiality clearly takes priority and legal has agreed. This is not legal advice. Clarify the framework with legal before you activate a policy.

And if your organization does not want the tool at all: you can turn off Priority Cleanup for the whole tenant in the settings. Existing policies keep running, but no new ones can be created.

ℹ️ License
Priority Cleanup is part of Purview Data Lifecycle Management. Expect Microsoft 365 E5 or the E5 Compliance add-on, and check your licensing before you bring the topic to the compliance team.

What stays

Priority Cleanup is an honestly built tool. Microsoft does not replace the hold, it creates a controlled exception path. With the new hard delete option, though, that path becomes final. If you only see it as a Copilot cleanup helper, you miss the other half: the workflow is only as good as the people who approve.

☕ Espresso Moment: A delete button that overrides legal holds does not need courage. It needs clear roles.

Your takeaways

• Priority Cleanup deletes in a targeted way, even despite retention or eDiscovery holds. It is not automatic, but a policy someone creates on purpose.
• New is “Delete data permanently”: hard deletion without the recycle bin. The rollout runs until mid-November 2026.
• The feature is on by default, and Organization Management gets the admin role automatically. Check now who holds it.
• Simulation, a second admin, eDiscovery approval and audit are your seat belts.
• Choose neutral policy names, because users see them.
• Start with a narrow scope and in recycle bin mode, for example with old Teams recordings.
• Clarify the legal framework with legal. The feature does not replace legal advice.

Your next step: Open Purview today and check under roles and role groups who holds Priority Cleanup Admin and eDiscovery Admin. Look at Organization Management in particular. It takes ten minutes and tells you who in your tenant could override holds today.

Message Center post: MC1261587

How does this work for you: who decides when Copilot hygiene and legal hold collide? Tell me on LinkedIn.