Fix Cannot Create a Team after a Tenant Migration

After a Microsoft 365 tenant-to-tenant migration, users often report that the New Team button in Teams is grayed out or that creating a team fails with a generic error. This problem usually stems from stale Azure AD objects, missing licenses, or mismatched group settings that survive the migration. In this article, I explain the root causes and provide a step-by-step fix that restores team creation for your users. You will also learn how to prevent the same issue from recurring after future migrations.

Why Team Creation Fails After a Tenant Migration

When you migrate a tenant, you typically copy users, groups, and mailboxes from the source to the target. However, the migration process does not always replicate the exact Azure AD configuration that Teams relies on. Teams creates a team by provisioning a Microsoft 365 group. If that group already exists in the target tenant but lacks the proper GroupType or Visibility attributes, the New Team button stays disabled.

Another common cause is a missing service plan. Teams requires a Teams license, but migration tools sometimes assign only the Exchange Online or SharePoint Online plan. Without the Teams service plan, the client blocks creation. Finally, group creation settings in Azure AD can be set to No for certain security groups, which prevents users from creating any team until an admin changes the policy.

Understanding the Role of Microsoft 365 Groups in Teams

Every team is backed by a Microsoft 365 group. The group holds the membership, the SharePoint site, and the shared mailbox. When you create a team, Teams sends a request to Azure AD to create a new group. If the group creation request is rejected, the entire operation fails. After a migration, the group may exist but be marked as a security group, or it may have a Classification that is no longer valid in the target tenant.

Steps to Diagnose and Fix Team Creation After Migration

Follow these steps in order. Each step targets a specific root cause. Stop when the New Team button works again.

1. Check the user’s Teams license in the target tenant
   Open the Microsoft 365 admin center at admin.microsoft.com. Go to Users > Active users, select the affected user, and open the Licenses and apps tab. Confirm that Microsoft Teams is toggled on. If it is off, enable it and wait 30 minutes for the license to propagate. If the license is missing entirely, assign a plan that includes Teams, such as Microsoft 365 Business Standard.
2. Verify that the migrated group is a Microsoft 365 group
   Go to the Azure AD admin center at entra.microsoft.com. Navigate to Groups > All groups and locate the group that should back the new team. Open the group and check the Type field. It must say Microsoft 365. If it says Security, the migration created the wrong group type. Delete the security group and recreate it as a Microsoft 365 group, or use PowerShell to convert it as shown in step 4.
3. Check the group creation settings in Azure AD
   In Azure AD, go to Groups > Group settings. Under General, confirm that the setting Users can create Microsoft 365 groups in Azure portals is set to Yes. If this is set to No, users cannot create any team. Change it to Yes and save. This setting affects all users, so apply it with care.
4. Update the group attributes with PowerShell
   If the group type is correct but creation still fails, use the Microsoft Graph PowerShell SDK to update the group. Install the SDK if needed, then run the following commands. Connect with an admin account, set the group’s visibility to Public or Private, and ensure the groupType attribute includes the Unified value. Replace the placeholder with your group ID. The command Set-MgGroup -GroupId “group-id” -Visibility “Public” -GroupTypes @(“Unified”) forces the group to act as a Microsoft 365 group. After running the command, wait 5 minutes and test team creation again.
5. Clear the Teams client cache
   If the backend is fixed but the client still shows the error, clear the Teams cache. Close Teams completely. In Windows, press Ctrl+R to open the Run dialog, type %appdata%\Microsoft\Teams, and press Enter. Delete the contents of the Cache, Code Cache, and GPUCache folders. Restart Teams and sign in again.
6. Test with a fresh user account
   Create a test user in the target tenant and assign a Teams license. Ask that user to create a team. If the test user succeeds, the problem is specific to the migrated user’s profile. In that case, delete the migrated user’s Teams data in the target tenant and let Teams re-provision it on the next sign-in.

If Team Creation Still Fails After the Main Fix

The steps above resolve most migration-related issues. But some environments have deeper problems. Here are related failure patterns and their fixes.

Teams Shows “You can’t create a team because your organization has reached the maximum number of teams”

This error appears when the target tenant has a group creation limit set by an Azure AD policy. The limit is usually 500,000 groups. Check the Azure AD group settings and raise the limit if needed. Alternatively, ask an admin to delete obsolete groups to free up space.

The New Team button is grayed out for one user only

A single user with this symptom often has a corrupted Teams cache or a missing license assignment. Re-run the license check from step 1. If the license is correct, clear the cache as described in step 5. If the problem persists, sign the user out of Teams and sign back in.

Team creation works in the web client but not in the desktop app

This indicates a desktop app issue, not a tenant problem. Update the Teams desktop app to the latest version. If the app is already current, repair the installation through Windows Settings > Apps > Teams > Advanced options > Repair. This resets the app without deleting your data.

New Teams Desktop vs Teams on the Web After Migration

Item	New Teams Desktop	Teams on the Web
Cache location	%appdata%\Microsoft\Teams	Browser cookies and site data
License check	Reads from the signed-in user profile	Reads from the same user profile
Group creation behavior	Uses the same Azure AD backend	Uses the same Azure AD backend
Error messages	Detailed with error codes	Often generic
Best for troubleshooting	Preferred for cache fixes	Useful for verifying backend issues

After applying the fixes, you can now create teams normally in the target tenant. Start by testing with a single user, then roll out to the rest of the organization. For future migrations, run the Azure AD group verification script before you cut over to avoid the same problem. As an advanced tip, use the Microsoft Graph API to bulk-check the groupType attribute of every migrated group within minutes.