When you create a new Microsoft 365 tenant and try to assign a Teams policy package in the Teams admin center, the assignment may fail with an error. This usually happens because the policy package is not yet visible or the user lacks the required admin role. In this article, you will learn why the assignment fails and how to resolve it step by step.
The root cause is often a delay in provisioning the policy package or a missing license assignment. You will also find a workaround using PowerShell when the admin center does not show the package.
Key Takeaways: Fixing Teams Policy Package Assignment in a New Tenant
- Teams admin center > Users > Manage users > Policies: Shows the effective policy assignments that can block a policy package.
- Microsoft 365 admin center > Billing > Licenses: Ensures the user has a Teams license, which is required for policy assignment.
- PowerShell command Get-CsUserPolicyPackage: Lists available policy packages when the admin center does not show them.
Why Teams Policy Package Assignment Fails in a New Tenant
A policy package is a collection of predefined Teams policies for a specific role, such as an educator or a frontline worker. In a new tenant, the package might not be available immediately after you create the tenant. Microsoft provisions policy packages asynchronously, which means the package may take up to 24 hours to appear in the admin center.
Another common cause is that the user does not have a Teams license assigned. Without a license, the Teams admin center refuses to apply any policy package. Additionally, the admin who performs the assignment must have the Teams Administrator or Global Administrator role. If you are using a custom role, it may not include the permission to assign policy packages.
Provisioning Delay in New Tenants
When you sign up for a new tenant, the policy package definitions are not created instantly. The Teams service creates them as part of the background setup. If you try to assign a package before this process finishes, you will see an error that says the package does not exist or is not available.
License and Role Requirements
Each user must have a valid Teams license, such as Microsoft 365 Business Basic or Enterprise E3. The assigning admin must have the Teams Administrator or Global Administrator role in Azure AD. Without these, the assignment fails even if the package exists.
Steps to Diagnose Teams Policy Package Assignment Issues in a New Tenant
Follow these steps in order to identify and fix the problem.
- Verify the user has a Teams license
Go to the Microsoft 365 admin center at admin.microsoft.com. Select Billing > Licenses. Find the user and confirm that Teams is enabled. If not, assign a license that includes Teams. - Check your admin role
In the Microsoft 365 admin center, go to Users > Active users. Select your account and view the Roles tab. Ensure you have the Teams Administrator or Global Administrator role. If not, ask a global admin to assign it to you. - Wait for the policy package to appear
Open the Teams admin center at admin.teams.microsoft.com. Go to Teams > Policy packages. If the package you need is not listed, wait up to 24 hours after tenant creation. Refresh the page after a few hours. - Assign the policy package manually
When the package is visible, go to Teams > Policy packages. Select the package, then select Manage users. Search for the user, select them, and choose Apply. Confirm the assignment. - Use PowerShell as a workaround
If the package still does not appear, use PowerShell. Install the Teams PowerShell module and run Connect-MicrosoftTeams. Then run Get-CsUserPolicyPackage to list available packages. If the package exists, run Grant-CsUserPolicyPackage -Identity “user@domain.com” -PackageName “Education_Teacher” to assign it.
If Teams Policy Package Assignment Still Fails
“Policy package not found” error in the admin center
This error means the package has not been provisioned yet. Wait 24 hours and refresh. If it persists, create a support ticket with Microsoft and mention the tenant ID and the package name.
User already has a policy package assigned
A user can have only one policy package at a time. If the user already has a package, you must remove it first. Use PowerShell: Remove-CsUserPolicyPackage -Identity “user@domain.com” -PackageName “Old_Package”. Then assign the new package.
PowerShell returns an error about permissions
The PowerShell session must run with an account that has the Teams Administrator role. Reconnect with a different account or ask a global admin to run the command.
Teams Admin Center vs PowerShell for Policy Package Assignment
| Item | Teams Admin Center | PowerShell |
|---|---|---|
| Availability | May not show the package for up to 24 hours | Lists packages as soon as they are provisioned |
| Role required | Teams Administrator or Global Administrator | Teams Administrator or Global Administrator |
| Batch assignment | Manual, one user at a time | Can assign to multiple users with a script |
| Error messages | Generic error without details | Detailed error output for troubleshooting |
After you assign the policy package, the policies apply within a few minutes. You can verify the assignment in the Teams admin center under Users > Manage users > Policies. To confirm the effective policies, use Get-CsUserPolicyAssignment in PowerShell.
If you manage many users, consider using PowerShell to automate the assignment. You can also create a custom policy package in the admin center under Teams > Policy packages > Add, but this is only available after the initial provisioning delay.