Fix Teams Expiration Policy Does Not Renew a Team after a Tenant Rename

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. This article explains the root cause and provides a step-by-step fix to restore automatic renewal.

Why Tenant Rename Breaks Teams Expiration Policy Renewal

When you rename a Microsoft 365 tenant, the system updates the primary domain and often the tenant ID in Azure AD. Teams expiration policies are tied to the tenant ID and the group lifecycle. The policy engine uses the tenant ID to locate the team and check its expiration date. After a rename, the old tenant ID may no longer match, so the policy cannot find the team to renew it.

Another factor is that the expiration policy stores the group’s expiration date based on the last renewal. If the renewal process fails silently, the team stays in a state where it appears active but is actually flagged for deletion. The owner sees a warning but the renew action does nothing because the policy cannot authenticate against the new tenant context.

This issue is not about the team itself being broken. The team still exists and functions normally. The problem is that the expiration policy’s metadata is stale. You need to refresh the policy so it points to the new tenant ID and domain.

Steps to Diagnose and Fix Teams Expiration Policy After a Tenant Rename

Before you make changes, confirm that the tenant rename actually completed. Check the Microsoft 365 admin center for the new domain and verify that all services are using the new tenant ID. Then follow these steps to fix the expiration policy.

1. Verify the tenant ID and domain
   Sign in to the Microsoft 365 admin center at admin.microsoft.com. Go to Settings > Domain names and note the new primary domain. Then go to Settings > Org settings and look for the Tenant ID. Write down both values. This gives you the correct target for the policy.
2. Connect to Microsoft Teams PowerShell
   Open Windows PowerShell as an administrator. Run Install-Module -Name MicrosoftTeams -Force if you have not installed it. Then run Connect-MicrosoftTeams and sign in with a Teams admin account. Wait for the connection to complete.
3. Check the current expiration policy
   Run Get-TeamExpirationPolicy to see the policy settings. Look for the GroupId and ExpirationDate fields. Note the teams that show an expiration date in the past or that have a RenewalStatus of Failed. This tells you which teams are affected.
4. Reapply the expiration policy
   Run Set-TeamExpirationPolicy -GroupId -ExpirationDate -RenewNow for each affected team. Replace <GroupId> with the actual team ID and <new date> with a date 30 to 90 days in the future. The RenewNow parameter forces the policy to process the renewal immediately.
5. Verify the renewal succeeded
   Run Get-TeamExpirationPolicy -GroupId again. Check that the ExpirationDate has moved to the future and the RenewalStatus shows Success. If you see Failed, check the audit log for errors.
6. Check the audit log for confirmation
   Go to the Microsoft Purview compliance portal. Navigate to Audit > Audit log search. Search for the activity Set-Group or Renew group with the team name. Confirm that the action was performed by the policy engine and not just by a manual user action.

Using the Teams Admin Center as an Alternative

If you prefer a graphical interface, you can also fix the policy in the Teams admin center. Go to Teams > Teams policies > Expiration policy. Select the policy that applies to the affected team. Edit the policy and change the Expiration duration to a different value, then change it back to the original value. This refreshes the policy and forces the engine to re-evaluate all teams under it. Save the change and wait a few minutes.

If Teams Still Does Not Renew After the Main Fix

Sometimes the policy reapplication does not solve the problem. Here are related failures and their fixes.

Teams Expiration Warning Appears but Renew Button Does Nothing

This usually happens when the team owner does not have the correct admin role. Only a Teams service administrator or a global administrator can renew a team. Ask the owner to check their role in the Azure AD admin center. If they are only a member, the renew action will fail silently. Promote the user temporarily or have an admin perform the renewal.

Expiration Policy Applies to the Wrong Teams After Rename

After a tenant rename, the policy may target teams that were created under the old domain. Use PowerShell to list all teams and their expiration status with Get-TeamExpirationPolicy -All. Then filter by the new domain. If some teams are missing, you need to assign the policy to them manually using Set-TeamExpirationPolicy.

Expiration Policy Fails with an Error About Invalid Tenant

This error means the policy still references the old tenant ID. In the Teams admin center, navigate to Org-wide settings > Tenant-wide settings. Check the Teams lifecycle section. If the tenant ID is outdated, you may need to contact Microsoft support to update the lifecycle metadata. In most cases, reapplying the policy with PowerShell resolves it.

New Teams Desktop vs Teams on the Web for Managing Expiration Policies

Item	New Teams Desktop	Teams on the Web
Admin access	Full admin center access	Full admin center access
PowerShell integration	Not available	Not available
Renew action	Visible to owners but limited	Same as desktop
Best for policy changes	Quick navigation	Works on any device

Conclusion

After a tenant rename, you can restore Teams expiration renewal by reapplying the policy with PowerShell or by editing the policy in the admin center. Always verify the tenant ID and domain first, then use Set-TeamExpirationPolicy with the RenewNow parameter to force a renewal. Check the audit log to confirm the action succeeded. For future tenant renames, document the old and new tenant IDs so you can quickly update any policies that depend on them. As a final tip, schedule a monthly review of expiration policies using Get-TeamExpirationPolicy to catch any failures early.