Teams & migration
Updated August 12, 2026 · min read
Duplicate Cleanup and Microsoft 365 Retention Policies
Keep content equality separate from records obligations, holds, labels, and required copies.
Technical deduplication asks whether content matches; retention asks whether an item must remain, for how long, and under whose control. Those questions overlap but are not interchangeable.
Add policy attributes and an exception state to the review process. Exclude protected locations or labels where the scanner lacks authoritative policy context, and record the reason rather than implying the item is ordinary redundancy.
A practical checklist
- 1Identify applicable records, legal, contractual, and project rules.
- 2Map policies to owners, locations, and items.
- 3Exclude holds and unclear classifications from cleanup recommendations.
- 4Document why the retained item satisfies the requirement.
- 5Audit the approved action and recovery path.
Understand the situation
Technical deduplication asks whether content matches; retention asks whether an item must remain, for how long, and under whose control. Those questions overlap but are not interchangeable.
Team libraries need an owner and a decision trail. A byte-identical file may still be required in a separately permissioned workspace, under a retention rule, or as the target of a shared link.
Use a controlled workflow
Add policy attributes and an exception state to the review process. Exclude protected locations or labels where the scanner lacks authoritative policy context, and record the reason rather than implying the item is ordinary redundancy.
Pilot the workflow on a representative scope, record exceptions, and measure false positives before expanding. Business cleanup is safer as a governed series of batches than as a single drive-wide action.
- Map policies to owners, locations, and items.
- Exclude holds and unclear classifications from cleanup recommendations.
- Document why the retained item satisfies the requirement.
Make the final decision
Only approve candidates when the authorized policy owner confirms that removing that specific item is permitted and the retained copy satisfies requirements. Preserve the scan evidence, approval, and action log for audit.
The exported plan should be useful outside the scanner: identify the account and scan, retained items, candidates, evidence, reviewer, and exceptions so another person can audit the decision.
Limits and risks to check
- — Content equality does not establish policy equivalence.
- — Labels and holds may apply to specific item identities or locations.
- — Scanner metadata may not include authoritative policy state.
- — Jurisdiction and organization rules vary.
Official references
Frequently asked questions
Can I delete an exact copy under retention?
Only if the authorized policy interpretation permits removal of that item and the retained copy satisfies all obligations.
Should the scanner make legal decisions?
No. It should expose evidence and exceptions while policy owners make retention decisions.
What should be logged?
Match evidence, item identities, policy check, keeper, approver, action time, outcome, and recovery information.
Scan first. Decide with evidence.
ClearCopies reads supported cloud-drive metadata and groups exact copies by byte size plus a provider-supplied content fingerprint. Original file bodies are not downloaded for the scan. You review the result and export a plan before any separate write step.