E7 is the right SKU for approximately 15–20% of enterprise customers in 2026. The decision turns on five specific factors that procurement teams should answer before evaluating the bundle math. Organisations that match three or more of the five factors should evaluate E7 seriously. Organisations matching one or fewer should default to E5 with selective add-on components and revisit E7 in a subsequent renewal cycle when AI deployment matures.
Why a framework, not a calculation
The pure pricing calculation for E7 versus E5 plus components is straightforward arithmetic. The reason a framework is necessary is that the calculation requires inputs — specifically, the assumed deployment scope of Copilot, Agent 365, and the Entra Suite — that procurement teams routinely overestimate. Microsoft account teams will use aspirational deployment numbers in the bundle math; the framework forces realistic deployment numbers.
The five questions
What percentage of your knowledge worker population will use Microsoft 365 Copilot in 2026 with measurable productivity outcomes? Not aspirational deployment — actual deployment with active monthly usage above 8 hours per user. 70%+: E7 is a serious candidate. 30–70%: conditional on other factors. Under 30%: E5 + selective Copilot is better.
Are you actively building AI agents through Copilot Studio at scale? “At scale” means multiple business units, multiple deployment scenarios, and a defensible plan for production agents requiring governance controls. Yes with defined roadmap: E7 attractive. Exploring or piloting: conditional. No active agent programme: Agent 365 component is notional today.
Do you operate or are you actively implementing a Zero Trust architecture using Entra ID Governance, Internet Access, and Private Access? Mature deployment: Entra Suite component is genuinely valuable. Partial: depends on roadmap. None or basic Entra ID P1 only: Entra Suite is partial value at best.
What percentage of your user population is on E5 today? 60%+: E7 migration is structurally clean. 30–60%: cross-over math is complex because some users would be over-licensed under E7. Under 30%: E7 is the wrong shape entirely — E5 + selective add-ons is the right architecture.
Are you comfortable committing three years to the E7 architecture? E7 economics are most attractive on three-year commitments during the promotional window. Shorter commitment or hesitation about the AI components argues for waiting. Three-year commitment ready: act in the promotional window. Hesitation: stay on E5 and reassess.
Scoring the framework
The framework produces three answers: E7 fit, E7 not fit, or model individually. Scoring:
- Three or more “positive” answers (Question 1 ≥ 70%, Question 2 yes with roadmap, Question 3 mature, Question 4 60%+, Question 5 ready): E7 is a serious candidate. Run detailed bundle math and engage Microsoft on promotional pricing.
- Two positive answers: Model individually. The decision is conditional on the specific combination.
- One or zero positive answers: Default to E5 + selective add-ons. Revisit in next renewal cycle.
Profile fit by organisation type
Strong fit: AI-first enterprises and identity-mature security buyers
Organisations in regulated industries with strong security and compliance investments who are also broadly deploying Copilot tend to match three or more positive answers. Examples in our portfolio: a global investment bank deploying Copilot universally with mature Zero Trust; a multinational pharmaceutical with universal E5 and an active agent programme; a defence contractor with full Entra Suite deployment and broad Copilot rollout. For these organisations, E7 promotional pricing is clearly the right answer.
Conditional fit: large enterprises with selective AI deployment
Organisations with broad E5 deployment and mature identity programmes but selective Copilot adoption typically match two positive answers. The decision turns on Copilot trajectory: if the deployment is growing toward 70%+ over the term of the EA, E7 makes sense. If deployment is steady at 30–40%, E5 + selective Copilot is better.
Poor fit: mid-market and AI-conservative enterprises
Organisations below 2,000 seats, organisations on basic Entra ID P1, and organisations skeptical of broad Copilot ROI typically match zero or one positive answer. For this cohort, E7 commits substantial capital to capability that will not be used. The right architecture is E5 base with future option to expand — or in many mid-market cases, Business Premium with selective add-ons.
What to do if you are uncertain
For organisations matching exactly two positive framework answers, the cross-over math depends on which two. Three common patterns:
- Strong Copilot + strong Entra Suite, weak Agent 365 + weak E5 share: Consider hybrid contract with E7 for the strong-fit users and E5 for the rest.
- Strong E5 share + strong commitment horizon, weak Copilot + weak Agent 365: Lock in E5 with pre-negotiated expansion rights to E7 in year 2 or 3 of the term if Copilot deployment grows as planned.
- Strong Agent 365 + strong Entra Suite, weak Copilot + weak E5 share: Modular architecture with E3 or E5 base + Agent 365 + Entra Suite as add-ons. This is often cheaper than E7 because it avoids paying for Copilot across users who won’t use it.
Action plan
- Run the five-question framework this week. Document the answers with specific data, not aspiration.
- Score and classify. Strong fit, conditional, or default to E5.
- If strong fit, accelerate to promotional window. 10–15% promotional pricing through 31 December 2026.
- If conditional or default, model E5 + selective add-ons. Most organisations save substantial money on this path.
- Engage independent advisory. The E7 decision is genuinely material and the framework benefits from external pressure-testing. Book a scoping call.