Teams Premium (for Departments): identify the licence before you remove it

If Teams Premium (for Departments) has appeared in your Microsoft 365 tenant, do not start by deleting it.

Start by finding out what it is in your tenant.

Microsoft lists Teams Premium (for Departments) as a real product name in its official licensing service-plan reference. However, Microsoft’s public documentation does not say that this label always means a self-service trial, that it can never be assigned through a group, or that its presence indicates a fault.

The safe answer is therefore:

Treat the name as an identifier, not a diagnosis. Check the subscription, purchaser, expiry, assigned users and assignment source before changing anything.

This guide shows you how to make those checks, distinguish the two documented Teams Premium trial routes and remove or replace the licence without cutting people off unexpectedly.

Quick diagnosis

What you need to know	Where to check
Is it a self-service purchase or trial?	Microsoft 365 admin centre > Billing > Your products > Self-service trials, or filter Products by Self-service
Who acquired it and when does it expire?	Open the subscription under Billing > Your products
Who currently has a licence?	Open the product under Billing > Licences, or export the users from the self-service subscription
Is the assignment direct or group-based?	The product’s Licences page shows direct users and assigned groups separately
Is there a real assignment error?	Open the product’s Errors & issues tab and read the error for the affected user
Is the tenant using Teams Premium features?	Check with the meeting, communications, compliance and Teams administration owners before removal

Do not infer any of these answers from the words “for Departments” alone.

What Microsoft actually documents about the product

Microsoft’s current product-reference table contains these identifiers:

Field	Documented value
Product name	Teams Premium (for Departments)
String ID	`Teams_Premium_(for_Departments)`
GUID	`52ea0e27-ae73-4983-a08f-13561ebdb823`

That proves the product exists and gives administrators reliable values for inventory work. The same reference also lists the service plans included in the product.

It does not establish:

how your organisation acquired the subscription;
whether it is a 30-day admin trial or a 60-day self-service trial;
whether an administrator, user or partner initiated it;
whether a licence is direct or inherited from a group;
whether it is causing a licensing error.

Those are tenant facts. Check them in your own admin centre.

Teams Premium has two documented trial routes

The similar names are easy to confuse, but Microsoft documents two different trial journeys.

Admin-managed trial

An administrator can add a zero-cost Teams Premium trial to the organisation. Microsoft says this trial provides 25 licences for 30 days. The administrator chooses the participants and assigns the licences.

Microsoft’s Teams Premium trial deployment guide recommends defining the test cases, users, settings and feedback process before starting it.

User self-service trial

An eligible user can start a Teams Premium self-service trial from Teams desktop or the web app. Microsoft says this trial lasts 60 days, does not require payment details, and is not available to Government or EDU customers.

Administrators can see these subscriptions in the Microsoft 365 admin centre. However, Microsoft also says an administrator cannot assign or unassign licences from a user-owned self-service subscription until the administrator takes control of that subscription.

When either trial expires, users lose Teams Premium functionality. Microsoft says there is no grace period. Uploaded Premium assets such as meeting templates and backgrounds remain in the tenant, but become unavailable.

The label in the licensing table does not, on its own, tell you which of these routes created the subscription. The billing record does.

Step 1: identify the subscription owner and route

In the Microsoft 365 admin centre:

Go to Billing > Your products.
Open the Self-service trials tab. Also check the Products tab with the Self-service filter.
If the subscription appears, record its product name, purchaser, expiry date, quantity and assigned users.
Export the user list before making a change.
If it does not appear there, check the other subscriptions under Your products and speak to your licensing partner if the purchasing route is unclear.

This check matters because a user-owned self-service subscription has a different management path from a centrally acquired subscription.

Step 2: inspect assignments and real errors

Go to Billing > Licences, select the product and inspect its assignments.

Microsoft’s current admin-centre documentation says the page distinguishes:

a direct user assignment, where the person appears individually; and
a group-based assignment, where the group name appears instead of every member.

Open Errors & issues as well. Microsoft lists several common causes of licence assignment failure, including insufficient licences, conflicting service plans and an invalid usage location.

Do not assume a MutuallyExclusiveViolation, a provisioning failure or an Entra Connect fault unless the affected user’s actual error shows it. The product label is not error evidence.

Optional read-only Graph inventory

The admin centre is the best place to establish subscription ownership. Microsoft Graph PowerShell is useful when you also need a repeatable inventory.

The following commands only read tenant and user licence information:

Connect-MgGraph -Scopes "Organization.Read.All","User.Read.All"

$departmentsSku = Get-MgSubscribedSku -All |
    Where-Object SkuPartNumber -eq 'Teams_Premium_(for_Departments)'

