The Microsoft EA additional products list is the contractual category for every SKU inside an EA that is not part of the enterprise-required commitment. Where the enterprise commitment (M365 E3/E5/E7, Office 365 enterprise suites, Core CAL or Enterprise CAL Suite) is the eligibility floor for the EA and is committed for the full term, additional products are the optional layer: server SKUs (Windows Server, SQL Server, System Center), D365, Power Platform, Visual Studio subscriptions, Project, Visio, third-party SKUs in the marketplace, and a growing list of Copilot and AI add-ons. The 2026 negotiation reality is that Microsoft's account team consistently tries to move SKUs from the additional-product layer up into the enterprise-required commitment, where they become harder to rationalise. The buyer-side counter is to keep the additional-product perimeter explicitly drawn and protect it through the EA terms.
Understanding the Microsoft EA additional products category is one of the structural moves that distinguishes a well-negotiated EA from a poorly-negotiated one. The category is not contractually exotic — it is defined in every EA enrollment document — but the implications for renewal flexibility, true-up exposure, and per-SKU rationalisation are real, and most buyers do not work the additional-product perimeter actively enough at signature. Microsoft's account team works it actively from the other direction, and the asymmetry is where additional-product scope creep lives.
Microsoft EA additional products vs enterprise-required
Inside an Enterprise Enrollment, the EA contract distinguishes between two SKU categories. The distinction matters because each category carries different commitment mechanics.
- Enterprise products. The qualifying suite the buyer commits to across all qualifying users or devices at EA signature. The commitment is enterprise-wide: every qualifying user gets the same SKU (or a step-up SKU within the same family). Examples: M365 E3 for the full enterprise; or M365 E5 for the full enterprise; or a base of M365 E3 with a defined sub-population stepped up to E5.
- Additional products. SKUs the buyer adds to the EA above the enterprise commitment. The commitment is per-quantity, not enterprise-wide: a buyer can add 200 Project Online seats or 50 Visio Plan 2 seats without committing all qualifying users to those SKUs. Server SKUs, D365, Power Platform, AI add-ons, and developer tools sit in this layer.
The structural difference matters in three places: at signature (additional products are sized to actual demand; enterprise products are sized to the full qualifying user base), at anniversary true-up (additional products true up annually based on incremental deployment; enterprise products grow with qualifying-user growth and are harder to true down), and at renewal (additional products can be dropped or resized; enterprise products are sticky because they anchor the EA's eligibility).
The 2026 additional-product list
The categorisation below reflects how Microsoft structures additional products in 2026 EA enrollments. SKUs marked "drift candidate" are products Microsoft's account team frequently positions for migration up into the enterprise-required commitment at renewal — the buyer-side counter is to keep them in the additional-product layer where they remain optional.
| Additional-product category | Representative SKUs | Drift candidate? |
|---|---|---|
| Server SKUs | Windows Server Standard / Datacenter, SQL Server Standard / Enterprise, System Center, Exchange Server, SharePoint Server | No — structural additional products |
| Productivity add-ons | Project Online Professional/Premium, Visio Plan 1/2, Microsoft Bookings Premium | No |
| Dynamics 365 | D365 Sales, Customer Service, Field Service, Finance, Supply Chain, HR, Project Operations, Commerce | Selective — Microsoft pushes Sales/Service into broader enterprise commitments at scale |
| Power Platform | Power BI Pro / Premium, Power Apps per-app / per-user, Power Automate per-user / per-flow, Power Pages, Copilot Studio capacity | Yes — Power Platform increasingly positioned into enterprise commit |
| Copilot & AI | Copilot for M365, Copilot for Sales, Copilot for Service, Dragon Copilot, Security Copilot SCU, GitHub Copilot Business / Enterprise | Yes — the largest 2026 drift category |
| Developer tools | Visual Studio Professional / Enterprise (annual or perpetual), GitHub Enterprise Cloud, GitHub Advanced Security | Selective — GitHub increasingly positioned into enterprise commit |
| Security add-ons | Defender for Cloud, Defender for IoT, Sentinel, Entra Suite, Entra ID Governance, External ID, Workload Identities | Yes — the second-largest 2026 drift category as Microsoft consolidates security into E5 / E7 |
| Compliance & governance | Purview standalone modules, Intune standalone, Compliance Manager standalone | Selective — many being pulled into E5 |
| Frontline workers (when not the enterprise commitment) | F1, F3, F5 Frontline suites | No |
| D365 Business Central | BC Essentials / Premium, BC Team Member | No |
| Mixed reality / vertical | D365 Guides, D365 Remote Assist, Mesh, HoloLens-tied SKUs | No |
| Marketplace third-party | Microsoft-resold partner SKUs (ISV, security tools, observability) | No |
Why the additional-product perimeter matters
The structural reason buyers should care about the additional-product perimeter is that the perimeter shapes three downstream renewal options:
- Per-SKU rationalisation. An additional product can be dropped at anniversary or at renewal without affecting the EA. An enterprise-required product cannot — dropping it requires dropping the affected users from the EA entirely, which is structurally disruptive. Keeping Power BI Premium in the additional-product layer means it can be retired at anniversary if usage data shows underutilisation; promoting it into the enterprise commitment locks it in for the EA term.
- True-up exposure. Additional products true up annually on incremental deployment; the true-up bill is bounded by what the buyer actually deployed. Enterprise-required products grow with the qualifying-user base regardless of deployment. The Copilot-for-M365 question, in particular, is where this matters: keeping Copilot as an additional product means deployment can be paced; promoting Copilot into enterprise-required commits all qualifying users at signature.
- Step-up flexibility. Step-up SKUs (the contractual mechanism for moving a subset of enterprise users from E3 to E5, or E5 to E7) work cleanly within the additional-product framework. Once a SKU is enterprise-required, the step-up mechanics are constrained.
The Microsoft account-team drift tactics
Microsoft's account team has consistent tactics for moving SKUs from the additional-product layer into the enterprise-required commitment. The tactics are not adversarial individually; in aggregate they represent a meaningful TCV impact across the EA term.
- The "enterprise-class" framing. Microsoft positions certain additional products as "enterprise-grade" and pressures the buyer to commit enterprise-wide for governance or security consistency reasons. Power BI Premium and the Defender / Purview stack are the most common 2026 examples.
- The bundling argument. Microsoft offers attractive per-seat pricing on an additional product conditional on enterprise-wide commitment. The pricing is real, but the structural cost (the SKU is now sticky for the EA term) typically exceeds the per-seat savings on aggregate.
- The compliance argument. Microsoft positions certain security or compliance additional products as required for the buyer's regulatory posture. The argument is sometimes correct (regulated industries with specific E5 Compliance dependencies) but often used opportunistically.
- The roadmap argument. Microsoft positions an additional product as a leading indicator of future enterprise-required commitment ("everyone will need this in 18 months; commit now at favourable pricing"). The 2026 Copilot drift sits here.
The single highest-leverage drift counter is to insist the EA contract explicitly enumerates the enterprise-required commitment list as a numbered, finite set in the EA documentation. Microsoft's first-proposal EA often leaves the enterprise-required scope ambiguous on certain SKUs (typically Copilot, Power BI Premium, and security add-ons). Explicit enumeration is the buyer-side contractual move.
How to structure the additional-product perimeter at signature
Three negotiation moves preserve additional-product flexibility through the EA term.
- Document the enterprise-required commitment as an exhaustive, named list. The EA enrollment document should list the enterprise-required SKUs by name. Every other SKU is additional. This forces Microsoft to either explicitly include a SKU in the enterprise commitment (where the buyer can negotiate the inclusion) or accept it as additional.
- Use step-up SKUs rather than enterprise-wide promotion for selective upgrades. If 800 of 4,000 users need M365 E5 features, the right structure is a base of M365 E3 (enterprise-required) plus 800 E5 step-up SKUs (additional product). The wrong structure is to commit all 4,000 to E5. The same logic applies to E7 step-ups within an E5 base.
- Reserve the additional-product anniversary true-down right explicitly. The default EA true-up clause language covers incremental deployment; the true-down (reduction in additional-product quantity) is often silent or restrictive. The buyer-side counter is to negotiate explicit anniversary true-down rights for the additional-product layer, capped at a reasonable percentage of the prior-year quantity.
Renewal where additional-product scope is contested?
30-minute scoping call. Additional-product perimeter structuring is a standard advisory track.
Copilot specifically: the highest-stakes 2026 additional-product question
The single highest-stakes additional-product question in 2026 renewals is whether Copilot for M365 sits in the enterprise-required commitment or stays as an additional product. Microsoft's account-team pressure to promote Copilot into enterprise-required is consistent and forceful; the buyer-side counter is to keep Copilot in the additional-product layer until deployment data justifies enterprise-wide promotion.
The case for keeping Copilot as an additional product:
- Copilot adoption realised value is heavily role-dependent. Front-office roles capture meaningfully more value than back-office roles; the role mix decides whether enterprise-wide commitment is economically sensible.
- Copilot SKU economics are still evolving. The 2026 introduction of E7 / Frontier Suite and Agent 365 reshape how Copilot is bundled; an enterprise-required Copilot commit at 2026 EA signature may be poorly structured against the 2027-2028 bundling reality.
- The Copilot Studio 2026 four-mechanism structure creates additional Copilot-adjacent commitments (CCCU, ACU, message-pack, included-message-allowance) that interact with the Copilot M365 commitment. Treating Copilot M365 as additional-product preserves the flexibility to optimise across the four mechanisms over time.
The Copilot ROI calculator linked at the end of this article is the modelling tool our advisory team uses to size the Copilot commitment against role-mix and adoption-ramp assumptions.
The security-stack drift
The second-largest 2026 drift category is the security stack. Microsoft has been consolidating standalone security SKUs into the E5 (and now E7) enterprise commitment for several cycles; the 2026 cycle adds Defender for Office 365 P1 into E3 (the P1 bundling change) and Intune Suite into E5. The implication for EA additional-product structuring is that buyers running standalone Defender / Intune / Purview modules need to decide at renewal whether to consolidate into the enterprise commit or maintain the standalone additional products.
The decision varies by buyer. Buyers with mature E3 baselines and limited E5 footprint typically benefit from the consolidation; buyers with selective E5 footprint and active standalone Defender deployment typically lose flexibility on consolidation. The right answer is buyer-specific and depends on the realised utilisation of the standalone modules versus the bundled equivalents.
The Microsoft Negotiations briefing
Monthly. Buyer-side EA negotiation moves, additional-product scope tactics, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take additional-product structuring next
The additional-product perimeter is one of several scope decisions at EA signature. The companion pages walk the adjacent structural choices: EA online services included vs add-on covers the same question on the M365 services side; the EA negotiation pillar guide covers the full renewal cadence; the EA negotiation service is the engagement path for buyers in active renewal. For buyers approaching renewal where additional-product scope is open, the free EA assessment is the entry point.