Fix Teams Provisioning Request Is Stuck after a Tenant Rename

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 rename breaks provisioning and provides step-by-step fixes to clear the stuck request and restore full functionality.

The root cause is that a tenant rename updates the Azure AD domain but does not automatically update the Teams service’s internal references. Teams provisioning relies on the initial tenant ID and domain name, and a mismatch leaves the request in a queued state. You will learn how to verify the issue, force a re-provisioning, and apply a PowerShell workaround when the UI fails.

Why a Tenant Rename Leaves Teams Provisioning Stuck

When you rename a tenant in Microsoft 365, you change the initial domain name that was set when the tenant was created. For example, if your tenant was originally contoso.onmicrosoft.com and you rename it to fabrikam.onmicrosoft.com, Azure AD updates the directory. However, Teams provisioning is a background service that creates and configures the Teams environment for the tenant. This service caches the original tenant domain and ID. After a rename, the cached value no longer matches the current Azure AD state, so the provisioning request remains in a “pending” or “in progress” status indefinitely.

The Teams provisioning pipeline is separate from Azure AD. It reads the tenant’s domain from the initial setup. A rename does not trigger an automatic refresh in Teams. The system expects the tenant to remain stable. When a mismatch occurs, the provisioning engine cannot complete the final steps, such as creating the default team or enabling the Teams service for users. This is why the admin center shows a stuck request.

What Exactly Gets Stuck

The stuck request is not a single item. It is the entire provisioning job that includes creating the Teams service principal, setting up the tenant’s Teams policy, and enabling the service for all users. The job gets queued but never completes because the domain validation fails. In some cases, the job appears as “Provisioning” for weeks. Users might see a sign-in error that says “Your account is not enabled for Teams.”

Steps to Diagnose and Fix Teams Provisioning After a Tenant Rename

Follow these steps in order. The first two steps are diagnostic. The remaining steps apply the fix. You need Global Admin or Teams Admin permissions.

1. Verify the tenant rename in Microsoft 365 admin center
   Sign in to admin.microsoft.com. Go to Settings > Domains. Confirm that the new domain, such as fabrikam.onmicrosoft.com, is listed as Default. Also check that the old domain, contoso.onmicrosoft.com, is either removed or marked as non-default. If the old domain is still present, remove it or set the new one as default.
2. Check the Teams provisioning status
   Open the Teams admin center at admin.teams.microsoft.com. Go to Org-wide settings > Teams settings. Look for the provisioning status. If it shows “In progress” or “Pending” and has not changed in more than 24 hours, the request is stuck. Note the exact status text.
3. Force a re-provisioning with PowerShell
   Install the Teams PowerShell module if you have not done so. Run the following commands in an elevated PowerShell window:
   Install-Module MicrosoftTeams -Force
Connect-MicrosoftTeams
   Sign in with your admin account. Then run:
   Set-CsTenantFederationConfiguration -Identity global
   This command forces Teams to re-read the tenant configuration. Wait for the command to complete. This often clears the stuck provisioning job.
4. Restart the Teams provisioning service
   If the previous step does not work, you need to restart the provisioning service. Use the following PowerShell commands:
   Get-CsTenant
Set-CsTenant -Identity "yourtenant.onmicrosoft.com" -Force
   Replace yourtenant.onmicrosoft.com with your current tenant domain. This resets the tenant’s provisioning state. Wait 10 minutes, then check the Teams admin center again.
5. Clear the stuck request using the Teams admin center
   In the Teams admin center, go to Users > Manage users. Select all users. Click Edit settings. Change the Teams license setting to Off and then back to On. This triggers a per-user re-provisioning. Save the changes. Wait for the status to update.
6. Contact Microsoft Support if the request remains stuck
   If after 48 hours the status has not changed, open a support ticket with Microsoft. Mention that the tenant was renamed and that the provisioning request is stuck. Provide the tenant ID and the old and new domain names. Microsoft can manually reset the provisioning pipeline.

If Teams Still Shows a Stuck Provisioning After the Fix

Teams Users Cannot Sign In After the Rename

If users see a sign-in error, the issue might be a cached credential on the client. Ask users to sign out of Teams completely. Then clear the Teams cache by deleting the %appdata%\Microsoft\Teams folder. On Windows, press Ctrl+Shift+Esc to open Task Manager, end all Teams processes, then delete the folder. Restart Teams and sign in again.

Teams Admin Center Shows a Different Tenant Name

Sometimes the admin center still shows the old domain in the URL or in the header. This is a display issue. Clear your browser cache and cookies. Use an InPrivate window in Microsoft Edge or a Private window in Google Chrome. Sign in again. The correct tenant name should appear.

Provisioning Request Reappears After a Few Days

If the stuck request returns, the tenant rename might not have been fully completed. Go back to Microsoft 365 admin center > Settings > Domains. Ensure that the old domain is removed from the list entirely. If the old domain is still present, remove it. Then rerun the PowerShell command from step 3.

Teams Provisioning Fix Methods Compared

Item	PowerShell Set-CsTenantFederationConfiguration	Teams Admin Center License Toggle
Effort	Requires PowerShell module and admin credentials	UI-based, no extra tools
Time to apply	5 minutes	10 minutes
Effectiveness	High, resets the entire provisioning pipeline	Medium, works for per-user issues
Risk	Low, but requires careful execution	None, safe to perform
Best for	Tenant-wide stuck provisioning	Individual users with sign-in errors

You now have the tools to clear a stuck Teams provisioning request after a tenant rename. Start with the PowerShell method because it addresses the root cause. If that fails, use the license toggle in the admin center. Always verify the domain list in the Microsoft 365 admin center as the first step. For persistent issues, contact Microsoft Support with the tenant ID and domain names. Remember to clear client caches on user devices to avoid sign-in errors.