SharePoint Storage Growth: How to Control Cost Without Hurting Collaboration

Most organisations only think about SharePoint storage when something hurts.

A project team cannot create a new site. Teams users suddenly see warnings. Finance asks why the Microsoft 365 bill increased again. Or IT discovers that meeting recordings alone are consuming a frightening amount of space.

By that point, storage growth is no longer just a capacity question. It is a symptom of deeper issues: no lifecycle, no retention strategy, and years of content being migrated, duplicated, and abandoned.

The good news is that you can reduce storage pressure and cost without turning Microsoft 365 into a locked-down archive. The key is to treat storage as a governance and lifecycle topic, not just a technical limit.

In this post I will walk through how I approach SharePoint and OneDrive storage growth in real environments, decisions IT should make, and practical steps you can take in the next 90 days.

TL;DR

• SharePoint and OneDrive storage growth is mostly a lifecycle and governance problem, not a capacity problem.
• The biggest silent contributors are Teams meeting recordings, unmanaged OneDrive growth, duplicate migration content, and inactive SharePoint sites.
• You can control storage costs without hurting collaboration by focusing on three things: visibility, lifecycle decisions, and light-touch enforcement.
• Start with a tenant-wide storage review, pilot ROT cleanup with friendly business units, and introduce simple lifecycle patterns for new sites and Teams.

Table of Contents

• Why SharePoint Storage Growth Is Really a Governance Problem
• How SharePoint and OneDrive Storage Actually Works
• Real-World Scenario
• Common Mistakes That Make Storage Costs Explode
• Decision Framework: Four Questions To Control Growth
• Technical Recommendations
• ROT Cleanup Approach That Users Accept
• Lifecycle Checklist for SharePoint and OneDrive
• Business Impact
• Practical Checklist
• Final Thoughts

Why SharePoint Storage Growth Is Really a Governance Problem

When storage pressure hits, the first instinct is often technical:

• How much storage do we have left
• Can we buy more
• Is there a way to compress or archive

Those are valid questions, but in Microsoft 365 they are usually symptoms, not causes.

Storage growth is often a sign that:

• Sites and Teams have no clear purpose or end date.
• OneDrive is being treated as a permanent file share, not a personal workspace.
• Meeting recordings and transcripts are saved by default and never revisited.
• Migration projects copied everything, including redundant and obsolete content.
• No one owns lifecycle decisions for sites, documents, and meeting artifacts.

If you only respond by buying more storage or deleting random large files, you might get a short-term fix but you will still carry governance debt:

• Users do not trust where to store things.
• Legal and compliance cannot find authoritative records.
• Copilot and other AI features surface outdated or duplicate content.

Treating storage as a governance and lifecycle topic forces different conversations:

• Who decides when a Team or SharePoint site is no longer active
• What is the retention expectation for meeting recordings and OneDrive content
• What is the process for archiving or deleting old content
• How do we handle migrated legacy content that is rarely used

When those decisions are clear, storage controls become much easier to implement and explain.

How SharePoint and OneDrive Storage Actually Works

Before changing anything, it helps to understand how storage is counted in Microsoft 365 today.

Tenant storage pool

For most licences, SharePoint Online gets:

• A base tenant storage allocation.
• Additional storage based on licensed users.
• Optional extra storage if you purchase add-ons.

This pool is shared across:

• SharePoint sites, including Teams-connected sites.
• Some types of Teams meeting artifacts stored in SharePoint.

OneDrive has its own per-user allocation, typically 1 TB or more per user, separate from the shared SharePoint pool.

Teams and meeting recordings

Most new collaboration content comes from Teams:

• Standard channel files live in the SharePoint site connected to the Team.
• Private and shared channels can create separate SharePoint sites with their own storage and permissions.
• Meeting recordings for channel meetings are usually stored in the Teams-linked SharePoint site in a Recordings folder.
• Meeting recordings for non-channel meetings are stored in the organiser s OneDrive in a Recordings folder.

If you never adjust defaults, those recordings can grow quickly and consume both SharePoint and OneDrive storage.

For a deeper dive into Teams meeting artefacts governance, you can read my post on Teams meeting artifacts governance.

Migration leftovers

In many organisations I work with, there are entire site collections that exist only because someone migrated an old file share or on-premises SharePoint environment:

• Project archives from a decade ago.
• Department shares that have since moved to Teams.
• Staging or temporary sites created during the migration.

Without lifecycle decisions, these sites quietly consume storage and complicate search and Copilot readiness.

If you are planning a migration or have one coming up, I strongly recommend reviewing before you migrate file shares to SharePoint so you do not bring this problem forward again.

