If you manage Teams and rely on the Ownerless Team report in the Teams admin center, you may notice it stops listing certain teams after you change the Microsoft 365 group that backs a team. The report only shows teams that have no owners, but a change to the group owner or membership can leave … Read more
If you run the ownerless team report in the Teams admin center and the results look incomplete for a multi-geo tenant, you are not alone. The report often misses teams that live in satellite data locations. This happens because the report only queries the primary geography by default. This article explains why the report is … Read more
Your Teams admin center Ownerless Team report shows fewer teams than expected after you renamed your Microsoft 365 tenant. The report misses teams that still have an owner in the directory, even though the owner account appears inactive or unlicensed. This happens because the report filters on the tenant name stored in each team’s metadata, … Read more
When you create a new team in Microsoft Teams, the Ownerless Team report in the Teams admin center may show incomplete data or miss the team entirely. This happens because the report only refreshes on a fixed schedule and may not yet include teams created within the last few hours. This article explains why the … Read more
When you create a new department team in Microsoft Teams, the provisioning request can sometimes get stuck in a pending state. The team never appears in the Teams client, or it appears but shows a message that provisioning is still in progress. This typically happens because of a delay in the backend provisioning service, a … Read more
When you create a new team for a department, the naming policy you set in the Teams admin center may not apply. The team gets a generic name like “Marketing” instead of “MKT-Marketing-2024”. This happens because the naming policy only applies to teams created by users through the Teams client, not to teams created by … Read more
You changed a Microsoft 365 group name or renamed a team, but Teams still shows the old name or ignores your naming policy. This happens because Teams caches group metadata and only applies naming policies at specific triggers. This article explains why the policy stops applying and gives you a step-by-step fix to force Teams … Read more
If your organization runs Microsoft 365 in a multi-geo configuration, you may find that the Teams naming policy fails to apply to certain users. The policy appears configured in the Teams admin center, yet new teams or renamed teams do not follow the required prefix or suffix. This article explains why the naming policy can … Read more
After renaming your Microsoft 365 tenant, Teams may stop enforcing the naming policy for new teams and channels. This happens because the naming policy references the old tenant ID or domain in its blocked words list and prefixes. You will see new teams created with default names instead of your custom prefix and suffix. This … Read more
When you create a new team in Microsoft Teams, the naming policy you set in the Teams admin center may not apply. The team gets a default name or an old name, and you see no error. This happens because the policy is cached or because the policy assignment is missing for your user. This … Read more