if (@($departmentsSku).Count -ne 1) {
    throw "Expected one Teams Premium (for Departments) SKU. Review Get-MgSubscribedSku output before continuing."
}

$departmentsSku |
    Select-Object SkuPartNumber, SkuId, CapabilityStatus, ConsumedUnits, PrepaidUnits

$assignedUsers = Get-MgUser -All `
    -Property Id,DisplayName,UserPrincipalName,AssignedLicenses,LicenseAssignmentStates |
    Where-Object { $_.AssignedLicenses.SkuId -contains $departmentsSku.SkuId }

$assignedUsers | ForEach-Object {
    $user = $_
    $states = $user.LicenseAssignmentStates |
        Where-Object SkuId -eq $departmentsSku.SkuId

    foreach ($state in $states) {
        [PSCustomObject]@{
            DisplayName       = $user.DisplayName
            UserPrincipalName = $user.UserPrincipalName
            AssignedBy        = if ($state.AssignedByGroup) {
                "Group: $($state.AssignedByGroup)"
            } else {
                "Direct or subscription-managed — confirm in the admin centre"
            }
            State             = $state.State
            Error             = $state.Error
        }
    }
}

AssignedByGroup can identify an inherited group assignment. A blank value does not prove that a user personally started a trial; confirm that in Billing > Your products.

In a very large directory, use the admin-centre export or a reviewed Graph query rather than casually enumerating every user in an interactive session.

Step 3: find out what would stop working

Teams Premium is an add-on to a base Teams licence. It contains a mix of organiser-based, attendee or user-based, and admin-based features.

That distinction matters. It is wrong to say that only meeting organisers ever need Teams Premium.

For example, Microsoft documents some meeting protection and branding features as organiser-based. Other capabilities, including parts of intelligent recap, alerts, Queues and administrator analytics, depend on the licence of the user or administrator who consumes them.

Before removal, ask:

Are organisers using Premium meeting templates, themes, watermarks or encryption?
Are licensed users relying on intelligent recap or translated meeting features?
Are Teams administrators using Premium analytics or quality controls?
Is the Queues app in use, and do its users also have the required Teams Phone licence?
Are meeting templates, backgrounds or sensitivity-label configurations tied to the trial?
Is there a centrally purchased Teams Premium licence ready for anyone who must keep access?

Use Microsoft’s current Teams Premium licensing matrix for the feature-by-feature decision. Microsoft changed parts of Teams Premium and Teams Enterprise licensing on 1 April 2026, so an old feature list is not a safe purchasing guide.

Step 4: choose the correct removal path

There are three common outcomes.

Keep it and govern it

If it is a valid centrally managed subscription and the assigned people still need it, document the owner, renewal or expiry date, assignment method and supported use cases. Fix any actual errors shown under Errors & issues rather than removing a legitimate product.

Move users to a centrally managed Teams Premium subscription

For a self-service subscription, Microsoft provides a takeover workflow:

Make sure the destination subscription has one available licence for every person being moved.
Go to Billing > Your products and filter Products by Self-service.
Open the subscription and choose Take control of this subscription.
Choose Move users, select the destination product and complete the move.
Confirm that the replacement licences are active before testing the affected Teams features.

Microsoft says the old self-service subscription is automatically cancelled after the move. The original purchaser receives an email.

This is usually safer than cancelling first because it gives users a replacement entitlement as part of the controlled change.

Cancel or unassign it

Only do this when the owner and affected teams have confirmed that the entitlement is no longer required.

Microsoft says you must be at least a Licence Administrator or User Administrator to assign or unassign centrally managed licences in the Microsoft 365 admin centre. Self-service takeover has separate billing-role requirements, which depend on the organisation's billing account type.

For a centrally managed direct assignment, use Billing > Licences, select the users and choose Unassign licences.
For a group assignment, change the assignment on the product or group. Removing a direct licence from one user does not remove an inherited group assignment.
For a self-service purchase or trial, take control of the subscription first. Microsoft’s cancellation flow removes access from assigned users and notifies the original purchaser.

Export the affected users, name a rollback owner and test one low-risk account before a wider change.

Optional single-user PowerShell removal

Use this only after confirming that the licence is centrally managed, directly assigned and safe to remove. It is not a substitute for taking control of a self-service subscription, and it cannot remove a licence inherited from a group.

Connect-MgGraph -Scopes "User.ReadWrite.All","Organization.Read.All"

$userUpn = Read-Host "User principal name"
$departmentsSku = Get-MgSubscribedSku -All |
    Where-Object SkuPartNumber -eq 'Teams_Premium_(for_Departments)'

if (@($departmentsSku).Count -ne 1) {
    throw "SKU lookup was not unambiguous. Nothing was changed."
}

Get-MgUserLicenseDetail -UserId $userUpn |
    Where-Object SkuId -eq $departmentsSku.SkuId |
    Format-List SkuPartNumber,SkuId,ServicePlans

$confirmation = Read-Host "Type REMOVE to unassign this verified direct licence"
if ($confirmation -eq 'REMOVE') {
    Set-MgUserLicense -UserId $userUpn `
        -RemoveLicenses @($departmentsSku.SkuId) `
        -AddLicenses @{}

    Get-MgUserLicenseDetail -UserId $userUpn
} else {
    Write-Host "No change made."
}

Do not turn this into a bulk-removal loop until the first change has been checked in Teams and in the admin centre.

Step 5: control future self-service Teams Premium trials

Blocking future self-service trials is a separate decision from cleaning up existing subscriptions.

In the Microsoft 365 admin centre, go to:

Settings > Org settings > Services > Self-service trials and purchases

Select the Teams Premium product and choose Do not allow if that is your approved policy.

Microsoft says the setting is managed per product, can take up to 72 hours to take effect, and does not change trials or purchases that already exist. For Teams trials, users might need to close and restart Teams before the new policy is reflected.

Microsoft requires a Global Administrator for this admin-centre policy change. For MSCommerce, Microsoft documents the Global Administrator or Billing Administrator role for changes, and Global Reader for a read-only policy list. Keep the number of Global Administrators to a minimum.

You can make the same per-product change with Microsoft’s MSCommerce PowerShell module. Discover the current product record before changing it:

Import-Module MSCommerce
Connect-MSCommerce

$teamsPremiumPolicy = Get-MSCommerceProductPolicies `
    -PolicyId AllowSelfServicePurchase |
    Where-Object ProductName -eq 'Teams Premium Introductory Pricing'