Real-World Scenario

Let us look at a realistic scenario that I see often.

A mid sized organisation moved to Microsoft 365 four years ago. They migrated several legacy file shares into SharePoint Online, encouraged staff to use Teams, and did not strictly control who could create Teams or sites.

At first, everything seemed fine. Storage was well within the tenant allocation, and users appreciated the flexibility. OneDrive was promoted as the new personal drive. Recording Teams meetings became common during the pandemic.

Fast forward to today:

• Finance notices that Microsoft 365 storage add ons have been purchased several times.
• A major new project cannot create a new Team because the tenant storage limit is approaching.
• IT discovers that a handful of Teams sites and classic migration sites are consuming a large portion of the storage.
• Copilot pilots are surfacing old documents and outdated policies, undermining trust.

When we dig deeper, we find patterns like these:

1. Legacy migration site

   • A site called Dept Archive hosts a full copy of an old file share.
   • Most documents have not been opened in years.
   • The same department now uses several Teams and their connected SharePoint sites for current work.

2. Teams meeting recordings

   • Recording is enabled for all meetings with generous default retention.
   • Large recurring meetings generate multiple recordings every week.
   • Channel meetings store recordings in the Teams SharePoint sites, often in forgotten folders.

3. Unmanaged OneDrive growth

   • Some power users treat OneDrive as a dumping ground for raw data exports, logs, and massive zip files.
   • When staff leave, their OneDrive is not reviewed before the standard retention and deletion process.

4. Inactive project sites and Teams

   • Projects completed years ago still have active Teams and SharePoint sites.
   • No one is sure if they can delete them, and there is no formal archive process.

The organisation has a few options:

• Buy more storage and accept continued growth.
• Put in hard limits that block users but do not address root causes.
• Or, take a governance and lifecycle approach that realigns storage with current business needs.

The last option takes more upfront work, but it is the only one that reduces both cost and complexity over time.

Common Mistakes That Make Storage Costs Explode

Here are the mistakes I see repeatedly when reviewing SharePoint and OneDrive storage.

1. Treating storage as unlimited

   When Microsoft 365 is introduced, it is often positioned as unlimited cloud storage. Later, when limits and bills appear, users feel that something has been taken away. This erodes trust.

2. Migrating everything from legacy systems

   Many migration projects copy entire file shares and legacy SharePoint sites as is. Redundant, obsolete, and trivial content (ROT) comes along for the ride, doubling or tripling the storage footprint on day one.

3. Ignoring inactive sites and Teams

   Inactive project sites, old departmental sites, and abandoned Teams quietly accumulate. Without policies for managing inactive SharePoint sites, they remain online forever.

4. No retention or lifecycle policy for recordings

   Teams meeting recordings are often left with long or indefinite retention settings. This leads to huge storage consumption from content that has rarely been watched more than once.

5. Overusing OneDrive for shared content

   Staff share files from OneDrive for years, even when a Team or SharePoint site would be a better home. When they leave, those links break and IT struggles to decide what to keep.

6. Too many versions and large files

   Document libraries with unlimited versions and very large design files, videos, or archives can consume enormous storage without anyone noticing.

7. No owner accountability

   When no one owns a site or Team lifecycle, decisions about deletion, archiving, or reclassification are postponed indefinitely.

8. No visibility for IT leadership

   Storage reports exist, but they are not surfaced at the right level. IT directors and CIOs only hear about storage when a crisis arrives.

Decision Framework: Four Questions To Control Growth

To avoid turning this into a never ending storage cleanup project, I use a simple decision framework with four core questions.

1. Where is storage actually going

• Which sites are the top consumers
• How much is in OneDrive vs SharePoint
• How much is due to recordings, media, or legacy content

Without this visibility, any action feels arbitrary.

2. What lifecycle patterns do we support

You do not need a unique policy for every site. Define a small set of patterns:

• Permanent sites, like HR or Finance.
• Long lived collaboration sites, like departments.
• Time bound projects with expected end dates.
• Temporary or experiment spaces.

Each pattern has default expectations for retention, archive, and deletion.

3. What retention and storage controls align with those patterns

For each pattern, decide:

• Retention policy or label behaviour.
• Default versioning settings.
• Meeting recording retention for related Teams.
• When and how to archive or delete.

This is where tools like retention policies, content types, and sensitivity labels come in. They support the model; they are not the model.

4. How do we enforce just enough control

Finally, decide how strict you want to be:

• Soft controls: reports, dashboards, quarterly reviews, nudges to owners.
• Hard controls: auto archive, retention driven deletions, limits on Team or site creation.

