E3 and E5 set the floor. The add on stack on top, Defender Plans 1 and 2, Purview compliance modules, Power BI Premium per user, Teams Phone, Copilot for M365, Entra ID Governance, decides whether the contract closes at the right total cost of ownership or at a 25 percent premium. The mistake is treating add ons as point purchases. They are part of the same negotiated instrument and they price as a portfolio.
Microsoft sells a deliberately fragmented add on portfolio so that every security, compliance, analytics, and AI conversation in the buyer organization can land on a paid SKU. Knowing the stack is the precondition to choosing it.
The largest add on family by spend. Each module carries E3 and E5 dependencies. Buyers frequently hold overlapping standalone SKUs because the rationalization was not done at attach.
The other four families carry the highest per user prices in the Microsoft estate. They warrant the most disciplined stacking discussion.
The math is straightforward at the per user level and obscured at the portfolio level. The honest comparison requires tiering by role and modeling utilization, not by comparing list prices.
When the user population genuinely needs Defender Plan 2, Defender for Cloud Apps, Purview eDiscovery Premium, Entra ID P2, and Power BI Pro, the E5 bundle is meaningfully below the sum of the standalone SKUs.
When only one or two add ons matter, or when different parts of the user population need different add ons, targeted attach to E3 beats E5 attach across the estate.
Most large enterprises land here. 20 to 40 percent of users on E5 for the security and compliance population. The balance on E3 with targeted Defender and Purview attach. Copilot and Power BI Premium per user layered where role warrants.
Base E3 and E5 SKUs are deliberately constrained at the discount band. Add on SKUs are not. Microsoft sales leadership has materially more authority on the attach lines, especially when they aggregate to a meaningful incremental commit.
Add ons negotiated as separate line items routinely close at five to eight percent above the bundled rate. Aggregating the entire add on stack, including Copilot, Power BI Premium, Teams Phone, Defender Plan 2, and Purview, into a single attached portfolio creates a meaningful commit that the deal desk can compensate against.
The mechanism is straightforward. Microsoft compensation is based on TCV, total contract value, on the deal. Each add on aggregated into the EA grows TCV in a way the comp plan rewards.
For Copilot and other emerging add ons, the buyer should negotiate explicit pilot pricing for the first quarter or first six months at a discount well below the long term rate, with ramped commit growth to full attach by end of year one. This protects the buyer if the pilot reveals lower than expected adoption.
Future use rights matter because Microsoft routinely reorganizes its add on SKUs mid term. Buyers should negotiate language preserving entitlement when SKUs are renamed, repackaged, or moved between bundles, and capping uplift on renamed equivalents at the originally contracted level.
The add on engagement is a portfolio rationalization, a tiering exercise, and a contracting discipline carried into the EA renewal. The output is a contracted add on stack the buyer can defend at every true up cycle without renegotiating the floor.
We map the existing standalone add on SKUs against bundled equivalents inside E3 and E5 and identify the overlap. The rationalization removes overlap, consolidates onto the correct base, and frees the dollars previously spent on duplicated entitlement.
The work surfaces patterns that compound across the contract. Standalone Defender Plan 2 on top of E5. Standalone Entra ID P2 alongside E5. Standalone Power BI Pro on E5 users. Each pattern recovers measurable spend at the next renewal cycle.
The negotiated stack lands in the EA as a portfolio with explicit pre approved add on SKUs, pre negotiated step up and ramp paths, and future product use language covering Microsoft's SKU reorganizations. The contract reads as a portfolio commitment, not as a list of separately priced lines.
The result is a contract where the buyer can expand Copilot, Defender Plan 2, Purview eDiscovery Premium, or Power BI Premium per user during the term at contracted rates rather than at the rate Microsoft would charge at the moment of the order. The expansion conversation becomes operational.
The add on portfolio decision is the most variable line in any modern Microsoft renewal. The tiering, the bundling, and the future use language belong in the months before the quote, not in the weeks after it.