SharePoint Storage Costs: What You're Actually Paying
How SharePoint Online storage costs work in Microsoft 365. Covers per-plan allocations, overage pricing, the biggest storage consumers, and how a typical small business can reduce costs with basic cleanup.
Last updated: 2026-05-24
SharePoint Online storage is included with every Microsoft 365 subscription, which creates the impression that it is free. It is not. Every plan comes with a finite pool of storage, and exceeding that pool means paying Microsoft for additional capacity at a rate that adds up faster than most administrators expect. Understanding how SharePoint storage costs actually work is the first step toward controlling them.
Disclaimer: This article is for informational purposes only and does not constitute legal or financial advice. Pricing and plan details referenced here are based on publicly available Microsoft documentation as of early 2026 and may change. Verify current pricing directly with Microsoft.
How SharePoint Storage Allocation Works
Microsoft 365 provides SharePoint storage as a tenant-wide pool rather than a per-user bucket. The pool starts with a base allocation of 1 TB for the organization, plus an additional per-user allocation that depends on the plan.
Here is how the per-user allocations break down across common business plans:
- Microsoft 365 Business Basic -- 1 TB base + 10 GB per licensed user
- Microsoft 365 Business Standard -- 1 TB base + 10 GB per licensed user
- Microsoft 365 Business Premium -- 1 TB base + 10 GB per licensed user
- Microsoft 365 E3 -- 1 TB base + 10 GB per licensed user
- Microsoft 365 E5 -- 1 TB base + 10 GB per licensed user
For a company with 20 users on a Business Standard plan, the total SharePoint storage pool is 1 TB + (20 x 10 GB) = 1.2 TB. That is the ceiling before overage charges apply. Note that this pool is shared across all SharePoint sites in the tenant -- it is not divided equally among users or sites.
OneDrive for Business storage is separate. Each user gets 1 TB of personal OneDrive storage on most plans, which does not count against the SharePoint pool. However, files shared extensively through OneDrive sometimes get copied into SharePoint sites by users who do not understand the distinction, which consumes pool storage unnecessarily.
What Overage Storage Costs
When the tenant pool runs out, the options are to buy additional storage or delete existing content. Microsoft sells additional SharePoint storage at $0.20 per GB per month. That translates to $2.40 per GB per year, or $200 per month for an extra 1 TB.
For context, that $200 per month is often more than the combined cost of several user licenses on a Business Basic plan. It is a significant recurring expense, especially for small businesses where the IT budget is already tight. And because storage tends to grow rather than shrink, overage charges tend to increase over time unless something is done to manage what is being stored.
The Biggest Storage Consumers
Before buying additional storage, it is worth understanding what is actually consuming the existing pool. In most SharePoint environments, four categories account for the majority of storage usage.
Version History
SharePoint keeps a copy of every version of every document by default. For frequently edited files, this means dozens or even hundreds of versions accumulating silently. A 5 MB PowerPoint deck that has been edited 50 times is consuming 250 MB -- and that is just one file. Across an entire tenant, version history routinely accounts for 30 to 50 percent of total storage consumption. Microsoft has introduced automatic version history trimming in newer tenants, but many environments still carry legacy versions that were never cleaned up.
Recycle Bin
When users delete files, those files move to the site recycle bin and stay there for 93 days. After that, they move to the second-stage recycle bin for another 93 days. During this entire window, deleted content continues to count against the storage pool. A large cleanup effort that deletes hundreds of gigabytes will not free up storage until the recycle bin is emptied -- something administrators need to do manually or wait out.
Large Media Files
Video files, high-resolution images, design assets, and ZIP archives are common in SharePoint libraries. A single training video can consume several gigabytes. Teams that store marketing assets or recorded meetings in SharePoint often find these files dominating their storage reports. SharePoint is not optimized for large media storage, and Microsoft Stream or Azure Blob Storage are better suited for video content.
Abandoned Sites
Old project sites, former team sites, and test sites that no one has visited in months still consume storage. Their content sits untouched, their document libraries full of outdated files, and their storage usage invisible to anyone who is not actively looking. In organizations without site lifecycle management, abandoned sites can account for 10 to 20 percent of total storage.
How to Check Current Storage Usage
The SharePoint Admin Center provides a straightforward view of storage consumption. Here is how to access it:
- Sign in to the Microsoft 365 admin center at admin.microsoft.com
- Navigate to Admin centers and select SharePoint
- In the SharePoint admin center, select Active sites from the left navigation
- The Storage used column shows how much each site is consuming
- At the top of the page, a summary bar shows total storage used versus total storage available
- Click on any individual site to see a breakdown of storage by library
For a more detailed view, select Settings in the SharePoint admin center and then Site storage limits. This page shows the overall tenant storage allocation and how much is currently in use. Sites can also be sorted by storage consumption to quickly identify the largest offenders.
Administrators with access to PowerShell can run the Get-SPOSite cmdlet with the -Detailed flag to export storage data for all sites into a spreadsheet for deeper analysis.
Calculating Potential Savings
Consider a typical 20-person company on Microsoft 365 Business Standard. The total SharePoint storage pool is 1.2 TB. After two years of use, the tenant is consuming 1.5 TB, meaning 300 GB of overage storage at $0.20 per GB per month -- a cost of $60 per month or $720 per year.
A basic cleanup effort might recover storage from three areas:
- Version history trimming -- Reducing versions on older files from unlimited to 50 major versions across the most active libraries could recover 150 to 200 GB in a tenant of this size
- Recycle bin purge -- Emptying second-stage recycle bins across all sites might recover 30 to 50 GB
- Abandoned site cleanup -- Archiving or deleting two or three unused project sites could recover another 50 to 100 GB
That is a potential recovery of 230 to 350 GB. In the scenario above, that would eliminate the overage entirely, saving the full $720 per year. Even a partial cleanup that recovers 150 GB would cut the overage bill roughly in half.
These numbers are conservative. Organizations that have never performed a storage audit often find they can recover 25 to 40 percent of their total storage consumption through cleanup alone, without deleting any content that anyone is actively using.
Setting Up Ongoing Storage Management
One-time cleanup solves the immediate problem. Preventing recurrence requires a few ongoing practices:
- Set version limits -- Configure document libraries to retain a maximum of 50 major versions rather than the default unlimited setting
- Establish site lifecycle reviews -- Review all sites quarterly and archive or delete any that have not been accessed in 90 days
- Set storage quotas per site -- Use the SharePoint admin center to assign individual storage limits to sites, preventing any single site from consuming the entire pool
- Educate users -- Make sure team members understand that SharePoint storage is finite and that large media files belong in dedicated services, not document libraries
Storage costs are one of the most controllable expenses in a Microsoft 365 environment. The pool allocation is fixed by the plan, but how efficiently that pool is used depends entirely on how the environment is managed.
Related Articles
- SharePoint Governance: A Framework for Small Businesses
- SharePoint Permission Levels Explained: Owner, Member, and Visitor
- Sensitivity Labels in Microsoft 365: A Practical Guide
- Does Microsoft Copilot Use Your Data for Training?
- Data Governance Before AI: Why You Need to Clean Up Before Turning On Copilot