Fix Teams Storage Report Does Not Match SharePoint after a Tenant Rename

After renaming your Microsoft 365 tenant, the storage report in Teams may not match the numbers shown in SharePoint. This happens because Teams and SharePoint use different identifiers after the rename. This article explains why the mismatch occurs and provides clear steps to verify and fix the storage numbers.

The root cause is that a tenant rename changes the SharePoint domain URL but not the underlying site collection IDs. Teams storage reports rely on the site collection ID, while SharePoint reports use the new domain. Until the cache refreshes, the numbers appear inconsistent.

You will learn how to force a refresh of the storage data, verify the correct site collection IDs, and reconcile the numbers across both admin centers.

Why the Teams Storage Report Differs from SharePoint After a Tenant Rename

When you rename a tenant, Microsoft 365 changes the SharePoint domain from the old name to the new name. For example, contoso.onmicrosoft.com becomes newcontoso.onmicrosoft.com. However, the underlying site collection IDs remain unchanged. Teams storage reports are built on the site collection ID, while SharePoint reports use the domain URL. Because the domain changes but the ID does not, the two reports can show different totals.

Another factor is caching. Both Teams and SharePoint admin centers cache storage data for performance. After a tenant rename, the cache may still contain old domain references. This can cause the Teams report to show a lower or higher number than SharePoint until the cache expires.

A third factor is the storage quota calculation. SharePoint calculates storage per site collection, while Teams aggregates storage for all channels and files within a team. If a team has multiple channels, the storage may be spread across several site collections. The Teams report should sum these, but a rename can disrupt that aggregation.

Finally, the tenant rename process itself might take time to propagate across all services. Microsoft recommends waiting up to 48 hours for full synchronization. During this period, the reports will naturally show inconsistencies.

Steps to Verify and Fix the Storage Report Mismatch

Follow these steps in order. Each step helps you identify whether the mismatch is due to a cache issue, a site collection ID problem, or a quota calculation error.

1. Check the current SharePoint domain
   Go to Microsoft 365 admin center > Settings > Org settings > Organization profile. Look for the SharePoint domain. It should show the new domain after the rename. If it still shows the old domain, the rename may not have completed.
2. Compare site collection IDs
   In the SharePoint admin center > Active sites, note the site collection ID for each team site. In Teams, open the Teams admin center > Teams apps > Manage apps > Storage. The storage report lists the site collection ID for each team. Compare the IDs. If they match, the data source is the same. If they do not match, the report is pulling from a different site collection.
3. Force a refresh of the Teams storage report
   In the Teams admin center, navigate to Teams apps > Manage apps > Storage. Click the Refresh icon at the top of the page. This forces a manual refresh of the storage data. Wait 10 minutes and check the numbers again.
4. Clear the SharePoint cache
   In the SharePoint admin center, go to Settings > General > Cache settings. Click Clear cache. This removes any cached data that may reference the old domain. Wait 30 minutes and recheck the storage numbers in both admin centers.
5. Verify the storage quota per site collection
   In the SharePoint admin center > Active sites, select a team site and click Edit. Note the storage quota and the used storage. Compare this with the Teams storage report for the same site collection ID. If the numbers differ, the quota may be set incorrectly.
6. Run a usage report in Microsoft 365 admin center
   Go to Microsoft 365 admin center > Reports > Usage > SharePoint. This report shows the total storage used across all site collections. Compare this with the sum of the Teams storage report. If the totals differ by more than 5 percent, there may be orphaned site collections.
7. Wait for the 48-hour synchronization window
   If the numbers still do not match after completing the above steps, wait 48 hours from the time of the tenant rename. Microsoft may take up to 48 hours to fully propagate the change across all services. After 48 hours, repeat steps 3 and 4.

If Teams Storage Still Does Not Match SharePoint

Teams Shows Zero Storage for a Team That Has Files

This usually happens when the site collection ID for the team was changed during the rename. The Teams report cannot find the site collection, so it shows zero. To fix this, go to the SharePoint admin center and verify that the site collection exists. If it does, check the site collection ID in the Teams admin center. If the ID is different, you may need to manually update the team’s site collection association. Contact Microsoft support if this occurs.

SharePoint Shows More Storage Than Teams

This can happen when there are orphaned site collections that are not associated with any team. These site collections still consume storage but are not counted in the Teams report. To find orphaned site collections, go to the SharePoint admin center > Active sites. Look for sites that are not listed in the Teams admin center. Delete or archive these sites to free up storage. After deletion, the numbers should align.

Teams Shows More Storage Than SharePoint

This is rare but can happen if a team has multiple channels that map to different site collections. The SharePoint report may only show the root site collection, while the Teams report sums all channel site collections. To verify, check the site collection IDs in the Teams storage report. If there are multiple IDs for one team, the SharePoint report may be missing some. You may need to check each channel’s storage separately in the SharePoint admin center.

Teams Storage Report vs SharePoint Storage Report: Key Differences

Item	Teams Storage Report	SharePoint Storage Report
Data source	Site collection ID	Domain URL
Update frequency	Every 24 hours	Real-time
Scope	Per team	Per site collection
After tenant rename	May show old IDs until cache refresh	Shows new domain immediately

After completing the steps above, you can now verify and fix the storage report mismatch between Teams and SharePoint. The key is to compare site collection IDs and force a cache refresh. If the numbers still differ after 48 hours, check for orphaned site collections or multiple channel site collections.

Next, try the Microsoft 365 admin center > Reports > Usage > SharePoint to get a global view of storage. For advanced troubleshooting, use the SharePoint Online Management Shell to list all site collections and their storage usage. This command-line tool gives you precise data that can help you identify discrepancies quickly.