Fix Teams Provisioning Request Is Stuck for a Newly Created Team

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 background job, or a sync delay between Teams and SharePoint. This article explains the root cause of a stuck provisioning request and gives you three working fixes, including how to re-trigger provisioning from the Teams admin center.

Why the Teams Provisioning Request Gets Stuck

When you create a team, Teams sends a background job to SharePoint Online to create the associated SharePoint team site. That site holds the Documents library, OneNote notebook, and the team’s SharePoint home page. If that job fails or times out, the team object appears in the admin center but the site never gets created. The result is a provisioning request that stays in a pending state indefinitely.

Another common cause is a temporary glitch in the Teams service itself. Microsoft runs thousands of these provisioning jobs per minute. A brief outage or a throttling event can interrupt the job before it finishes. When that happens, the system does not automatically retry in all cases, so the team stays stuck.

A third cause is a conflict with an existing SharePoint site name. If the team’s name matches a site that was recently deleted but not fully purged, SharePoint rejects the new site creation. The provisioning job then fails silently and leaves the team in a stuck state.

What Happens Behind the Scenes

The provisioning process involves three main components. First, Teams creates the team object in Microsoft 365. Second, SharePoint creates the team site. Third, Teams links the two together. If step two fails, the link never gets established. The Teams admin center still shows the team, but the team is not usable in the Teams client.

Steps to Fix a Stuck Teams Provisioning Request

Follow these steps in order. Start with the least disruptive fix and move to the more aggressive ones only if needed.

Method 1: Check Service Health and Retry

1. Open the Teams admin center
   Go to https://admin.teams.microsoft.com and sign in with an account that has the Teams Administrator role.
2. Check service health
   In the left navigation, select Health then Service health. Look for any active incident under Teams or SharePoint Online. If an incident is active, wait until it is resolved before you retry creating the team.
3. Retry the provisioning
   If no incident is active, open the Teams client and try to access the team. Sometimes the simple act of opening the team forces a retry. If the team still does not appear, proceed to Method 2.

Method 2: Delete and Recreate the Team

1. Open the Teams admin center
   Go to https://admin.teams.microsoft.com and sign in.
2. Navigate to the stuck team
   In the left navigation, select Teams then Manage teams. Find the team that has a provisioning status of Pending or Failed.
3. Delete the stuck team
   Select the team, then click Delete in the top bar. Confirm the deletion. This removes the incomplete team object from Microsoft 365.
4. Wait 30 minutes
   Wait at least 30 minutes to allow the backend to fully clean up the failed site. If you recreate the team immediately, the same name conflict may occur.
5. Recreate the team
   In the Teams client, create a new team with the same name. The provisioning should complete normally this time.

Method 3: Use PowerShell to Remove the Stuck Team

1. Install the Teams PowerShell module
   Open Windows PowerShell as an administrator and run Install-Module -Name MicrosoftTeams.
2. Connect to Teams
   Run Connect-MicrosoftTeams and sign in with your admin credentials.
3. Identify the stuck team
   Run Get-Team | Where-Object {$_.GroupId -eq "your-group-id"}. Replace your-group-id with the actual group ID from the Teams admin center. Note the GroupId value.
4. Remove the team
   Run Remove-Team -GroupId "your-group-id". Confirm the removal when prompted.
5. Recreate the team
   After the removal completes, create the team again in the Teams client.

If Teams Still Has Issues After the Main Fix

The Team Appears in Admin Center but Not in the Teams Client

This usually happens because the client has cached the old team state. Sign out of Teams and sign back in. To sign out, click your profile picture at the top right of the Teams window and select Sign out. Then sign in again. If the team still does not appear, clear the Teams cache by deleting the contents of the %appdata%\Microsoft\Teams folder. Restart Teams after clearing the cache.

The Provisioning Request Failed Because of a Name Conflict

When you delete a team, the associated SharePoint site is not removed immediately. It goes into a recycle bin for 93 days. If you recreate the team with the same name before that period ends, SharePoint may reject the new site. Use a different name for the new team, or wait until the old site is fully purged.

The Provisioning Job Has Been Stuck for More Than 24 Hours

If the request has been pending for over a day, the background job is likely dead. You cannot resume it. Delete the team and recreate it. If the problem happens again with a different team, open a support ticket with Microsoft 365 admin center and reference the GroupId of the affected team.

New Teams Admin Center vs Teams Client: Key Differences

Item	Teams Admin Center	Teams Client
Purpose	Manage all teams and policies in your tenant	Use teams for daily collaboration
Provisioning status	Shows pending or failed status for each team	Shows only teams that are fully provisioned
Delete a stuck team	Yes, from the Manage teams page	No, only the owner can delete a team, and only if it is fully provisioned
Retry provisioning	Not directly possible; you must delete and recreate	Not possible; you must use the admin center

Conclusion

Now you know why a Teams provisioning request can get stuck and how to fix it. Start by checking service health, then delete the stuck team and recreate it. Use PowerShell if the admin center does not allow you to delete the team. After recreating the team, verify that the SharePoint site is accessible. As a next step, test creating a team with a new name to confirm the issue is resolved. Remember that a name conflict with a recently deleted SharePoint site is the most common hidden cause, so always wait 30 minutes after deletion before recreating the team.