SharePoint Storage at 90% – Retention Hold Preventing Cleanup

Question

Hello Experts,

I’m looking for guidance on how to safely reduce storage usage in our tenant.

Current situation:

• Our SharePoint storage consumption is at 90%.
• A 7‑year retention policy (tenant-wide, including OneDrive) is currently applied.
• I attempted to reduce storage by deleting older versions in several SharePoint sites, but version cleanup is blocked due to the active retention hold.

Because the retention policy prevents deleting content or reducing versions, I’m unsure how to proceed with storage cleanup without violating compliance requirements.

Answer 1

You can either exclude specific sites from the retention policy or use the Priority cleanup feature to target items based on some criteria (such as filetype) and remove them, overriding any retention settings that apply. I have a short guide on how the process works here: https://michev.info/blog/post/6927/priority-cleanup-for-sharepoint-online-and-onedrive-for-business

Answer 2

Storage can be reduced, but only in ways that respect the existing 7‑year retention requirements. The key point from the platform behavior is that retention always wins over version trimming and deletion, so standard cleanup actions are blocked while the policy is in effect.

Use the following options that are supported with retention in place:

1. Optimize storage within the retention constraints
   • Configure site storage limits and version history limits to reduce future growth rather than trying to delete content that is currently under hold:
     • Set site storage limits to Automatic or Manual as appropriate, and adjust version history limits to the Automatic setting for optimal version restore and storage. This reduces the number and age of versions going forward.
     • See: site storage limits and version history limits in SharePoint storage planning.
   • Use retention policies to automatically delete content after the required retention period. Retention settings can be configured for retain-only, delete-only, or retain-then-delete behavior, but cannot be bypassed for items still within the retention window.
2. Understand why version cleanup is blocked
   • When a site or document is under a retention policy or eDiscovery hold, the retention setting determines the retention of versions. The retention policy “wins” over version trimming.
   • When the trim job encounters a version under retention, it does not delete it; instead it stamps an expiration date. If the retention policy is still in effect at that date, the expiration date is extended. Only after the hold is lifted and the expiration date is reached will the version be deleted.
   • This is why manual or automatic version deletion is blocked while the 7‑year policy is active.
3. Use Priority cleanup when there is a justified need to override holds
   • If there is a regulatory, security, or privacy requirement to delete specific content earlier than the 7‑year policy (for example, large stale Teams meeting recordings used by Copilot recap), use Priority cleanup in Microsoft Purview:
     • Priority cleanup lets administrators override existing retention settings or eDiscovery holds to delete identified content from SharePoint and OneDrive.
     • Items are moved to the second-stage Recycle Bin and then follow the normal compliant deletion process for SharePoint/OneDrive, ensuring the deletion remains compliant.
     • This is suitable for targeted scenarios (e.g., large low‑value files) but should be used only when the organization’s compliance owners approve overriding the existing retention.
4. Adjust retention scope only if compliance allows
   • If the 7‑year policy is broader than required, compliance owners can:
     • Edit the retention policy in the Microsoft Purview compliance portal and exclude specific SharePoint sites from the tenant‑wide policy, or
     • Remove specific sites from a policy that applies only to selected locations.
   • Notes:
     • Excluding a site from a retention policy bypasses the 30‑day retention grace period.
     • Removing a site from a policy keeps it under a 30‑day retention grace period before items become eligible for permanent deletion.
   • Any such change must be driven by compliance/legal requirements; it is not a purely technical storage optimization.
5. Additional storage optimization options that respect retention
   • Use the guidance in SharePoint storage planning to:
     • Archive inactive content to lower‑cost storage using Microsoft 365 Archive.
     • Empty site recycle bins to reclaim space for items that are no longer under retention.
     • Configure lifecycle and inactive site policies (for example, via SharePoint Advanced Management) to automatically detect inactive sites and manage them, while still respecting retention.

In summary, storage can be reduced by:

• Limiting future version growth and using archive/lifecycle features.
• Using Priority cleanup for specific, justified scenarios where overriding holds is allowed.
• Narrowing or adjusting retention scope only when compliance requirements permit.

Retention itself cannot be bypassed for current content without using these supported mechanisms, and any change to the 7‑year policy must be coordinated with compliance/legal stakeholders.

---

References:

• SharePoint storage planning
• Override holds to clean up files for Copilot and reclaim storage
• Learn about retention policies and retention labels
• FAQs
• Learn about retention for SharePoint and OneDrive
• Exclude or remove sites from a SharePoint Online retention policy