When SharePoint storage grows, investigate retention before deleting files
Large files are visible. Retention side effects often are not. That is why a storage incident can become a compliance incident when somebody responds by changing a policy before understanding what is preserving the content.
Deletion and storage reclamation are different events
When SharePoint or OneDrive content is retained, Microsoft can preserve the original version in the Preservation Hold library after a user edits or deletes it. The user may see a file disappear while the tenant still retains a copy. Microsoft explains the workload-specific behaviour in retention for SharePoint and OneDrive.
That leads to a simple rule: do not promise storage recovery from a deletion until you have identified the retention, hold, versioning, and recycle-bin path for that content.
Build a storage evidence pack
For a high-consumption site, collect:
- Site owner and business purpose
- Largest libraries and versioning configuration
- Retention policies and retention labels in scope
- eDiscovery holds or cases
- Site lock state and archive state
- A legal or records-management owner for each control
Retention policies apply the same settings to locations. Retention labels allow item-level decisions, can start from an event, support disposition review, and can mark content as a record. Microsoft compares the two approaches in its retention policy and label guidance.
Decide with the right owner
Storage operations can identify candidates. They should not unilaterally exclude a site from a retention policy or remove a label. The appropriate decision needs the site owner, records or legal owner, and platform owner. Document the scope, the reason, approval, expected timing, and the verification result.
Use a small, reversible pilot when the policy design permits it. Validate both business access and compliance evidence after the change. Then assess actual storage behaviour rather than assuming the first dashboard has already caught up.
Retention is not a storage tax. It is an explicit decision to preserve information. Treat changes to it with the same care as any other security or compliance control.