Microsoft’s long‑running shift toward unbundled, modular licensing continues into April 2026 , and for Enterprise organisations (300+ users), the impact is even more significant than for SMBs.
Where smaller organisations must choose between Microsoft 365 “no Teams” SKUs and standalone Teams options, the Enterprise market faces a broader restructuring of E‑level and F‑level suites, new standalone Teams Enterprise SKUs, and evolving compliance requirements around Teams Phone and API‑driven workflows.
Here’s everything you need to know.
1. What’s Actually Changing?
Teams Removed From Enterprise Suites
Microsoft continues to separate Teams from its flagship Enterprise suites, including:
- Microsoft 365 E3 / E5 (no Teams)
- Office 365 E1 / E3 / E5 (no Teams)
This shift, first introduced in 2025, becomes effectively mandatory for new Enterprise customers going forward. Existing customers can continue using bundled SKUs (E3/E5 with Teams) for renewals, adds, and step‑ups , but Microsoft’s commercial direction is clear: Teams is becoming a distinct product, not a baked‑in feature.
Standalone Teams Enterprise SKU
Enterprise customers now have access to a dedicated Microsoft Teams Enterprise standalone licence.
This is designed for organisations that want precise control over Teams deployment across large, multi‑department estates.
2. Why Microsoft Is Making These Changes
Microsoft’s goal is to:
- Offer more flexible licensing for large organisations
- Allow customers to match Teams capabilities to departments or personas
- Reduce SKU overlap and simplify global compliance
- Respond to regulatory scrutiny around bundled applications
The outcome is a more modular ecosystem where organisations can architect collaboration and telephony on their own terms.
3. What This Means for Enterprise Organisation
A. More Granular, Role‑Based Licensing
Enterprise teams tend to have diverse user profiles , from knowledge workers to contact centre agents, field staff, and third‑party contractors.
The new structure makes it easier (and necessary) to align licensing with job function:
- Full Teams Enterprise for collaboration‑heavy workers
- Teams‑only licensing for voice‑centric or frontline staff
- Non‑Teams M365 suites for roles without collaboration needs
B. Increased Focus on Teams Phone & Voice Compliance
Several enterprise‑focused email threads emphasise a major enforcement by Microsoft:
All users AND resource accounts involved in calls must hold a Teams Phone (Phone System) licence with Enterprise Voice enabled.
This applies to:
- Contact centre workflows
- Auto attendants
- Call queues
- Bots
- Graph API‑driven transfers
For large estates (300–30,000 seats), these changes introduce operational overhead:
- Every call flow must be licence‑audited
- Every resource account (not just people) must be compliant
- Any automated or AI‑driven transfers must involve properly licensed endpoints
C. Multi‑Tenant & Multi‑Organisation Considerations
Large public sector and enterprise accounts often share tenants (e.g., shared services across councils).
This was highlighted when one organisation discovered an E5 licensing assumption no longer held true after Teams was unbundled
This adds complexity around:
- Shared telephony infrastructures
- Shared Teams policies
- Cross‑organisation licence governance
4. Cost Implications for Enterprise
Unbundling = Mixed impact
Costs may go up or down depending on structure:
- Organisations running Teams across all users may see slightly higher costs due to Teams Enterprise add‑ons.
- Organisations with mixed personas may reduce spend by reserving Teams licences only for those who truly need them.
As with the SMB licensing guidance, the theme remains the same:
- Teams is no longer “free with Microsoft 365.”
5. Preparing for April 2026: Enterprise Edition
1. Conduct a Tenant‑Wide Licensing Audit
Key checks include:
- Which users need Teams?
- Which users need Teams Phone / Enterprise Voice?
- Which resource accounts are tied to telephony workflows?
2. Rebuild Your Licence Personas
For Enterprise, persona modelling becomes essential.
Typical profiles now include:
- Collaboration Worker (E3/E5 + Teams Enterprise)
- Voice Worker (Teams Enterprise + Teams Phone)
- Contact Centre Agent (Teams Enterprise + Teams Phone + other CCaaS)
- Frontline (F3 + optional Teams)
- Resource Accounts (Teams Phone RA licence + EV)
3. Review Telephony & API‑Driven Workflows
Teams Phone enforcement applies equally to:
- Call queues
- Auto attendants
- Bots
- CCaaS platforms
Large estates often have legacy flows that will break without correction.
4. Communicate Internally : Especially to Subsidiaries
Enterprise organisations with multi‑site or multi‑region users need clear internal guidance around:
- Which licences can be assigned locally
- Which licences are centrally governed
- How Teams add‑ons should be requested
5. Evaluate Contract Renewal Timing
Since existing bundled E‑SKUs can still be renewed, some organisations may strategically renew early to extend their “grandfathered” status.
6. Whats Next?
For Enterprise customers, April 2026 isn’t a disruptive overhaul , it’s a step in Microsoft’s long‑term plan to make Teams a product that stands on its own.
The key takeaway is simple:
Enterprise organisations must now license Teams intentionally, not by default.
IF you’d like to find out more please get in touch.