On March the 9th Microsoft announced their first new enterprise tier in over a decade, the E7!
This immediately drew attention across licensing and IT leadership circles as Microsoft does not create a new enterprise tier unless it wants to shift the market.
Consider history: E3 gave organisations cloud productivity and Teams collaboration. E5 represented the shift to enterprise‑grade communications, with integrated security, compliance and full Teams Phone capabilities. With E7 Microsoft is signalling us to get ready for the agent era: a world where employees, copilots and AI agents all operate inside the same identity and security framework.
Whether customers are truely ready is another question.
E7 – The Frontier Suite
E7 bundles four components- E5, Copilot, Entra Suite and Agent 365 – into a single “Frontier” licence at 99 USD per user per month, versus roughly 117 USD if bought separately.
Generally available 1st May 2026.
Damovo view: E7 is E5’s “AI‑era” heir
E7 is not a finished destination; it’s the next architectural layer in the same family Microsoft has been building for over a decade.
E5 launched in 2015 as a bold, forward-looking bundle but it took years before organisation truely understood where it fit. E7 follows the same pattern, but at AI speed. It is positioned for organisations moving from AI trials to a governed, agent‑operated model.
The E7 bundle:
- E5: for security, compliance, voice, collaboration
- Copilot: embedded AI in Office and Teams
- Entra Suite: Identity, Zero Trust Network Access (ZTNA) and secure web access
- Agent 365: AI Agent visibility, policy and lifecycle management
Some parts are mature. Others, such as agent governance, AI‑driven UC and CC automation and deeper ZTNA adoption, we can expect to evolve over the next two to three years. It’s too early to think of E7 as a finished stack. More as a platform in motion where you buy into a roadmap, not a final product.
When E7 is probably wrong in 2026
Say No Go or maybe “Not yet” if:
- You are still on E3 or only recently moved to E5 and have not finished deploying E5 security, compliance or Teams capabilities.
- You have not yet run measured Copilot pilots with clear outcomes: time saved, quality uplift, adoption levels.
- Identity and Zero Trust are weak in your organisation: inconsistent Conditional Access, legacy VPN usage, or incomplete Entra ID hygiene.
- You rely on hybrid UC or CC architectures (Teams plus Cisco, Zoom, NICE, Genesys etc) and so cannot narrow your ecosystem too early.
The reality is that for many organisations, E7 is currently over‑licensed, over‑bundled and prematurely timed.
What to focus on instead in 2026
Move E3 → E5 deliberately
Plan a structured, value‑led programme, not just a licence switch.
Add Copilot
Run small, measured pilots with clear metrics. The aim is to prove or disprove value, not merely to “experiment with AI”.
Stabilise identity and conditional access
Tighten Entra hygiene, remove exceptions and move towards identity-driven access.
Start your agent governance small
Use Agent 365 standalone at 15 USD per user for a limited group. Define discovery, approval, monitoring and retirement processes before considering broader use.
When a small E7 pilot makes sense
It is easy to be cynical about the commercial cost of M365 licensing but for certain organisations it absolutely makes sense to be early adopters of E7. But ask yourself:
Are you genuinely ready?
Is your estate already on E5 with mature identity, consistent Conditional Access and strong Teams adoption? If not, stop here
Do you have real AI use cases?
Are there clear, high‑value agent opportunities in areas like finance, service operations or security?
Are you prepared to invest?
Do you have budget and intent to scale AI consumption across Copilot Studio, Fabric or model usage?
Do you need governance now?
Will you require Agent 365 to control agent behaviour and avoid uncontrolled “shadow agents”?
If the answer is yes across this sequence, a small, targeted E7 pilot may be worth running. Otherwise stay on E5, strengthen your foundations, and treat E7 as a future EA option, not today’s answer
Our Damovo Simple guidance for 2026
- Priority: Make E5 work properly, prove Copilot value, and design identity and AI governance.
- E7: Treat it as an option for later EA cycles, not an automatic next step.
- Pilots: Use limited E7 pilots only to validate economics and governance, not as a broad rollout.
E7 is not the next licensing step. It is the next architectural step. And architecture must always come before licensing.