Users can start a 60-day Teams Premium self-service trial from inside Teams, and the admin-side change can take up to 72 hours to fully apply. That is the part that matters here: this is not just a cosmetic button. It is a governance setting, and if you leave it alone, users will keep discovering features you never agreed to roll out.
The source article shows the practical fix well. I agree with the direction: for most organizations, disabling self-service trials for Teams Premium is the right default. An agent, app, or user should not get a blank check to introduce new product behavior into your tenant just because Microsoft decided to place a prompt in the client.
What this button actually does
The Unlock Teams Premium entry in Teams can let eligible users start a self-service Teams Premium trial. Microsoft documents that these user-started trials last 60 days, while the admin-acquired zero-cost trial is a separate 30-day experience with 25 assignable licenses.
That distinction matters. If you want a controlled evaluation, use the admin trial. If you leave self-service on, you get fragmented testing, user confusion, and the usual follow-up question: why can one user see a feature that the rest of the tenant cannot?
There is also a second-order issue: Microsoft says self-service purchases and trials are managed per product, not with one tenant-wide kill switch. So this is rarely a one-and-done cleanup. If your team cares about spend control and predictable user experience, this is exactly the kind of thing worth including in an AI and automation audit.
How to disable Teams Premium self-service trials
You have two supported ways:
- In the Microsoft 365 admin center: Settings > Org settings > Services > Self-service trials and purchases.
- With the MSCommerce PowerShell module.
For Teams Premium, set the product to Do not allow.
One important correction to common blog advice: Microsoft’s current documentation says the change can take up to 72 hours to take effect. The source mentions 24 to 48 hours, which may happen in practice, but I would plan for 72. Microsoft also notes that for Teams self-service trials, users may need to close and restart the Teams app.
The PowerShell way I would use
If you manage more than one tenant, or if you want something repeatable, use PowerShell. This is the cleanest approach from the source, with the parameter style reflected in Microsoft documentation:
Install-Module MSCommerce -Scope CurrentUser
Connect-MSCommerce
$policy = Get-MSCommerceProductPolicies -PolicyId AllowSelfServicePurchase |
Where-Object { $_.ProductName -like "*Teams Premium*" }
$policy
Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $policy.ProductId -Enabled $False
To verify:
Get-MSCommerceProductPolicies -PolicyId AllowSelfServicePurchase |
Where-Object { $_.ProductName -like "*Teams Premium*" }
If you are standardizing this across products, this fits nicely into broader PowerShell and Azure automation work, especially if you already manage tenant baselines as code.
What this does not solve
This is the part admins should be realistic about.
Microsoft’s own FAQ says disabling self-service blocks the trial or purchase activation, but it doesn’t always remove in-product upgrade prompts. Community threads around this button have been noisy for exactly that reason. In other words, the control is about entitlement, not guaranteed UI cleanliness.
So my practical read is:
- If your tenant currently allows Teams Premium self-service trials, turn it off.
- If the prompt still appears for some users, verify after 72 hours and after a client restart.
- If you built internal guidance assuming every upsell prompt can be fully hidden, recheck that assumption.
For most orgs, this is a small but worthwhile hardening step. It reduces user confusion, stops unmanaged trial sprawl, and gives IT back control over how Teams Premium gets evaluated. If you are building governed Microsoft Copilot and AI agents, the same principle applies everywhere: trial-first product exposure without admin intent is not a feature, it is drift.
