Storage Quota Warning Appears on the Wrong Site: Fix

You see a storage quota warning in the SharePoint admin center, but it points to a site that is not using excessive storage. The warning message shows a different site URL than the one actually consuming space. This problem occurs because SharePoint calculates storage across site collections linked to the same content database or because of a stale cached metric. This article explains why the wrong site appears and provides the exact steps to identify the real storage consumer and clear the false warning.

Why the Storage Quota Warning Points to the Wrong Site

SharePoint Online storage quotas are enforced at the tenant level, but warnings in the admin center are generated per site collection. The system calculates storage usage for each site individually. However, two factors cause the warning to appear on the wrong site.

Shared Content Database in SharePoint On-Premises

If you are using SharePoint Server on-premises, multiple site collections can reside in the same content database. When one site collection exceeds its quota, the warning may appear on a different site collection within the same database. This happens because the database-level storage check triggers the alert for all associated sites, even if only one site is over the limit.

Stale Cache in SharePoint Online

In SharePoint Online, the admin center caches storage metrics for performance reasons. This cache can become outdated. If a site recently deleted large files or emptied its recycle bin, the cached value may still show high usage. The warning then appears on the site that previously held the data, not the site currently consuming space.

Recycle Bin and Version History Overlap

SharePoint counts files in the site recycle bin and the second-stage recycle bin toward the site quota. Version history for documents also counts. If you move files from one site to another, the original site may still show high usage until the recycle bins are emptied. The warning then incorrectly points to the source site instead of the destination.

Steps to Identify the Real Storage Consumer

Follow these steps to find which site is actually consuming the storage and clear the false warning.

1. Run the SharePoint Online Management Shell
   Open Windows PowerShell as an administrator. Run the command Connect-SPOService -Url https://[tenant]-admin.sharepoint.com and sign in with a global admin or SharePoint admin account. Then run Get-SPOSite -Limit ALL | Select-Object Url, StorageUsageCurrent, StorageQuota. This returns live storage usage for every site. Compare the values with what the admin center shows. The site with the highest StorageUsageCurrent value is the real consumer.
2. Check the Site-Level Storage Metrics
   Navigate to the site that shows high usage in PowerShell. Go to Site settings > Storage metrics. This page lists every document library, list, and recycle bin with their exact sizes. Look for libraries with many versions or large recycle bins. Empty the recycle bins if needed.
3. Clear the Admin Center Cache
   In the SharePoint admin center, go to Active sites. Select the site showing the false warning. Click Storage and then Refresh. This forces the admin center to recalculate the storage for that site. Wait 15 minutes and check the warning again. If it disappears, the cache was stale.
4. Verify Content Database in On-Premises
   If you use SharePoint Server, open Central Administration. Go to Application Management > Manage content databases. Select the database that contains the site with the warning. Check the number of site collections in that database. If multiple sites share the database, run Get-SPSite -ContentDatabase [DBName] | Select-Object Url, Quota in the SharePoint Management Shell. Identify the site that exceeds its quota. Adjust the quota for that site or move it to a different database.
5. Use Microsoft 365 Usage Reports
   Go to the Microsoft 365 admin center > Reports > Usage > SharePoint activity. Filter by date range and look for sites with the highest storage consumption. This report uses live data and can confirm which site is the true source of the warning.

If the Warning Still Appears on the Wrong Site

Warning Persists After Refresh

If the warning remains after clearing the cache, the site may have a hidden file or a large recycle bin that is not visible in the standard storage metrics. Run Get-SPOSite -Identity [SiteURL] -Detailed | Select-Object StorageUsageCurrent in PowerShell. Compare this value with the sum of all libraries shown in the site-level metrics. A discrepancy indicates hidden content. Use Get-PnPRecycleBinItem -RowLimit 5000 in PnP PowerShell to list all items in both recycle bins. Empty both bins with Clear-PnPRecycleBinItem -All.

Warning Shows on a Site That Was Deleted

If the warning references a site that no longer exists, the site may still be in the SharePoint admin center recycle bin. Go to the SharePoint admin center > Deleted sites. If the site is there, permanently delete it. If it is not listed, run Remove-SPOSite -Identity [SiteURL] -Confirm:$false in PowerShell to remove any orphaned references. Wait 24 hours for the warning to clear.

Warning Appears on a Communication Site with No Files

Communication sites often have no document libraries, yet they can still show storage usage from system pages and metadata. Check the Site assets library and the Style library. These hidden libraries may contain images or scripts that count toward the quota. Delete unnecessary files from these libraries. If the site is unused, consider deleting it to free the quota.

Item	SharePoint Admin Center	PowerShell Get-SPOSite
Data freshness	May be cached up to 24 hours old	Live data from the service
Recycle bin inclusion	Includes recycle bin sizes	Includes recycle bin sizes
Version history inclusion	Includes version history	Includes version history
Per-library breakdown	Not available	Not available
Best use case	Quick overview of all sites	Accurate troubleshooting

Use the admin center for a general view. Use PowerShell when you need precise, current storage numbers to identify the real source of a quota warning.

You can now identify which site is actually consuming storage and clear the false warning. Start by running the PowerShell command to get live usage data, then empty recycle bins and refresh the admin center cache. For on-premises environments, check the content database for multiple site collections and adjust quotas accordingly. An advanced tip: schedule a weekly PowerShell script that exports storage usage for all sites and sends an email alert when any site exceeds 80 percent of its quota. This prevents false warnings before they appear.