Fix Teams Provisioning Request Is Stuck after a Microsoft 365 Group Change

When you change a Microsoft 365 group that backs a Teams team, the provisioning request can get stuck. This usually happens after you rename the group, change its privacy, or modify its membership. The Teams admin center shows a pending provisioning request that never completes. This article explains why the request stalls and gives you step-by-step fixes to clear it.

The root cause is a mismatch between the group object in Microsoft Entra ID and the team object in Teams. When the group changes, Teams tries to sync the team’s settings. If the sync fails, the provisioning request remains in a pending state. You will learn how to identify the stuck request, force a re-sync, and verify that the team is healthy again.

Why Teams Provisioning Gets Stuck After a Group Change

In Teams, every team is backed by a Microsoft 365 group. The group holds the membership, email, and SharePoint site. The team holds the channels, tabs, and settings. When you change the group, Teams must update the team to match. This process is called provisioning.

The sync is triggered by an event in Microsoft Entra ID. If the event is not delivered or processed correctly, the provisioning request stays in a pending state. Common triggers include renaming the group, changing the group’s privacy from private to public, or adding a large number of members at once. The request can also stall if the group has been deleted and recreated with the same name.

The Role of the Group in Teams Provisioning

The Microsoft 365 group is the source of truth for identity. Teams reads the group’s display name, description, and membership to build the team. When you change the group, Teams receives a notification. It then queues a provisioning request to apply the changes. If the notification is lost or the queue is blocked, the request remains pending.

Why the Request Does Not Complete Automatically

The sync fails silently in most cases. The Teams admin center shows the pending state, but there is no error message. The failure can be caused by a temporary network issue, a misconfigured group policy, or a conflict with an existing team that has the same name. The system does not retry automatically, so you must intervene manually.

Steps to Diagnose and Clear the Stuck Provisioning Request

Follow these steps in order. Each step checks a different part of the system. Stop when the provisioning request shows as completed.

Step 1: Identify the Team with the Stuck Request

1. Open the Teams admin center
   Go to Teams admin center > Teams > Manage teams. Sign in with an account that has the Teams Administrator role.
2. Find the team
   Use the search box to enter the team name or the group ID. Look for the team that shows a provisioning state of Pending or Failed.
3. Note the group ID
   Click the team name to open the details pane. Copy the Group ID from the General tab. You will need it later.

Step 2: Check the Group in Microsoft Entra ID

1. Open Microsoft Entra admin center
   Go to Microsoft Entra admin center > Groups > All groups. Sign in with the same admin account.
2. Locate the group
   Search for the group ID you copied. Open the group and check the Provisioning tab. If the status is Failed, click Retry provisioning.
3. Wait for the retry
   Wait 5 minutes. Then go back to the Teams admin center and refresh the team list. If the request is still pending, continue to the next step.

Step 3: Force a Re-sync with PowerShell

Use the Teams PowerShell module to force a new provisioning event. This updates a team property, which triggers a fresh sync.

1. Install the Teams PowerShell module
   Open Windows PowerShell as an administrator. Run Install-Module -Name MicrosoftTeams -Force -AllowClobber. If you already have it, skip this step.
2. Connect to Teams
   Run Connect-MicrosoftTeams and sign in with your admin account.
3. Update a team property
   Run the following command, replacing the group ID with the one you copied:
   Set-Team -GroupId "your-group-id" -DisplayName "Temporary Name"
   This changes the display name, which triggers a new provisioning request.
4. Revert the display name
   After the sync completes, run the same command with the original display name. Wait 10 minutes.

Step 4: Verify the Provisioning Status

1. Refresh the Teams admin center
   Go back to Teams admin center > Teams > Manage teams. Refresh the page.
2. Check the status
   Confirm that the team now shows Provisioned. If it still shows Pending, wait 30 minutes and check again.
3. Test the team
   Open the team in the Teams desktop app. Verify that you can see all channels and that members appear correctly.

If Teams Still Has Issues After the Main Fix

Sometimes the provisioning request clears, but the team still shows problems. Here are the most common related failures and how to fix them.

Teams Shows a Blank Window After the Group Change

This happens when the team’s SharePoint site is not fully synced with the group. Open the SharePoint site associated with the group. Go to Site settings > Site information and click Save without changing anything. Then refresh Teams.

Members Cannot Access the Team After a Privacy Change

If you changed the group from private to public, external users might need to be re-added. Go to Teams admin center > Users > Manage users and check the guest accounts. Remove and re-add any guest that is missing.

Provisioning Request Fails with a Name Conflict

If you renamed the group to a name that already exists, the provisioning fails. Rename the group to a unique name in Microsoft Entra ID. Then run the PowerShell command from Step 3 again.

Teams Admin Center vs PowerShell for Provisioning Fixes

Item	Teams Admin Center	PowerShell
Access	Web browser, no install	Requires Windows PowerShell and module
Visibility	Shows provisioning status directly	Shows detailed properties and errors
Actions	Retry provisioning button	Set-Team to force re-sync
Speed	Slower, manual refresh	Faster, scriptable
Best for	Quick checks and one-off fixes	Bulk changes and automation

Use the admin center for a single team. Use PowerShell when you have multiple teams with stuck requests.

After following these steps, you can clear a stuck provisioning request and get your team back to normal. Check the provisioning status in the Teams admin center after each change. For recurring issues, review your group change process and avoid making multiple changes at once. Use the PowerShell re-sync method as your primary tool, and keep the admin center open for verification.