Most organisations start with soft controls and move to targeted hard controls where risk and cost are highest.

Technical Recommendations

Once the decisions above are made, you can implement them with practical, low friction technical steps.

1. Build a storage report for SharePoint and OneDrive

Start by getting a current picture of storage usage. The SharePoint admin center provides basic reports, but I often supplement this with PowerShell.

Example using the SharePoint Online Management Shell:

Connect-SPOService -Url https://contoso-admin.sharepoint.com
Get-SPOSite -Limit All -Detailed |
  Select Url, Owner, Template, StorageUsageCurrent, StorageQuota |
  Sort-Object StorageUsageCurrent -Descending |
  Export-Csv -Path .\SPOStorageReport.csv -NoTypeInformation

This produces a tenant wide report showing which sites consume the most storage. You can filter for sites based on template, such as Teams connected sites or classic migration sites.

For OneDrive, PnP PowerShell can help identify heavy users:

Connect-PnPOnline -Url https://contoso-admin.sharepoint.com -Interactive
Get-PnPTenantSite -IncludeOneDriveSites |
  Where-Object { $_.Template -eq 'SPSPERS' } |
  Select Url, Owner, StorageUsageCurrent |
  Sort-Object StorageUsageCurrent -Descending

Use this to identify a handful of OneDrive accounts that might need attention or coaching.

2. Tune versioning and large file behaviour

Document library versioning is important, but unlimited versions on large files can be costly.

Practical steps:

• For general collaboration libraries, consider keeping 50 to 100 versions instead of unlimited.
• For libraries with large design files or videos, set lower version limits and consider a separate site or library for raw assets.
• Educate power users to avoid uploading huge zip files or repeated exports when a shared location or dataset would be better.

You can combine these changes with SharePoint document library best practices so users do not feel that storage control is the only goal.

3. Adjust Teams meeting recording behaviour

Work with your Teams admin to:

• Set default recording policies that match business needs.
• Configure meeting recording retention so that recordings expire after a defined period unless explicitly retained.
• Align recording behaviour with retention policies and labels for key functions like HR or Legal.

As covered in the separate article on Teams meeting artifacts governance, this is both a storage and a risk topic.

4. Manage inactive sites and Teams

Combine storage data with site activity to identify inactive sites that are heavy storage consumers.

• Use the SharePoint admin center or reports to find sites with no recent activity.
• Cross check with storage usage to prioritise high impact candidates.
• Apply an archive workflow that involves the site owner, not just IT.

If you need a detailed approach, I have outlined patterns for managing inactive SharePoint sites that you can adapt.

5. Use retention policies and labels thoughtfully

Retention configuration should be driven by lifecycle decisions, not the other way around.

Consider:

• Tenant level retention policies for general collaboration content.
• Retention labels for critical records and regulated content.
• Shorter retention for transient content like drafts, working folders, and some meeting recordings.

Sensitivity labels can complement this by controlling sharing and external access, but they do not replace lifecycle policy.

6. Build a simple storage and lifecycle dashboard

For IT directors and CIOs, a simple Power BI or Excel dashboard can be more effective than a complex portal.

Include:

• Top 20 sites by storage usage.
• Storage usage by category: collaboration, archives, recordings, migration.
• OneDrive storage distribution by department or region.
• Trend over time for total storage and key categories.

This dashboard becomes the basis for quarterly governance reviews and discussions with business owners.

ROT Cleanup Approach That Users Accept

ROT stands for redundant, obsolete, and trivial content. Removing ROT is usually the fastest and safest way to reduce storage pressure.

Here is a practical approach that avoids surprises.

1. Start with reports, not deletion

Produce lists of:

• Inactive sites with high storage.
• Libraries with very old last modified dates.
• OneDrive accounts with large storage but low recent activity.

Share these reports with business owners before you propose any deletion.

2. Classify content into tiers

For each candidate site or library, classify content into simple tiers:

• Tier 1: Active or business critical.
• Tier 2: Reference or archive, needed for a defined period.
• Tier 3: ROT or low value.

Owners do not need to inspect every file; patterns and date ranges are usually enough.

3. Align with retention and legal requirements

Confirm whether any regulatory or legal holds apply before deleting anything. Work with compliance or legal as needed.

4. Offer archiving options

Give owners a safe option before deletion, for example:

• Move Tier 2 content into an archive library with stricter permissions and clear naming.
• Apply specific retention labels or policies.
• For truly cold content, export to a separate archive storage if your organisation uses that model.

