SharePoint Storage Quota Exceeded? What Breaks First and How to Reclaim Space Fast

The first sign is rarely an alert in the admin centre. It’s someone in finance who can’t save a spreadsheet, and a OneDrive sync icon that has been spinning for an hour. By the time the ticket reaches IT, people have been losing work for a day.

Running out of SharePoint storage is one of the few Microsoft 365 problems that degrades rather than stops. Different things break at different times, some silently, and none of the error messages says “your tenant is full”. Here’s what happens when you exceed the SharePoint storage quota, how to diagnose it quickly, and the three safest ways to get space back.

What the quota alert actually means

Microsoft’s service description is clear: a tenant that keeps running above its storage limit risks being put into read-only mode, where users can’t add or change content until usage drops or more storage is bought. Long before that, the symptoms appear at the edges:

1. Office saves fail. Word, Excel and PowerPoint say the file can’t be saved to the server. Users blame their Wi-Fi and keep retrying.
2. OneDrive sync stalls on specific files. Local edits keep working, so people think their work is safe.
3. Teams file uploads fail, because channel files live in the site that’s out of space.
4. Teams meeting recordings fail silently. This is the worst one: nobody notices until someone looks for the recording days later.
5. Power Automate flows that write files start failing with generic errors that are hard to trace back to storage.

Because the failures surface in the apps, not in the admin centre, storage is rarely the first suspect.

Diagnose it in this order

1. SharePoint admin centre → Active sites. Add the Storage used column and sort descending. Look at the tenant total against your limit, and at any single site that has ballooned.
2. Confirm your allowance. Tenant storage is 1 TB plus 10 GB per licensed user, plus any extra storage you’ve bought. A previous purchase may now be exhausted too.
3. Is it one site? A single site can grow to 25 TB. If one site is most of the problem, the fix is local and fast.
4. Check site quotas. If storage management is set to manual, a site can hit its own cap while the tenant still has space. In that case you’re chasing the wrong problem.
5. Check the recycle bins. Recycle bin content counts against your total. A library deleted last week hasn’t freed anything yet.
6. Look for a recent migration or sync loop. A re-run migration can add terabytes in days, and the growth curve will show whether this is gradual or a single event.

The three quickest ways to reclaim space

1. Empty the largest sites’ recycle bins

Clear both the first-stage and second-stage recycle bins on your biggest sites, and check the storage figure after each one. After a migration this is usually the biggest single win, because the failed first attempt is often still sitting in a bin (items stay for up to 93 days).

2. Review leavers’ OneDrive accounts

A deleted user’s OneDrive is kept for 30 days by default, or much longer if someone has changed the retention setting. Check your setting first. Then:

• List leavers’ OneDrives above a size threshold.
• Hand anything important to their manager or move it to a team site.
• Release the rest.

Don’t skip the review step: this is the action most likely to delete something legal wanted to keep.

3. Limit version history, then trim existing versions

Versioning is often the biggest hidden consumer of storage. Setting a version limit only affects future versions, so it won’t reclaim anything on its own, and many admins stop there and wonder why the number hasn’t moved. Instead:

1. Set organisation-level version history limits. Microsoft recommends the Automatic setting, or you can use Manual with a maximum number of major versions and an optional expiry.
2. Run the version storage report on your largest sites to see what trimming would recover.
3. Queue a trim job for existing versions.

Warning: trimmed versions skip the recycle bin and can’t be recovered, and content under retention policies or eDiscovery holds isn’t trimmed. Always run the report first.

What not to do in the first hour

• Don’t buy storage instead of investigating. Buying extra storage to restore service is fine, and you can revisit it at renewal. But if you never find the cause, you’ll pay for the same wasted gigabytes every year.
• Don’t run bulk deletions like “delete everything older than three years” across live team sites you haven’t reviewed. You’ll lose more in goodwill, and possibly compliance, than the storage is worth.

Preventing the next incident

Storage becomes an incident because it’s reported as a snapshot but consumed as a trend. A quarterly review of consumption, growth rate and what is being stored (duplicates, old versions, large media files, leavers’ data) turns a 2 a.m. emergency into an agenda item.

You can build that view with PowerShell (see my SharePoint PowerShell scripts) or use a dedicated tool such as LogiSam’s Tenant Storage Optimisation, which scans SharePoint, OneDrive, Exchange and Teams together and ranks clean-up recommendations. There’s a bonus too: removing stale and duplicate content also makes Copilot more accurate, as I explain in why Copilot gives wrong answers.

FAQ

How much SharePoint storage does my tenant get?

1 TB plus 10 GB for each licensed user, plus any extra storage you’ve purchased.

Does the recycle bin count towards storage?

Yes. Site recycle bin content counts against your tenant total until it’s emptied or expires.

Will setting a version limit free up space straight away?

No. It only affects new versions. To reclaim space from existing versions, you need to run a trim job.

Can SharePoint go read-only when storage is full?

Yes. Microsoft states that tenants staying over their limit risk read-only mode until usage is reduced or capacity is added.