Manage user access to Microsoft Teams


The Microsoft Teams admin center is gradually replacing the Skype for Business admin center, and we're migrating Teams settings to it from the Microsoft 365 admin center. If a setting has been migrated, you'll see a notification and then be directed to the setting's location in the Teams admin center. For more information, see Manage Teams during the transition to the Teams admin center.

At the user level, access to Microsoft Teams can be enabled or disabled on a per-user basis by assigning or removing the Microsoft Teams product license.

Use messaging policies, managed from the Teams Admin Center, to control what chat and channel messaging features are available to users in Teams. You can use the default policy or create one or more custom messaging policies for people in your organization. To learn more, read Manage messaging policies in Teams.


Microsoft recommends that you turn on Teams for all users in a company so that teams can be formed organically for projects and other dynamic initiatives. Even if you are deciding to pilot, it may still be helpful to keep Teams enabled for all users, but only target communications to the pilot group of users.

Manage Teams through the Microsoft 365 admin center

Teams user-level licenses are managed directly through the Microsoft 365 admin center user management interfaces. An administrator can assign licenses to new users when new user accounts are created, or to users with existing accounts. The administrator must have Office 365 Global Administrator or User Management Administrator privileges to manage Microsoft Teams licenses.

When a license SKU like E3 or E5 is assigned to a user, a Microsoft Teams license is automatically assigned, and the user is enabled for Microsoft Teams. Administrators can have a granular control over all the Office 365 services and licenses, and the Microsoft Teams license for a specific user or a group of users can be enabled or disabled.

Screenshot of Product licenses section in admin center.

A Teams user license can be disabled at any time. Once the license is disabled, the users access to Microsoft Teams will be prevented and the user will no longer be able to see Teams in the Office 365 app launcher and homepage.

Screenshot showing Teams selected in the Product licenses section.

Manage via PowerShell


New-MsolLicenseOptions will enable all services that were previously disabled unless explicitly identified in your customized script. As an example, if you wanted to leave both Exchange & Sway disabled while additionally disabling Teams, you'd need to include this in the script or both Exchange & Sway will become enabled for those users you've identified. To use a GUI to manage this functionality, see Office 365 License Reporting and Management Tool -Assign Remove Licenses in Bulk for more information.

Enabling and disabling Teams as a workload license through PowerShell is done just as any other workload. The service plan name is TEAMS1 for Microsoft Teams. For GCC the service plan name is TEAMS_GOV. For GCC High the service plan name is TEAMS_GCCHIGH. For DoD the service plan name is TEAMS_DOD (See Disable access to services with Office 365 PowerShell for more information.)

Sample: The following is just a quick sample on how you would disable Teams for everyone in a particular license type. You'll need to do this first, then individually enable it for the users who should have access for piloting purposes.

To display the subscription types you have within your organization, use the following command:


Fill in the name of your plan that includes your organization name and the plan for your school (such as ContosoSchool:ENTERPRISEPACK_STUDENT), and then run the following commands:

  $acctSKU="<plan name>
  $x = New-MsolLicenseOptions -AccountSkuId $acctSKU -DisabledPlans "TEAMS1"

To disable Teams for all users with an active license for your named plan, run the following command:

  Get-MsolUser | Where-Object {$_.licenses[0].AccountSku.SkuPartNumber -eq  ($acctSKU).Substring($acctSKU.IndexOf(":")+1,  $acctSKU.Length-$acctSKU.IndexOf(":")-1) -and $_.IsLicensed -eq $True} |  Set-MsolUserLicense -LicenseOptions $x
An icon representing a decision point Decision Point
  • What is your organization’s plan for Teams onboarding across the organization? (Pilot or Open)
An icon representing the next steps Next Steps
  • If onboarding via a closed Pilot, decide if you would like to do so via licensing, or targeted communication.
  • Depending on decision, take steps to make sure only Pilot users who are allowed to access Teams (if needed).
  • Document the guidelines for which users who will (or will not) have access to Teams.

Manage Teams at the Office 365 tenant level


Tenant-level control for Teams has been removed (effective August 2018). Control access to Teams in your organization with user-level licensing. To learn more, see Manage user access to Microsoft Teams.