Fix Teams Storage Report Does Not Match SharePoint after a Microsoft 365 Group Change

When you change a Microsoft 365 group that backs a Teams team, the storage report in Teams often stops matching the SharePoint site usage. You see one number in Teams admin center and a different number in SharePoint admin center. This happens because Teams reports rely on cached group metadata that does not refresh instantly. This article explains the root cause and gives you exact steps to force a resync and make both reports agree.

After a group rename, membership change, or site policy update, the storage calculation in Teams can become stale. The fix involves clearing the cache, running a SharePoint resync, and verifying the numbers in both admin centers. You will also learn how to avoid this issue in the future.

Why Teams Storage Report Differs from SharePoint After a Group Change

Teams stores its files in the connected SharePoint site of the Microsoft 365 group. The storage report in Teams admin center reads from a metadata cache that holds the group’s site ID, quota, and usage. When you change the group — such as renaming it, adding a member, or changing the site’s storage limit — SharePoint updates its own database immediately. Teams, however, polls this information on a schedule, often every 24 hours. Until the next poll, the Teams report shows the old value.

Another factor is the “Storage used” metric itself. SharePoint calculates usage from all files, including versions, recycle bin items, and metadata. Teams calculates the same metric but may exclude certain recycle bin contents or temporary files. This difference becomes visible after a group change because the underlying site structure changes, and the two services compute usage at different times.

Group Change Types That Cause a Mismatch

A rename of the group does not change the site URL, but it updates the display name in Teams. This alone can trigger a metadata refresh delay. More significant are changes to the site’s storage quota, such as when an admin raises or lowers the limit. The Teams report still shows the old quota until the cache updates. Membership changes also affect the “storage used” number because new members may have added files or the system recalculates permissions.

Steps to Reconcile the Teams Storage Report with SharePoint

Follow these steps in order. Do not skip the cache clearing step because it forces Teams to read fresh data from SharePoint.

1. Clear the Teams desktop cache
   Close Teams completely. Press Ctrl+Shift+Esc to open Task Manager and end any Teams process. Then open File Explorer and paste %appdata%\Microsoft\Teams into the address bar. Delete all files in this folder, but keep the folder itself. This forces Teams to rebuild its local cache on next launch.
2. Sign out and sign back in
   Open Teams and sign out from your profile. Wait 30 seconds, then sign in again. This refreshes the group metadata from the Microsoft 365 directory.
3. Run a SharePoint resync using PowerShell
   Install the SharePoint Online Management Shell if you have not already. Run Connect-SPOService -Url https://yourtenant-admin.sharepoint.com and authenticate. Then run Set-SPOSite -Identity https://yourtenant.sharepoint.com/sites/yourteam -StorageManagementEnabled $true. This command forces SharePoint to recalculate storage and push the new value to the group.
4. Verify in SharePoint admin center
   Go to SharePoint admin center > Active sites. Find your team’s site and check the “Storage used” column. Note this number. It is the authoritative value.
5. Verify in Teams admin center
   Go to Teams admin center > Teams > Manage teams. Select your team and open the Storage tab. Compare the number with the SharePoint value. If they match, the fix is complete.
6. Wait for the next sync cycle if numbers still differ
   If the numbers still differ, wait up to 24 hours. Teams syncs group storage once per day. You can also check the Microsoft 365 admin center > Reports > Usage to see the same data.

If Teams Still Shows a Different Storage Number

Teams Shows a Higher Storage Number Than SharePoint

This usually means the recycle bin is included in the Teams calculation. SharePoint excludes recycle bin items from the site usage report by default. To match, empty the recycle bin. Go to your team’s SharePoint site, select Recycle bin in the left navigation, and click Empty recycle bin. After that, rerun the PowerShell resync from the steps above.

Teams Shows a Lower Storage Number Than SharePoint

This happens when the Teams cache has not yet picked up new files added after the group change. Wait for the next sync cycle, or force a refresh by clearing the cache again. If the problem persists, check if the site has a storage quota that is lower than the actual usage. In that case, raise the quota in SharePoint admin center, then resync.

The Storage Tab in Teams Admin Center Is Missing

The Storage tab only appears for teams that have a connected SharePoint site. If you changed the group to a different site, the tab may disappear. Reconnect the site by going to the team’s Settings > Site URL and updating it. Then run the PowerShell resync to update the group metadata.

Teams Desktop vs Teams Admin Center Storage Reports: Key Differences

Item	Teams Desktop	Teams Admin Center
Data source	Local cache from the last sync	Metadata from the Microsoft 365 group
Refresh frequency	On app launch and every few hours	Once every 24 hours
Includes recycle bin	Sometimes yes	No, by default
Best for	Quick personal check	Official reporting for admins

The desktop app shows a cached value that can be stale immediately after a group change. The admin center is more reliable but still lags behind SharePoint. For the most accurate number, always use SharePoint admin center.

Final Steps to Keep the Reports in Sync

You can now force the Teams storage report to match SharePoint after a group change. Clear the Teams cache, run the PowerShell resync, and verify in both admin centers. To prevent future mismatches, set a weekly reminder to review storage in SharePoint admin center. Use the Set-SPOSite command after any major group change to avoid waiting for the daily sync.