You use the Teams admin center guest review policy to automatically remove inactive guests from your tenant. After renaming your Microsoft 365 tenant, the guest review process stops working and inactive guests remain in your directory. This happens because the guest review policy stores the old tenant name in its configuration, and the cleanup job … Read more
When you create a new team in Microsoft Teams and run the guest review process, inactive guests may remain in the team instead of being removed. This happens because the guest review policy relies on the guest’s last activity date, which is not always populated for a newly created team. This article explains why the … Read more
When you open the storage report for a department team in Teams, the numbers often do not match what SharePoint shows for the same team. This mismatch happens because Teams and SharePoint count storage differently, and some files live outside the team’s default document library. You will learn the exact reasons for the discrepancy and … Read more
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. … Read more
When you run a storage report for Teams in a multi-geo tenant, the numbers often do not match what SharePoint reports. This mismatch occurs because Teams stores files in SharePoint sites that are spread across different geographic locations. The Teams admin center shows aggregate storage, while SharePoint reports per-site detail. This article explains the root … Read more
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 … Read more
When you create a new team in Microsoft Teams, the storage report in the Teams admin center can show a different number than what SharePoint reports for the connected site. This mismatch confuses admins who expect the numbers to be identical. The difference happens because Teams counts the entire site collection, including system data and … Read more
When you run a Teams lifecycle workflow to archive or delete a department team, the workflow fails because it cannot assign an owner. This error usually happens when the team has no active owner or when the workflow’s owner selection rule conflicts with the team’s membership. The root cause is often a missing or inactive … Read more
When you apply a Teams template to a department team, the expected channels may not appear. Instead, you see default channels like General, or channels from an older template version. This mismatch wastes time and forces manual channel creation for every new team. The root cause is usually a stale template definition, a cached template … Read more
Your Teams template may create the wrong channels after you change the Microsoft 365 group that backs a team. This happens when the template definition still points to the old group structure. In this article, you will learn why the mismatch occurs and how to fix it using the Teams admin center and PowerShell. The … Read more