How to Reduce SharePoint Online Storage Usage

Introduction

Finding practical ways to reduce SharePoint Online storage is a priority for many small and mid-sized businesses that are watching their Microsoft 365 costs climb month after month. SharePoint Online allocates storage at the tenant level, and once that pool fills up, Microsoft charges for additional capacity — costs that can add up quickly if left unmanaged. The good news is that most organizations have significant room to reclaim space without purchasing extra storage, simply by cleaning up redundant files, adjusting version history settings, and rethinking how content is archived. This guide walks you through exactly how to do that, with practical steps any IT administrator or business owner can follow.

Understanding SharePoint Online Storage Allocation

SharePoint Online does not give each site collection an unlimited bucket of space. Instead, Microsoft 365 tenants receive a pooled storage quota that starts at 1 TB and grows by 10 GB for every Microsoft 365 license assigned in the organization. For example, a company with 50 users on Microsoft 365 Business Standard would receive 1 TB plus 500 GB, totaling 1.5 TB shared across all SharePoint sites, OneDrive accounts, and Microsoft Teams channels. When that pool runs low, document uploads fail, Teams channels stop accepting files, and collaboration grinds to a halt.

What surprises many administrators is how quickly that quota disappears. Version history is one of the biggest culprits — SharePoint keeps previous versions of every file by default, and a document that has been edited 50 times can consume 50 times the disk space of a single copy. Recycle bins also count against your quota, meaning deleted files are not truly "gone" until they are permanently purged. Understanding these mechanics is the foundation for any meaningful storage reduction effort, because you cannot fix what you do not understand.

How SharePoint Counts and Consumes Your Storage

Every file uploaded to a SharePoint document library consumes storage against the tenant pool. This includes files stored in Microsoft Teams (which uses SharePoint on the back end), files in OneDrive for Business, and any content in SharePoint site collections. Version history multiplies that consumption dramatically. If your organization has the default version limit of 500 major versions enabled, a 10 MB PowerPoint file that gets revised frequently could theoretically occupy gigabytes of space on its own. SharePoint also stores metadata, list attachments, and OneNote notebooks, all of which count toward the same pool.

The two-stage recycle bin is another hidden consumer. When a user deletes a file, it moves to the site recycle bin for 93 days before permanent deletion. Administrators can also restore items from a second-stage recycle bin during that same window. Until those 93 days expire or an admin permanently deletes the items, all that data counts against your storage quota. Knowing this helps explain why storage sometimes appears to shrink even when users feel like they are not uploading much — old deleted content is simply sitting in the bin, waiting to expire.

Step-by-Step Guide

1. Audit Your Current Storage Usage: Start by logging into the SharePoint admin center at admin.microsoft.com, navigating to SharePoint, and reviewing the Active Sites report to see which site collections are consuming the most space. Export the list to a spreadsheet so you can prioritize cleanup efforts on the heaviest offenders first rather than working blindly across hundreds of sites.
2. Reduce Version History Limits Across Site Collections: In the SharePoint admin center, open each site collection's settings and lower the major version limit from the default 500 to a more reasonable number such as 10 or 20, which is sufficient for most business workflows. You can also use PowerShell with the PnP.PowerShell module to apply version limits in bulk across all libraries, saving hours of manual configuration work.
3. Delete Old Versions From Existing Libraries: Changing the version limit going forward does not remove the thousands of old versions already stored — you need to actively delete them. Use the SharePoint admin center's built-in version history trimming feature, or run a PowerShell script that iterates through each document library and calls the RecycleBin or version deletion methods to purge outdated copies.
4. Empty Site and Tenant Recycle Bins: Navigate to each site collection, open the Recycle Bin, select all items you no longer need, and permanently delete them to immediately reclaim that space. For a faster approach, SharePoint administrators can use PowerShell or the SharePoint admin center to clear the second-stage recycle bin at the tenant level, which removes items that users have already deleted but that are still counting against your quota.
5. Identify and Remove Duplicate or Orphaned Files: Use Microsoft 365 storage reports combined with third-party tools such as ShareGate or Orchestry to scan for duplicate files, stale content that has not been accessed in over a year, and orphaned site collections that belong to former employees or disbanded projects. Removing or archiving this content can free up substantial space, especially in organizations that have been using SharePoint for several years without a formal governance plan.
6. Move Cold Content to Microsoft 365 Archive or Azure Blob Storage: Files that must be retained for compliance but are rarely accessed can be moved out of active SharePoint storage using Microsoft 365 Archive, which stores content at a lower per-GB cost, or exported to Azure Blob Storage for long-term retention. This approach keeps your active SharePoint pool lean while still meeting legal hold and records retention requirements without deleting anything permanently.
7. Establish an Ongoing Governance Policy: Set up automated storage alerts in the SharePoint admin center so administrators receive notifications when a site collection reaches 70% or 90% of its allocated quota, giving the team time to act before uploads fail. Create a written policy that defines version history limits, recycle bin review schedules, and a process for decommissioning sites when projects end, so storage creep does not quietly return within a few months.

