Administration

SharePoint Online Storage Management: Administrator Guide 2026

Optimize SharePoint Online storage usage, understand tenant storage pools, manage site quotas, identify version history bloat, reclaim wasted space, and implement storage governance policies to control costs and prevent read-only site incidents.

Errin O'ConnorFebruary 24, 202612 min read
SharePoint Online Storage Management: Administrator Guide 2026 - Administration guide by SharePoint Support
SharePoint Online Storage Management: Administrator Guide 2026 - Expert Administration guidance from SharePoint Support

SharePoint Online Storage Management: Administrator Guide 2026

Storage management is one of the most neglected aspects of SharePoint Online administration — until a critical site goes read-only because it hit its storage quota. This guide covers proactive storage management: understanding how SharePoint Online storage works, monitoring usage, reclaiming space, and implementing governance to prevent future problems.

SharePoint migration process workflow from planning to go-live
Step-by-step SharePoint migration workflow

---

How SharePoint Online Storage Works

Tenant Storage Pool

Your Microsoft 365 subscription includes a shared storage pool for all SharePoint sites (excluding OneDrive):

  • Base allocation: 1TB per tenant + 10GB per licensed user
  • Example: 500 users = 1TB + 5TB = 6TB total
  • Overage: Sites approaching limits go read-only — Microsoft does not auto-expand
  • Additional storage: $0.20/GB/month via Microsoft 365 admin center

OneDrive Storage

OneDrive is separate from the SharePoint pool:

  • Standard: 1TB per user
  • Extended: Up to 5TB per user on qualifying plans

Per-Site Storage

Default: Sites share from the pool (no individual limits). Best practice: Set individual site quotas to prevent one site consuming the entire pool. Maximum per site: 25TB.

---

Monitoring Storage Usage

SharePoint Admin Center Report

Active Sites → Sort by "Storage used" descending → identifies largest sites immediately.

PowerShell Storage Audit

```powershell

Connect-SPOService -Url "https://yourtenant-admin.sharepoint.com"

Get-SPOSite -Limit All |

Select-Object Url, StorageUsageCurrent, StorageQuota, Title |

Sort-Object StorageUsageCurrent -Descending |

Export-Csv "SharePoint-Storage-Report.csv" -NoTypeInformation

```

Storage Alerts

Per-site: Active Sites → [Site] → General → Edit Storage limit → Set quota + email alert at 80%.

---

Identifying Storage Waste

Version History (Biggest Culprit)

With default 500 version limits, a 5MB document edited 100 times = 500MB storage for that single document.

At scale: 10,000 documents × 50 versions avg × 2MB avg = 1TB in version history alone.

Identify version storage hotspots:

```powershell

Connect-PnPOnline -Url "https://yourtenant.sharepoint.com/sites/yoursite"

$libraries = Get-PnPList | Where-Object { $_.BaseType -eq "DocumentLibrary" }

foreach ($lib in $libraries) {

$files = Get-PnPListItem -List $lib.Title -Fields "FileRef,File_x0020_Size"

foreach ($file in $files) {

$versions = Get-PnPFileVersion -Url $file["FileRef"] -ErrorAction SilentlyContinue

if ($versions.Count -gt 50) {

Write-Output "$($file['FileRef']): $($versions.Count) versions"

}

}

}

```

Fix: Reduce version limits on high-traffic libraries. Reducing from 500 to 50 versions can reclaim 90% of that library's version storage.

Recycle Bin

Items in the Recycle Bin count against site storage. Empty after confirming no recovery needed.

Check Recycle Bin size:

```powershell

$ctx = Get-PnPContext

$recycleBin = $ctx.Web.RecycleBin

$ctx.Load($recycleBin)

$ctx.ExecuteQuery()

$totalSizeMB = ($recycleBin | Measure-Object -Property Size -Sum).Sum / 1MB

Write-Output "Recycle bin: $([math]::Round($totalSizeMB, 2)) MB across $($recycleBin.Count) items"

```

Duplicate Files

Common causes: users saving the same file in multiple libraries, email attachments saved multiple times, migration artifacts. Third-party tools (ShareGate, AvePoint) detect duplicates. Microsoft Syntex can identify duplicates via document fingerprinting.

---

Setting Site Storage Quotas

SharePoint Admin Center

Active Sites → [Site] → General → Edit Storage limit → Enter quota in MB.

PowerShell Bulk Quotas

```powershell

$teamSites = Get-SPOSite | Where-Object { $_.Template -like "GROUP*" }

foreach ($site in $teamSites) {

Set-SPOSite -Identity $site.Url -StorageQuota 102400 # 100GB in MB

}

```

Storage Quota Tiering

| Site Type | Recommended Quota |

|-----------|------------------|

| Standard team site | 50-100GB |

| Large project site | 250GB |

| Document management center | 1-5TB |

| Archive site | 5-25TB |

---

Automatic Version History Management

New in 2024: Microsoft 365 Automatic version history management — intelligently reduces version storage using logarithmic decay:

  • Last 30 days: All versions retained
  • 30-180 days: Fewer versions (daily instead of per-save)
  • 180+ days: Minimal versions (weekly)

Estimated savings: 40-60% version storage reduction.

Enable: SharePoint Admin Center → Settings → Version history limits → Automatic.

---

Microsoft 365 Archive for Cold Storage

Microsoft 365 Archive (GA 2024) provides cost-optimized storage for inactive sites:

  • Cost: ~$0.05/GB/month vs. $0.20/GB/month for active storage
  • Access: Content searchable and accessible (with slight latency)
  • Reactivation: Minutes to restore to active storage

Archive scenarios:

  • Project sites after completion (archive after 90 days of inactivity)
  • Post-restructuring departmental sites
  • Acquired company content no longer actively used but compliance-required

Archive a site: SharePoint Admin Center → Active Sites → [Site] → Archive.

---

Storage Governance Policy Framework

A written storage governance policy should cover:

1. Site storage quotas: All new sites receive 50GB default. Exceptions require IT approval.

2. Version history limits:

  • New libraries: 50 major versions
  • Compliance libraries: 500 (or automatic)
  • Working files: 20 versions

3. Recycle bin management: Monthly review by site owners. No emptying for sites under active legal hold.

4. Annual storage review: Sites over 100GB reviewed for archival eligibility. Sites inactive 180+ days archived. Quarterly storage report to department heads.

5. File type restrictions: Video files >5GB → Microsoft Stream, not SharePoint. Database files (.mdb, .accdb) → not permitted.

---

Conclusion

Proactive storage management prevents the emergency that occurs when a business-critical site goes read-only. Set quotas, monitor trends, clean up version history, and establish governance before problems occur.

EPC Group provides SharePoint storage audits as part of our free SharePoint Assessment, identifying version history bloat, quota gaps, and governance risks. Contact us to schedule your assessment.

Share this article:

Written by Errin O'Connor

Founder, CEO & Chief AI Architect | Microsoft Press Bestselling Author | 25+ Years Microsoft Ecosystem

Errin O'Connor is a Microsoft Press bestselling author of 4 books covering SharePoint, Power BI, Azure, and large-scale migrations. He leads our SharePoint consulting practice with expertise spanning 500+ enterprise migrations and compliance implementations across HIPAA, SOC 2, and FedRAMP environments.

Need Expert Help?

Our SharePoint consultants are ready to help you implement these strategies in your organization.