5. Automate what you can

Use tools like Power Automate or scripts to:

• Move old files based on last modified date.
• Apply retention labels in bulk.
• Notify owners when potential ROT thresholds are met.

The goal is to make repeated cleanup less manual and more part of the normal lifecycle.

Lifecycle Checklist for SharePoint and OneDrive

When I run a SharePoint storage and lifecycle governance review, I typically walk through a checklist like this:

• Do we have clear categories for sites and Teams with lifecycle expectations
• Is there a process to request new sites and Teams that captures purpose and expected duration
• Are there default retention policies for general collaboration content
• Are versioning settings standardised, with exceptions for specific scenarios
• Are Teams meeting recording policies aligned with business and regulatory needs
• Do we have an archive pattern for project and temporary sites
• Is there a defined process when staff leave, including OneDrive review
• Are owners identified and reachable for all major sites and Teams
• Do we have a simple, regular review process for storage and inactive sites
• Are migration projects required to classify and, where possible, clean ROT before or shortly after migration

If you want to go deeper on document centric design before AI and Copilot, you might also find the article on SharePoint document library design and governance helpful.

Business Impact

Storage growth often shows up as a technical line item, but the impact is broader.

IT and operations

• Reduced firefighting: With clear lifecycle patterns and reports, IT spends less time reacting to capacity alerts and ad hoc deletion requests.
• Predictable spending: Instead of sudden storage add on purchases, you can forecast growth and see where cost is coming from.
• Fewer risky quick fixes: IT avoids ad hoc deletions or hard limits that disrupt projects and erode trust.

Business owners and users

• Clearer workspaces: Users are less likely to be overwhelmed by outdated Teams, sites, and document libraries.
• Better search and Copilot results: AI and search can focus on current, authoritative content instead of old duplicates.
• Less confusion about where to store content: Lifecycle patterns and site categories make choices simpler.

Compliance and risk

• Reduced exposure from meeting recordings: Shorter, well governed retention for recordings reduces the volume of sensitive content stored indefinitely.
• Improved records management: Retention policies and labels aligned with lifecycle patterns make it easier to demonstrate compliance.
• Less shadow IT: When storage and lifecycle are well managed, users are less likely to seek alternative storage solutions outside Microsoft 365.

This is why I often position storage growth conversations as part of broader SharePoint governance consulting rather than a narrow storage tuning exercise.

Practical Checklist

If you want to take action in the next 60 to 90 days, here is a concrete checklist.

1. Run a tenant wide storage report

   • Use admin reports and PowerShell to identify top storage consumers in SharePoint and OneDrive.

2. Categorise top 50 sites

   • Classify them as department, project, archive, or migration legacy.

3. Review meeting recording policies

   • Adjust retention defaults and align them with legal and business needs.

4. Pilot a ROT cleanup

   • Pick one department or business unit, pair IT with business owners, and run through the ROT classification and cleanup approach.

5. Standardise versioning settings

   • Define default version limits and apply them across major libraries, with documented exceptions.

6. Define lifecycle patterns for sites and Teams

   • Create a short document describing standard patterns and their lifecycle expectations.

7. Introduce light weight creation controls

   • If you currently allow anyone to create Teams and sites, consider adding a simple request form that captures purpose and expected duration.

8. Set up a storage and lifecycle dashboard

   • Provide IT leadership with a simple view of storage trends and key metrics.

9. Align migration plans with lifecycle

   • For upcoming migrations, require teams to classify content and, where possible, avoid migrating ROT wholesale. For more guidance, see the migration planning guide for IT directors.

10. Schedule quarterly governance reviews

    • Review storage reports, inactive sites, and lifecycle adherence with key stakeholders.

Final Thoughts

SharePoint and OneDrive storage growth is not going away. As Teams, Copilot, and collaboration patterns evolve, content will continue to multiply.

The organisations that handle this well are not the ones with the strictest controls or the biggest storage budgets. They are the ones that treat storage as part of governance and lifecycle, make a few clear decisions, and implement light but consistent technical controls.

If you feel that your tenant is drifting toward storage sprawl, it is better to act now while you still have breathing room. Start with visibility, define your lifecycle patterns, and pilot a ROT cleanup where the business is most supportive.

If you would like a structured outside view, I offer a SharePoint storage and lifecycle governance review as part of my SharePoint governance consulting. We can walk through your current storage footprint, lifecycle patterns, and governance decisions, then design a realistic roadmap that fits your organisation.

You can also reach out via the contact page to discuss a focused review or broader SharePoint consulting services that includes migration, permissions, and Copilot readiness.