SharePoint Storage Management Approaches Compared

Best Practices

• Set Version Limits at Library Creation: Configure version history limits when a new document library is created rather than waiting until storage becomes a problem, so you never accumulate thousands of unnecessary versions in the first place.
• Schedule Monthly Recycle Bin Reviews: Assign an administrator to review and permanently empty the tenant-level recycle bin on a monthly cadence to ensure deleted content is not silently consuming quota for up to 93 days.
• Apply Site Quotas to High-Risk Collections: Use the SharePoint admin center to set individual storage quotas on site collections belonging to large teams or departments that tend to upload large media files, preventing any single site from consuming the entire tenant pool.
• Educate Users on Large File Alternatives: Train staff to store large video files in Microsoft Stream rather than uploading them directly to SharePoint document libraries, since Stream is optimized for video and does not count against the SharePoint storage pool in the same way.
• Review and Archive Inactive Sites Quarterly: Run a quarterly report on site collections that have had no activity in 90 days or more and either archive them using Microsoft 365 Archive or delete them after confirming with the site owner that the content is no longer needed.

Frequently Asked Questions

How Much Storage Does SharePoint Online Include by Default?

Every Microsoft 365 tenant starts with 1 TB of SharePoint Online storage, plus an additional 10 GB for each licensed user in the organization. This pooled quota is shared across all SharePoint site collections, Microsoft Teams file storage, and OneDrive for Business accounts. If your organization has 100 users on eligible Microsoft 365 plans, your total pool would be 2 TB. Once that limit is reached, Microsoft offers additional storage add-ons at an extra monthly cost.

Does Version History Really Consume That Much Space?

Yes — version history is consistently one of the top two or three causes of unexpected storage consumption in SharePoint Online environments. With the default limit of 500 major versions, a frequently edited file can store hundreds of copies of itself, each taking up space proportional to the file's size. A 5 MB Excel workbook edited daily for a year with no version cleanup could accumulate over 1 GB of version data on its own. Reducing version limits to 10–20 versions is a practical change that most businesses find has no negative impact on their day-to-day work.

Will Deleting Old Versions Affect Files Users Are Currently Working On?

Deleting old versions removes only the historical snapshots of a file, not the current version that users see and edit. The most recent copy of every document remains completely intact after a version purge. Users may lose the ability to roll back to a very old revision, which is why it is worth communicating the change to staff and setting a reasonable retention window — such as keeping the last 10 or 20 versions — rather than deleting all version history entirely. For most business documents, the ability to recover from the last week or two of edits is more than sufficient.

Can Microsoft Teams Storage Be Managed Separately From SharePoint?

Microsoft Teams stores all files shared in channels directly in a SharePoint document library behind the scenes, so Teams file storage and SharePoint storage are the same pool and cannot be separated. Each Teams channel maps to a folder inside the associated SharePoint site, and every file uploaded in a Teams conversation counts against your SharePoint quota. To reduce Teams-related storage consumption, you need to manage the underlying SharePoint site collection just as you would any other site, including version history limits and recycle bin cleanup.

Is Microsoft 365 Archive a Good Long-Term Solution for Reducing Active Storage?

Microsoft 365 Archive is a solid option for organizations that need to retain large volumes of content for compliance or legal reasons but do not need that content to be actively accessible to everyday users. Archived content is moved out of the active SharePoint pool and stored at a lower per-GB cost, with the trade-off that retrieval takes longer and requires reactivation. For truly cold data — records that must be kept for seven years but are almost never opened — Archive is a cost-effective middle ground between paying for active SharePoint storage and deleting content entirely. It is worth evaluating alongside your existing records retention policy before committing to a specific archiving strategy.

Managing SharePoint Online storage is an ongoing process, not a one-time fix, and Always Beyond helps SMBs build the policies, automation, and governance frameworks needed to keep storage costs under control without disrupting day-to-day operations. Whether you need help auditing your current usage, scripting a bulk version cleanup, or setting up a long-term archiving strategy to reduce SharePoint Online storage, our team has the Microsoft 365 expertise to get it done efficiently — contact Always Beyond today.