Content reviewed: 12 October 2026
The April update does not justify automatically renewing or removing every Teams Premium licence. From 1 April 2026, selected event features moved to Teams Enterprise and workspace licensing changed. Ordinary meeting protection, personal intelligence features and the Queues app retain their own requirements. Start with Microsoft’s announcement and the exact feature in use.
The base licence and the add-on solve different needs
Teams Enterprise provides the Teams service for an eligible user. Teams Premium is an add-on to a base Teams licence, not a replacement for it. For a new customer using an Enterprise suite without Teams, first confirm the separate Teams Enterprise entitlement or the applicable regional variant. Only then assess Premium. Seeing the add-on in a quote does not prove the user has the right base licence; inspect both assignments and the enabled service plans. Microsoft explains the relationship in its add-on licensing guide.
What changed in April 2026
Separate ordinary meetings, events and workspaces. Webinar branding and an ordinary meeting template are different entitlements. Desk booking is not necessarily a personal Premium feature merely because people previously accessed it with Premium.
| Use | What to assess now | Renewal consideration |
|---|---|---|
| Advanced town hall/webinar streaming chat, reactions, event insights, event branding and eCDN | Teams Enterprise and the selected event format | Event capacity and features have further limits. |
| Watermarks, advanced protection and personalisation for ordinary meetings | Teams Premium by role | Moving event features does not move every meeting feature. |
| Personal AI notes and tasks | The user’s entitlement to the specific intelligence feature | The organiser’s licence does not automatically share personal features. |
| Queues app | Teams Premium and Teams Phone | Separate from a queue resource account licence or PSTN funding. |
| Places Finder and Places Explorer | Eligible licences with Outlook and Teams calendar access | Not merely a move into standalone Teams Enterprise. |
| Individual desk booking | Space licensing: Shared Space or Single Space | Since April, licensed by space rather than Premium for every person booking. |
For workspaces, check the current Shared Space rules. A space or device licence is not a universal user entitlement. Check directory readiness and configuration: removing Premium does not create a bookable desk.
The current documentation includes events for up to 3,000 concurrent attendees with audience engagement and up to 10,000 in view-only mode with Q&A under Teams Enterprise. Full camera and microphone participation has a different product limit. A larger event may need an Attendee Capacity Pack even when its ordinary event features no longer need Premium.
Meeting roles change the licensing answer
The Premium requirement is not necessarily the same for the organizer, attendee and administrator. Some capabilities follow the organizer’s licence for a meeting, whereas others benefit only the individually licensed attendee or administrator. Do not count every Teams user as a Premium candidate. List your scenarios instead: who hosts sensitive meetings, who needs translated captions, who administers advanced policies, and who works with queues or virtual appointments. Check the entitlement rule for each scenario in Microsoft’s Premium licensing guidance.
For Advanced collaboration analytics, Microsoft explicitly requires Premium for every tenant user. One active Premium licence enables feature management but does not replace that tenant-wide requirement. Establish whether the organisation uses this analytics capability before reducing assignments.
Example: count distinct licence holders
A hypothetical company has 180 users. Eight organisers need Premium protection for ordinary meetings and six users need personal Premium features; two people belong to both groups. Another 45 use only the event features that moved. With the right base entitlement and no further Premium needs, the candidate scope is 8 + 6 − 2 = 12 people, rather than the sum of every role.
If the company also uses Advanced collaboration analytics, that calculation does not establish that 12 licences suffice: the documented requirement covers all 180 tenant users. The example shows why the feature must be established before counting distinct holders.
These are illustrative figures, not a customer case study or promised saving. Candidate assignments after a pilot are not the subscription quantity already ordered. Assess the financial result against the actual purchase term and proposed order.
Build a pilot matrix
Before changing a broad population, create a compact matrix with the feature, user or role, present licence, proposed entitlement and a test case. Include organizers of different meeting types, ordinary attendees and administrators. Test in the real tenant after assigning or removing the add-on: look at available settings, meeting behavior and usage evidence. The licensing portal alone is not enough. A feature may also depend on meeting role, Teams policy or a related entitlement; the pilot must establish what the user can actually do.
| Record | What it should establish |
|---|---|
| Feature and context | Ordinary meeting, event, personal recap, analytics or space |
| Actual holder | Organiser, individual user, admin, space or device |
| New entitlement | Base Teams, Premium, space licence or capacity pack |
| Pilot evidence | A working scenario without reliance on another remaining licence |
| Date and commitment | Purchase before/after 1 April 2026, term expiry and event date |
The pilot must distinguish a base Teams feature from one still supplied by the old Premium entitlement. Use controlled accounts and check remaining assignments, the actual organiser, policies and other relevant licences. A test during the current term without those checks does not prove the post-renewal position.
An existing purchase and a renewal are different decisions
Microsoft says customers who bought Teams Premium before 1 April 2026 retain access to the previously included experiences until those licences expire. Separate a new purchase decision from an existing commitment. Record the purchase date, end of term, assigned users, features in use and intended state after renewal. Removing the licence too early can disrupt a real workflow, while automatic renewal can preserve an unused add-on. Have both the service owner and procurement owner agree on the outcome.
For event organisers with Premium purchased before 1 April 2026, the documentation retains capacity up to 100,000 until the current term ends. Afterwards, events with audience engagement above 3,000 may require a capacity pack. Scheduling alone does not preserve the entitlement; the organiser’s licence at event time matters too.
Compare cost only after normalizing entitlements
Compare the full combination: base suite, Teams entitlement, distinct Premium users, any capacity packs and licensed spaces. Align country, licence term, currency, tax treatment and billing frequency across quotes. Without those inputs, a percentage saving is unsupported, and removing an assignment must not be treated as reducing the billed subscription quantity.
Review assignments after the change
After rollout, review assignment and usage regularly. A new meeting organizer, a change in protection policy or the introduction of queues may create a new need for the add-on; a departing employee may release a licence. Keep a reason, owner and next review date for every exception. Recheck Microsoft’s current documentation whenever the product changes because feature names and licensing matrices evolve. This makes the decision understandable at the next renewal.
- 01
Export licenses and roles
Separate meeting organizers, admins and advanced-communication users.
- 02
Compare actual use
Check whether Teams Enterprise now covers each capability.
- 03
Review existing subscriptions
Record purchase date and expiry of prior entitlements.
- 04
Adjust the next term
Keep Premium for the users and features that still require it.
Frequently asked questions
Did every Premium feature move to Enterprise?
No. Selected event capabilities moved. Advanced ordinary meeting protection, personalisation, intelligence and the Queues app retain their own requirements.
Is Places Finder available only with Teams Enterprise?
The announcement applies it to eligible licences with Outlook and Teams calendar access. That scope is separate from Teams Enterprise event entitlements.
Can we keep one Premium licence for the admin?
Not as a general rule. One active licence enables management, but personal features need the relevant holders, and Advanced collaboration analytics requires coverage for every tenant user.
Does everyone booking a desk need Premium?
Since April 2026, individual desk booking uses the applicable Shared Space licence for the space rather than Premium for every person booking. The space still needs correct configuration.
Can old Premium cover an event after expiry?
Scheduling alone is insufficient. Check the current term’s end and the organiser’s entitlement on the event date, including any Attendee Capacity Pack.
The Teams Premium and Rooms guide covers the products for users, rooms and events. Keep a decision for each feature, distinct licence holders, pilot conditions and the order status for the next term.








