You try to create a team in Microsoft Teams, but the option is grayed out, or you get an error saying you cannot create a team. This problem usually happens because your organization restricts who can create Microsoft 365 Groups. The restriction is controlled by an Azure Active Directory setting that limits group creation to specific security groups. This article explains the exact cause and shows you how to fix it using the Azure AD admin center.
When you cannot create a team, the root cause is almost always the group creation policy in Azure Active Directory. Teams uses Microsoft 365 Groups as its underlying membership and permission system. If your account is not allowed to create groups, Teams blocks the team creation flow. You will see the New team button grayed out, or you will receive an error message when you try to create a team from an existing group.
This article covers the technical reason for the block, the step-by-step fix for administrators, and related scenarios where users still cannot create teams after the main fix.
Key Takeaways: Fixing Team Creation Blocked by Azure AD Group Policies
- Azure AD > Groups > General > Group settings: Shows the toggle that restricts who can create Microsoft 365 Groups.
- Azure AD > Groups > General > Group settings > Assign access: Lets you add security groups that are allowed to create groups.
- Teams admin center > Users > Manage users > Policies: Shows the effective Teams policy assignments that can enable or block a feature.
Why Microsoft Teams Cannot Create a Team in a Microsoft 365 Group
Teams is built on top of Microsoft 365 Groups. Every team you create in Teams automatically creates a corresponding Microsoft 365 Group. That group holds the membership list, the shared mailbox, the SharePoint site, and the OneNote notebook. When you create a team, Teams calls the Azure AD API to create a new group. If your user account does not have permission to create groups, the API call fails and Teams shows an error.
Azure AD has a setting called Users can create Microsoft 365 groups in Azure portals, API or PowerShell. This setting is controlled by an administrator in the Azure Active Directory admin center. By default, the setting is set to Yes for all users. When an organization changes this to No, only users who are members of the specified security groups can create groups. If your account is not in those groups, you cannot create a team.
Another common cause is that the setting is set to Yes, but the Restrict access to Groups in Azure AD portal setting is enabled. This second setting blocks the group creation UI in the Azure portal, but it does not block Teams. However, if your administrator has also set the Group creation policy in the Teams admin center to Off for your policy, that will block team creation regardless of the Azure AD setting.
How the Azure AD Setting Works
The Azure AD setting is located in the Azure Active Directory admin center under Groups > General. The exact label is Users can create Microsoft 365 groups in Azure portals, API or PowerShell. When set to No, the admin must specify one or more security groups that are allowed to create groups. Users who are not members of those security groups will see the New team button grayed out in Teams.
The setting applies to all Microsoft 365 services that use groups, including Teams, Outlook, SharePoint, and Planner. So the same block will also prevent a user from creating a new Outlook group or a new Planner plan.
Steps to Fix Team Creation Blocked by Azure AD Group Policies
The fix requires administrator access to the Azure Active Directory admin center. If you are not an administrator, contact your IT department and ask them to check the group creation setting. The steps below are for an administrator.
- Sign in to the Azure AD admin center
Go to https://aad.portal.azure.com and sign in with an account that has the Global Administrator or Groups Administrator role. - Open the Groups blade
In the left navigation, select Groups, then select General under the Settings section. - Check the group creation setting
Look for the setting Users can create Microsoft 365 groups in Azure portals, API or PowerShell. If it is set to No, change it to Yes to allow all users to create groups. If you want to restrict creation to specific security groups, keep it set to No and proceed to the next step. - Add a security group for allowed users
If the setting is No, you must specify which security groups can create groups. Select the option Yes for Assign access, then click Add and choose the security group that contains the users who need to create teams. Click Select to confirm. - Save the changes
Click Save at the top of the page. The change takes effect within a few minutes, but it may take up to 30 minutes to propagate across all services. - Verify the Teams admin center policy
Open the Teams admin center at https://admin.teams.microsoft.com. Go to Teams > Teams policies. Select the policy assigned to the user and check that the Create private channels setting is not relevant. The main setting to check is Microsoft 365 group creation under General in the policy. This setting must be set to On for the user to create teams. - Ask the user to sign out and sign back in
After the policy change, the user must sign out of Teams and sign back in. This refreshes the user’s permissions from Azure AD. If the user is using the Teams desktop app, they should fully close it and restart it.
If the User Is Not in the Allowed Security Group
If your organization intentionally restricts group creation, the fix is to add the user to the allowed security group. The user must be a member of the security group you specified in the Azure AD setting. After adding the user, wait for the group membership to propagate, then have the user sign out and sign back in.
If Teams Still Has Issues After the Main Fix
Teams Shows a Grayed-Out New Team Button
If the New team button is still grayed out after the Azure AD fix, the user may be in a Teams policy that disables team creation. Check the Teams admin center under Teams > Teams policies. Select the policy assigned to the user and verify that Microsoft 365 group creation is set to On. If it is Off, change it to On and save.
Error Message: You Can’t Create a Team Because You Don’t Have Permission
This error appears when the user tries to create a team from an existing Microsoft 365 group. The user may have access to the group but not be a group owner. To create a team from a group, the user must be an owner of that group. Ask the group owner to add the user as an owner in the group settings.
User Cannot Create a Team in the Teams Web App
The Teams web app uses the same permissions as the desktop app. If the web app fails but the desktop app works, clear the browser cache and cookies, then try again. Also check that the browser is up to date and that third-party cookies are allowed for the Teams domain.
Azure AD Setting vs Teams Policy: Key Differences
| Item | Azure AD Setting | Teams Policy |
|---|---|---|
| Where to configure | Azure AD admin center > Groups > General | Teams admin center > Teams > Teams policies |
| Controls | Creation of Microsoft 365 Groups across all services | Creation of teams within Teams only |
| Default value | Yes for all users | On for all users |
| Effect on Teams | Blocks the New team button if set to No | Blocks the New team button if set to Off |
| Admin role needed | Global Administrator or Groups Administrator | Teams Administrator |
Both settings must allow team creation for the user to succeed. If either one blocks it, the user cannot create a team. Check both locations when troubleshooting.
You can now diagnose and fix the Cannot create a team error by checking the Azure AD group creation setting and the Teams policy. Start with the Azure AD setting because it is the most common cause. If the user still has issues, verify the user is a group owner when creating a team from an existing group. For administrators, the Azure AD setting is the primary control, and the Teams policy is the secondary control. Use PowerShell with the Get-AzureADDirectorySetting cmdlet to audit the current group creation policy across your tenant.