If you’re asking how do I reduce SharePoint Online storage costs for my organization, you’re already asking the right question, but the answer requires more than a one-time cleanup. SharePoint Online storage overages are billed at $0.20 per GB per month, roughly $2,400 per terabyte per year. Many organizations don’t notice the bill climbing until the tenant is already past its included quota. Storage waste rarely comes from one obvious source. It builds slowly across many sites: bloated version histories, full recycle bins, stale project sites nobody retires, and retention policies that quietly preserve copies of everything ever deleted or modified.
The harder truth is that most organizations have no native tool that gives them a tenant-wide picture of where storage is actually going. Without that breakdown, it’s nearly impossible to prioritize which sites to clean first or estimate how much each remediation tactic will reclaim. That visibility gap is where the real cost hides, and it’s the primary reason storage costs grow without anyone catching them at the right time. The rest of this guide walks through the audit, cleanup, archiving, and governance steps so you can reduce SharePoint Online storage costs in a structured, repeatable way.
How SharePoint storage billing works (and where the bill quietly leaks)
Tenant-wide pooled storage and per-license allocation
SharePoint Online does not assign storage per user or per site. Every tenant gets a shared pool: 1 TB base plus 10 GB per eligible Microsoft 365 license. A 500-seat tenant has roughly 6 TB of included storage. If that pool is exceeded, Microsoft’s pay-as-you-go overage kicks in at $0.20 per GB per month, about $2,400 per terabyte per year. That cost is metered and billed in arrears against the connected Azure subscription, so charges can accumulate for weeks before anyone reviews them.
The hidden storage drain most admins miss
When retention policies, litigation holds, or eDiscovery holds are active, SharePoint automatically creates and populates a hidden library called the Preservation Hold library. Every deleted file and every modified version covered by a hold gets copied there and preserved until the retention requirement expires. That library counts against the site’s storage quota just like any other content. Admins who have manually cleaned up sites are often confused when storage doesn’t drop as expected, the Preservation Hold library can often be the cause, quietly filling in the background even after a thorough manual cleanup.
Why storage creep is hard to spot with native tools
Native Microsoft 365 admin center reports show total site size, but they don’t break down how much of that size comes from live files, version history, recycle bin content, or preservation holds. Without that layer-by-layer breakdown, prioritizing which sites to address first, and predicting how much each tactic will actually reclaim, is largely guesswork.
How do I reduce SharePoint Online storage costs? Start with a proper audit
Using the SharePoint admin center to find top consumers
Start in the SharePoint admin center under Sites > Active Sites, then sort by the Storage column. Focus your initial effort on the top 10 to 20 sites, which often represent a disproportionate share of usage across the tenant and are the fastest path to meaningful reclamation. Export the list, including site name, storage used, and last-activity date, for offline tracking so you can measure before-and-after results for each site you touch.
Breaking down each site: files, versions, and recycle bin
For each high-usage site, inspect three distinct storage layers: active files (the content users actually work with), version history (which can be significantly larger than active files in high-churn libraries), and recycle bin content (frequently overlooked and rarely emptied on a schedule). Each layer calls for a different remediation tactic. Knowing which layer is the actual problem changes which action you take, so don’t skip the breakdown step.
How Chronom AI automates this step across your entire tenant
Manually clicking through sites is not a realistic audit strategy at enterprise scale. Chronom AI uses a read-only Microsoft Graph API scan to identify storage waste patterns across the full tenant without touching or altering any tenant data. The output is a per-site, per-layer savings report with annualized cost figures formatted for leadership review or vendor negotiation, giving IT teams the visibility they need to act quickly and confidently.
High-impact cleanup tactics that reclaim capacity fast
Reduce SharePoint Online storage costs: trim version history first
Version history is typically the single largest lever for Microsoft 365 storage optimization. A document library set to keep 500 versions on a high-churn file can accumulate gigabytes before anyone notices. For high-churn media libraries, consider reducing major version limits to a range of 10 to 30. For standard document libraries, somewhere in the range of 50 to 100 versions tends to balance recovery value against storage consumption, though the right number will depend on your team’s actual recovery habits and business requirements. Microsoft’s version history trimming feature in the SharePoint admin center supports removing low-value versions retroactively without affecting the current version of any file.
Purge both stages of the recycle bin
Deleted content stays in the first-stage recycle bin for 93 days and then moves to the second-stage recycle bin before permanent deletion. Both stages count against the site’s storage quota, and storage does not actually reclaim until both are cleared. Admins should empty both stages on a scheduled basis, especially immediately after any large cleanup effort, because the reclaim won’t register in storage reports until the bins are fully purged.
Remove orphaned, duplicate, and stale content
Abandoned project sites, duplicate files stored across multiple document libraries, and content untouched for 12 to 24 months are common storage drains that don’t surface clearly in native reports. Identifying this content at scale requires automated scanning because manual site-by-site review is too slow across a large tenant. Removing or archiving this content eliminates waste without disrupting active users, and it’s typically the third-largest reclamation opportunity after version history and recycle bins.
Archiving inactive content to dramatically cut storage costs
When to archive versus when to delete
Not every inactive site should be deleted. Some content needs to be retained for compliance, project records, or historical reference, but it doesn’t need to live in active SharePoint storage. Microsoft 365 Archive is the native option for inactive sites: it removes content from the active storage pool and moves it to a colder tier at $0.05 per GB per month, a 75% reduction compared to the active overage rate of $0.20. Content remains searchable and compliant, but the site must be reactivated before users can access it again.
The Azure Blob cost comparison for cold data
For truly cold data that rarely needs to be accessed, Azure Blob Storage is dramatically cheaper than keeping content in SharePoint Online. The cost comparison is stark:
- SharePoint Online pay-as-you-go overage: $0.20 per GB per month
- Azure Blob Cool tier: approximately $0.0115 per GB per month (about 17x cheaper)
- Azure Blob Cold tier: approximately $0.0045 per GB per month (about 44x cheaper)
- Azure Blob Archive tier: approximately $0.002 per GB per month (about 100x cheaper)
For organizations with multi-terabyte cold data sets, offloading to Azure Blob is one of the fastest ways to reduce SharePoint Online storage costs at scale. That said, retrieval fees apply when archived data is accessed, and each tier enforces minimum retention periods: 30 days for Cool, 90 days for Cold, and 180 days for Archive. These tiers work best for content you’re confident won’t need frequent retrieval.
Governance policies that stop storage from growing back
Site-level storage quotas and lifecycle controls
Set explicit storage quotas on high-risk sites, collaboration hubs, project sites, and team channels. As a site approaches its limit, admins can be alerted through the SharePoint admin center before overage becomes a billing problem. Pair quotas with inactive-site policies using SharePoint Advanced Management, which can automatically archive or flag sites with no activity for a defined period. This combination shifts storage governance from reactive to proactive.
Version limits and large-file upload policies
Apply lower version limits proactively to libraries that handle large files such as video recordings, CAD files, or design assets. A single large-file library can consume as much storage as dozens of standard document libraries. Setting version thresholds and upload governance policies for these libraries prevents the bloat from returning. Without these controls in place, the same cleanup work is likely to be needed again within a year or two.
Scoping retention policies to limit compliance-driven storage growth
Retention policies are necessary for compliance, but overly broad scope causes the Preservation Hold library to fill rapidly across many sites simultaneously. Audit your retention policies annually, narrow their scope to what is actually required by regulation or internal policy, and set expiration dates wherever permitted. Deliberate scoping is the difference between retention as a compliance tool and retention as an unmanaged storage drain that quietly inflates your monthly bill.
A practical 30/60/90-day plan to reduce SharePoint Online storage costs
Days 1 to 30: audit, identify, and execute quick wins
Run a full tenant audit using the SharePoint admin center or Chronom AI to get a ranked list of storage consumers. In the first 30 days, focus on the top 10 sites: purge both recycle bin stages, trim version history in the largest libraries, and delete clearly stale or orphaned content. Early wins here can be substantial depending on your tenant’s history, and the goal is measurable progress before month-end reporting, not a perfect solution.
Days 31 to 60: archive inactive sites and adjust versioning policies
Identify sites with no activity in the past 12 months and move eligible ones to Microsoft 365 Archive or an appropriate cold-storage tier. Update version history limits across high-churn and large-file libraries with caps that reflect actual business needs. This phase converts audit findings into durable savings rather than a one-time cleanup that rebuilds the following quarter.
Days 61 to 90: establish governance and continuous monitoring
Implement site quotas, inactive-site lifecycle policies, and a recurring retention policy review. Set up continuous monitoring so new drift is caught before it accumulates. Optimization done once without ongoing governance is a temporary fix. The goal is a self-maintaining storage posture where waste is flagged automatically before it becomes a billing problem, not after the invoice arrives.
Turning visibility into realized savings
Reducing SharePoint Online storage costs doesn’t require a months-long project. It requires visibility first, then execution in the right order. Start with the audit, focus cleanup on version history and recycle bins, archive what genuinely needs to be kept, and put governance in place so the problem doesn’t quietly rebuild over the next renewal cycle.
For most teams, the biggest obstacle is getting an accurate, tenant-wide picture of where storage is actually going. That’s the gap Chronom AI was built to close. Using a read-only Microsoft Graph API scan, Chronom AI maps storage waste by site and layer, giving IT teams and finance stakeholders the prioritized, annualized view they need to act without months of manual investigation.
If you’re still asking how do I reduce SharePoint Online storage costs for my organization and aren’t sure where to start, reach out to the Chronom AI team to schedule a free tenant scan and see exactly where your storage dollars are going.