if (@($teamsPremiumPolicy).Count -ne 1) {
    throw "Teams Premium policy lookup was not unambiguous. Review the product list."
}

$teamsPremiumPolicy

Update-MSCommerceProductPolicy `
    -PolicyId AllowSelfServicePurchase `
    -ProductId $teamsPremiumPolicy.ProductId `
    -Value "Disabled"

Get-MSCommerceProductPolicy `
    -PolicyId AllowSelfServicePurchase `
    -ProductId $teamsPremiumPolicy.ProductId

The product name above is the one in Microsoft’s current MSCommerce reference. Reading it from the service avoids embedding a commerce product ID that may later change.

A safe administrator checklist

Confirm the product and subscription in Billing > Your products.
Establish whether it is central, admin-trial or self-service.
Record the purchaser, expiry, quantity and assigned users.
Inspect direct and group assignments.
Read the actual Errors & issues entry instead of guessing.
Check which Teams Premium features people are using.
Prepare replacement licences before moving users.
Export the before-state and nominate a rollback owner.
Test one low-risk user.
Recheck the user’s licence and Teams experience.
Decide separately whether future self-service trials should be blocked.

Frequently asked questions

What is Teams Premium (for Departments)?

It is a product name in Microsoft’s official licence and service-plan reference. Microsoft publishes its string ID and GUID, but does not publicly define the name itself as proof of a particular purchasing or trial route. Inspect the subscription in your tenant before classifying it.

Is Teams Premium (for Departments) definitely a self-service trial?

No conclusion should be drawn from the name alone. Microsoft documents 30-day admin-managed and 60-day user self-service Teams Premium trials. Billing > Your products shows whether a subscription in your tenant is self-service, who acquired it and when it expires.

Can Teams Premium (for Departments) be assigned through a group?

Microsoft’s public product reference does not state that this SKU is universally barred from group assignment. Check the product’s assignment list and the affected user’s licenseAssignmentStates. If an assignment has failed, use the actual message under Errors & issues rather than assuming the product name is the cause.

Can an administrator remove a self-service Teams Premium licence?

Microsoft says administrators cannot assign or unassign licences in a user-owned self-service subscription until they take control of it. The takeover workflow can move users to a central subscription or cancel the self-service subscription.

Does blocking self-service trials remove existing licences?

No. Microsoft says the per-product policy affects future acquisitions. Existing purchases and trials are not changed, and the policy can take up to 72 hours to take effect.

Official Microsoft sources

If you look after Teams licensing, policies and the SharePoint sites created around Teams, join SharePoint & Teams Admins. It is the Collab365 Space for administrators who need current, practical answers without pretending Microsoft 365 is simpler than it is.