Five ways to manage SharePoint Online storage at the site-collection level, from a one-off admin center edit to bulk cleanup with ShareMaster's Optimise Storage Tools.
| Approach | Enforces quota ceiling | Scales to 100+ sites | Per-library breakdown | Reduces actual file size | Ongoing effort |
|---|---|---|---|---|---|
| SharePoint admin center | Yes | No | No | No | High (manual per site) |
| PowerShell (Set-SPOSite) | Yes | Yes | No | No | Medium (scripted) |
| Microsoft 365 usage reports | No | Yes | No | No | Low (read-only) |
| Microsoft 365 Archive | Partial | Yes | No | No | Low (policy-driven) |
| ShareMaster Optimise Storage Tools | No | Yes | Yes | Yes | Low (bulk cleanup) |
1. SharePoint admin center (manual quota per site)
Every site collection has a storage quota field in the SharePoint admin center. Admins can open Active sites, select a site, and set a specific limit in gigabytes. When the site hits that ceiling, uploads stop until the quota is raised or storage is reclaimed.
Where it works well
Useful for new site provisioning, where setting a quota at creation time prevents a project site from consuming an unreasonable share of the tenant pool. Also appropriate when a specific site has grown unexpectedly and needs a hard cap while a cleanup is organised.
Where it falls short
Applying or reviewing quotas across dozens or hundreds of sites one by one is not practical. The admin center has no bulk quota editor. It also shows total site storage but not which library or list is responsible for the growth, so admins still have to investigate root causes separately.
2. PowerShell: Set-SPOSite -StorageQuota
The SharePoint Online PowerShell module's Set-SPOSite cmdlet accepts a -StorageQuota parameter (in megabytes) and a -StorageQuotaWarningLevel for a pre-limit alert. A short script can loop through a CSV of sites and apply consistent limits in one run.
Set-SPOSite -Identity "https://contoso.sharepoint.com/sites/finance" `
-StorageQuota 51200 `
-StorageQuotaWarningLevel 46080
PnP PowerShell (Set-PnPTenantSite) offers the same parameters with a slightly cleaner syntax. Both require a SharePoint Administrator or Global Administrator account.
Where it works well
Ideal for bulk provisioning, where a governance standard requires that every new site starts with a defined ceiling. A script run on a schedule can also catch sites that were provisioned without a quota set.
Where it falls short
PowerShell sets a ceiling but does nothing about sites already near that ceiling. If a site collection is at 48 GB with a new 50 GB cap, the limit will trip almost immediately. The script also produces no insight into which library or list is consuming space, so a follow-up investigation is always required.
3. Microsoft 365 usage reports
The Microsoft 365 admin center and the SharePoint admin center both surface storage usage data. Sorting the Active sites view by storage used shows current usage and quota ceiling for each site. Microsoft Viva Insights and the Microsoft Graph API can extend this into trend data over time.
These reports are monitoring tools, not enforcement tools. They show which sites are growing fastest and which are approaching their quota, but they cannot apply quotas, block uploads, or trigger cleanup actions automatically. For a more detailed breakdown by library, ShareMaster's Folder inventory report surfaces the data these built-in reports omit.
4. Microsoft 365 Archive
Microsoft 365 Archive (generally available from July 2024) moves inactive site collections to a cold-storage tier at a lower cost than the standard per-user quota pool. Archived sites are read-only and can be reactivated on demand, though reactivation takes time.
Archive is not a quota-enforcement tool in the traditional sense; it is a lifecycle tool for sites that are genuinely inactive. It partially solves a storage problem by moving those sites out of the active pool. Sites with active users, even if over quota, are not archive candidates.
5. ShareMaster Optimise Storage Tools
Unlike the previous four approaches, ShareMaster's Optimise Storage Tools, with Version trimming from its Version History tile, address the root cause of storage growth rather than setting a ceiling on top of it. Together they target the main drivers of SharePoint storage bloat:
- Version trimming (Version History) - removes old major and minor versions across an entire library or site, applying a user-defined cut-off rule. Version history is typically the largest hidden contributor to site storage; a library with 500 files and uncapped versioning can easily hold 5,000 or more version copies.
- Reduce image sizes - compresses large image files stored in document libraries without requiring a download-edit-reupload cycle.
- Remove empty folders - clears folder structures that accumulate in synced libraries over time.
- Delete all files and folders in a library - empties a library, or one subfolder of it, optionally only items older than a date, in a single operation.
- Delete sites and subsites - decommissions sites that are no longer needed rather than leaving them consuming quota indefinitely.
ShareMaster's Reports, such as Folder inventory and Site and subsite storage, show where storage sits before any action is taken, and every clean-up tool previews first, so the highest-impact cleanup targets are visible upfront rather than requiring a manual search through the admin center.
Learn more about Optimise Storage Tools
Decision matrix: which approach fits which scenario?
| Your situation | Best fit |
|---|---|
| Set a quota on a single new site at provisioning time | SharePoint admin center |
| Apply consistent quotas across 50 or more sites in one run | PowerShell (Set-SPOSite) |
| Identify which sites are growing fastest before a renewal decision | Microsoft 365 usage reports + ShareMaster's Storage growth report |
| Reclaim quota from sites no one has accessed in 12 or more months | Microsoft 365 Archive |
| Reduce storage on active sites before purchasing more quota | ShareMaster Version trimming and Reduce image sizes |
| Find out which library inside a site is responsible for quota growth | ShareMaster's Folder inventory report |
| Enforce governance standards across all new and existing sites | PowerShell for caps, ShareMaster's Optimise Storage Tools for ongoing reclamation |
Most organisations end up combining approaches: PowerShell or the admin center to set initial quotas, usage reports to monitor trends, and ShareMaster's Optimise Storage Tools to reclaim storage when sites approach their limits. The combination means quota ceilings become a genuine safety net rather than a recurring incident. See also the version cleanup tools comparison for a deeper look at how version history specifically drives storage growth.
Frequently Asked Questions
What happens when a SharePoint site reaches its storage quota?
Uploads and new item creation stop until the quota is raised or storage is reclaimed. Existing content remains readable. Admins receive a warning notification when the site reaches the warning threshold set alongside the hard limit.
Does the SharePoint recycle bin count against the quota?
Yes. Items in both the first-stage and second-stage recycle bin count against the site collection's allocated storage. A site near its limit may have a substantial portion consumed by files users deleted weeks or months ago. Clearing the recycle bin is often the fastest way to recover quota headroom without deleting live content.
Can I set different storage quotas for different SharePoint sites?
Yes. SharePoint Online supports per-site-collection quotas drawn from the tenant pool (1 TB base plus 10 GB per user licence by default). Project sites can receive larger allocations than standard team sites. PowerShell makes it practical to apply differentiated limits at scale.
Last updated