After renaming your Microsoft 365 tenant, Teams might show a provisioning request stuck in a pending state. This typically happens because Teams still references the old tenant name in its provisioning pipeline. The result is that users cannot sign in, or the Teams admin center displays a perpetual provisioning status. This article explains why the … Read more
When you create a new team in Microsoft Teams, the provisioning process usually completes in seconds. Sometimes the request gets stuck and the team never appears in your team list. This leaves members unable to access shared files, channels, or the team site. The problem often stems from a failed service health event, a corrupted … Read more
When you set a Teams retention or archive policy for a department team, you expect the policy to run automatically. But sometimes the policy never triggers, and the team stays active with all its data. This usually happens because the policy assignment is incorrect, the team is excluded by a broader policy, or the archive … Read more
When you change a Microsoft 365 group, the Teams archive policy may stop running. You expect old teams to move to Archive automatically, but they stay active. This usually happens because the policy assignment is tied to the group’s old identity or because the change did not trigger a policy evaluation. This article explains why … Read more
When your organization uses a multi-geo Microsoft 365 tenant, the Teams archive policy may not run as expected. Users see chats and channels that never move to archived state, or the policy appears to have no effect. This happens because the archive policy is tied to the user’s preferred data location, and in a multi-geo … Read more
After renaming your Microsoft 365 tenant, the Teams archive policy may stop running. This usually happens because the policy still references the old tenant domain. The archive policy fails silently, and users never see their chat history moved to the archive mailbox. This article explains why the rename breaks the policy and gives you exact … Read more
When you create a new team in Microsoft Teams, the archive policy you set in the Teams admin center may not apply automatically. This leaves the team active past its intended expiration date, which can clutter your tenant and create compliance risks. The root cause is that archive policies are evaluated only when a team … Read more
After you rename your Microsoft 365 tenant, you may notice that Teams expiration policies stop renewing teams automatically. The team owner receives an expiration warning, but clicking renew fails or the policy simply does not apply. This happens because the expiration policy stores the tenant ID and domain, and a rename can break that link. … Read more
If you created a new team and set its expiration policy, the expiration date may not renew as expected. This usually happens when the policy assignment is missing or the renewal process fails silently. The expiration policy in Teams relies on Microsoft 365 group lifecycle rules. This article explains why a newly created team ignores … Read more
Your ownerless team report in Teams shows only some of the department teams that actually have no owner. The missing entries make it hard to assign new owners and keep governance accurate. This happens because the report only scans teams where the requester has access, or because the global admin report uses a cached data … Read more