Why are SharePoint sites going read-only over storage limits?
Cloud storage sites exceeding official capacity limits are receiving warnings that accounts will be restricted to read-only unless administrators pay expensive per-terabyte fees or manually prune data. Managing this requires monitoring actual consumption, tracking historical growth trends, and adjusting versioning limits to reduce oversized files.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Switching sites over to automatic versioning limits
- 2Evaluating third-party archiving tools like Layer2 ShArc to move files between Azure Blob and SharePoint
- 3Paying additional monthly fees per TB for extra storage
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Looks like overquota'd sharepoint sites are now getting warnings that their service will be made read only during October”source ↗
“I have one that is 6TB over it's official limit, switched a lot of the sites over to automatic versioning limits which has put it to 4.8TB over now as it was mostly adobe files.”source ↗
“Discussing with management about choices and obviously we can pay ~£180 perTB per month - but i saw this service layer2-sharc.com has anyone used it before?”source ↗
Where this came up
People with this problem also raised
- 9Why are cloud bills so unexpectedly high?
- 6Will all my furniture fit into a moving container?
- 4Why does a cloud outage feel like total chaos internally?
- 5How do you enable record updates in Agentforce and check credit costs?
- 4Why does a CRM get so messy as outbound volume grows?
- 6How to handle wedding guest list additions at the last minute