When Multiple EAs Become a Problem
Enterprises accumulate multiple Microsoft Enterprise Agreements in predictable ways: through mergers and acquisitions, through divisional autonomy that allowed separate IT procurement, through historical relationships with different Microsoft Large Account Resellers, or through a mix of government and commercial entity structures that required separate agreements. By the time a consolidation question arises, the typical multi-EA environment has two to five active agreements with different terms, different end dates, different product sets, and different pricing tiers.
Microsoft will tell you consolidation is simple and always beneficial. It often benefits Microsoft more than it benefits you. A consolidated EA creates a single, larger commercial relationship — which gives Microsoft more visibility, more leverage at renewal, and a simpler account management structure. None of these are bad outcomes for buyers, but they are not the same as better pricing or better terms. Consolidation delivers genuine commercial benefits under specific conditions. Under other conditions, it creates unnecessary risk and hands Microsoft leverage it did not previously have.
This article maps the decision framework across 500+ engagements. The question is not whether to consolidate in principle — it is whether consolidation delivers a better commercial outcome than managing multiple agreements strategically.
The Commercial Case for Consolidation
The genuine commercial argument for EA consolidation rests on four mechanisms. Each is real. Each is also bounded — it delivers value up to a point, after which the incremental benefit is marginal or negative.
1. Volume Discount Uplift
Microsoft's D-level discounts are tiered by revenue volume within each product category. A consolidated EA with £3M annual spend in M365 will typically command better discounts than two separate EAs at £1.5M each — because the higher tier only unlocks when spend is consolidated against a single agreement. The discount improvement ranges from 3–8% in most commercial scenarios, rising to 10–15% where consolidation moves an account into a strategically important volume band.
The caveat: this benefit only applies to product categories where the consolidated volume meaningfully crosses a tier boundary. Consolidating two mid-size EAs that are both already in the same discount tier produces no volume benefit — Microsoft will not give you a higher discount simply because you have one agreement instead of two if both are already in the same pricing band.
2. Negotiating Complexity Reduction
Managing two or three EA renewal cycles across a 12-month period consumes disproportionate internal resource and creates gaps in negotiating attention. A single renewal cycle, negotiated with full focus and professional support, consistently produces better outcomes than multiple partial-attention cycles. This is an operational argument as much as a commercial one — but operational simplicity that enables better negotiation preparation has real commercial value.
3. Azure MACC Consolidation
Microsoft Azure Monetary Commitments (MACCs) attract discounts that scale with commitment size. Fragmenting Azure consumption across two MACCs loses the volume benefit entirely. For organisations with meaningful Azure consumption — generally £2M+ annually — consolidating Azure commitments into a single MACC is almost always the right decision on pure economic grounds. Our Azure MACC negotiation guide covers how to structure consolidated MACC commitments effectively.
4. Simplified True-Up Management
Annual true-ups across multiple EAs create administrative complexity and increase the risk of compliance gaps. A consolidated true-up process with a single measurement date, single entitlement baseline, and single submission is simpler to manage and less likely to produce the kind of coverage errors that generate audit exposure. For organisations with significant Microsoft estate complexity, simplified true-up management is a meaningful risk-reduction benefit. See our EA true-up clauses guide for the compliance mechanics that consolidation simplifies.
The Risks Microsoft Doesn't Tell You About
For every commercial benefit listed above, there is a structural risk that Microsoft's account teams systematically understate. Before committing to consolidation, these risks require explicit quantification.
Losing Negotiating Optionality
Two separate EA renewals, even in the same calendar year, create two separate negotiating windows. The leverage available in each window — competitive alternatives, fiscal timing, benchmarked pricing — can be applied independently. Consolidation collapses these into a single negotiating event. If that single negotiation goes poorly, there is no second attempt. If Microsoft's commercial position is weak in March (when one EA renews) but strong in June (when the other would have), consolidation forces you into the June scenario.
This is not theoretical. In organisations where one entity has stronger competitive alternatives than another, separating those negotiations allows the stronger position to be applied exclusively where it has the most leverage — rather than being diluted across a consolidated entity where the weaker position sets the tone.
Inheriting Unfavourable Terms from the Legacy Agreement
When multiple EAs consolidate, Microsoft typically proposes to bring all entities onto the terms of a single surviving agreement. If one of your legacy agreements has better contractual terms — favourable audit rights limitations, stronger price protection language, longer notice periods — consolidation risks losing those provisions. The consolidation negotiation should include an explicit comparison of each agreement's non-commercial terms, with the best provisions from any legacy agreement carried forward into the consolidated document.
Co-Terming Forces Premature Renewal
To consolidate two EAs onto a single renewal date, one of them typically needs to be terminated early and rolled into the new consolidated agreement. Depending on where you are in each term, this may create a payment obligation for unused term, or may accelerate a renewal that you are not prepared to negotiate effectively. Microsoft will often offer to "waive" the co-terming cost — but this waiver comes with commercial strings that may be worth more than the cost it appears to save.
Audit Rights and Compliance Scope Expansion
A consolidated EA that covers a larger population and a wider product set creates a correspondingly wider audit scope. If any legacy EA contained favourable audit rights limitations — annual frequency limits, scope restrictions, cost-allocation provisions — verify that these survive consolidation before agreeing to the new agreement structure. Microsoft's audit rights templates are less favourable than the negotiated language in most well-structured existing agreements.
Never consolidate EAs without comparing the contractual terms of each legacy agreement against the proposed consolidated agreement. Beneficial non-commercial terms — price protection, audit rights limitations, notice periods — can be lost in consolidation if not explicitly carried forward.
The Consolidation Decision Framework
Across 500+ engagements, we have distilled the consolidation decision to seven questions. The answers will tell you whether consolidation delivers commercial benefit — and if so, on what terms.
| Decision Question | Consolidate Signal | Maintain Separate Signal |
|---|---|---|
| Does combined volume cross a meaningful discount tier? | Yes — tier threshold crossed | No — same tier either way |
| Are Azure MACC commitments fragmented? | Yes — meaningful Azure spend | No Azure or minimal spend |
| Do legacy agreements have unfavourable contractual terms? | Yes — consolidation upgrades terms | No — legacy terms are better |
| Are renewal dates within 6 months of each other? | Yes — co-terming is low-cost | No — one EA has 18+ months remaining |
| Is one entity in a stronger competitive position? | Same leverage across all entities | Yes — keep strong position separate |
| Are there M&A integration considerations? | Yes — simplification has value | Entities operate independently |
| Is your team resourced for single-window negotiation? | Yes — can concentrate effort | Multiple windows spread risk |
A consolidation that produces three or more "consolidate signals" in the table above is worth pursuing, subject to the conditions in the next section. Two or fewer signals suggests the status quo is commercially superior — or that a coordinated multi-agreement strategy will outperform consolidation without the associated risks.
Post-M&A EA Consolidation: Special Considerations
The most common trigger for EA consolidation is a merger or acquisition. The acquired entity's Microsoft agreement needs to be integrated — but "needs to be integrated" does not mean "should be immediately consolidated." Post-M&A EA management is one of the highest-risk areas in enterprise Microsoft licensing, and the timeline for integration decisions matters significantly.
Three scenarios are common: (1) The acquired entity's EA expires within 12 months of acquisition close — in this case, run a standard renewal negotiation aligned to the acquirer's EA terms and negotiate co-terming at that renewal; (2) The acquired entity's EA has 18+ months remaining — maintain it as a separate agreement until the natural renewal window, then consolidate on terms negotiated at that point; and (3) The acquired entity's EA contains valuable contractual protections — preserve these explicitly rather than defaulting to the acquirer's standard terms.
The worst outcome in post-M&A EA integration is an emergency consolidation under time pressure, with Microsoft aware that integration is required. This scenario creates exactly the kind of deadline leverage that drives poor commercial outcomes. Our M&A licensing guide covers the full timeline and risk framework for post-acquisition Microsoft estate management.
How to Negotiate Consolidation Terms
If your analysis confirms that consolidation creates commercial benefit, the negotiation approach matters as much as the decision itself. Microsoft will treat a consolidation request as a renewal opportunity — and will attempt to price the new consolidated agreement at current standard rates, effectively erasing any favourable pricing from legacy agreements.
Establish the Pricing Baseline Before Announcing Consolidation Intent
Do not signal consolidation intent to your Microsoft account team before you have independently benchmarked the pricing for the consolidated entity. If Microsoft knows you want to consolidate, they know you have a commercial motivation — and they will use that motivation to manage the negotiation toward standard pricing rather than best-in-class pricing. The consolidation intent should be disclosed only after your target pricing is established and your opening position is ready to present.
Use the Combined Spend as an Anchor, Not a Ceiling
When presenting the consolidated deal, open with your analysis of what the combined spend volume should command based on independent pricing benchmarks. The combined volume is your leverage — anchor the conversation there, not on what you currently pay. Many enterprises consolidate and receive discounts calculated as a percentage improvement over their highest-priced legacy agreement — which may still be materially above the market rate for that volume.
Carry Forward the Best Terms from Every Legacy Agreement
Build a term-by-term comparison of all legacy agreements before entering consolidation negotiations. For each non-commercial provision — audit rights, price protection, true-up timing, amendment notice periods — identify the most favourable version across your existing agreements and require it in the consolidated document. If Microsoft's account team claims a provision cannot be carried forward, escalate to the Enterprise Licensing Desk before accepting that answer.
Negotiate the Consolidation as a Strategic Account Designation
A consolidation that brings a customer's total Microsoft spend above certain thresholds (generally £2M+ annually) may qualify for strategic account status — which unlocks executive sponsorship, technical account management, and in some cases, commercial provisions not available through standard field channels. Request an explicit strategic account designation discussion as part of the consolidation negotiation. This is not a concession Microsoft typically offers proactively, but it is achievable when framed as a prerequisite for committing to consolidation. Our complete EA negotiation guide details how strategic account leverage works within Microsoft's internal approval structure.
The Alternative: Coordinated Multi-Agreement Strategy
Consolidation is not the only way to capture the commercial benefits of scale. A coordinated multi-agreement strategy — where separate EAs are negotiated simultaneously or in close sequence with a unified commercial position — can achieve equivalent or better outcomes while preserving the optionality that consolidation eliminates.
The mechanics: treat all your Microsoft agreements as a portfolio. Present Microsoft with a combined view of your spend at every engagement, make clear that all renewal decisions will be made with awareness of cross-agreement terms, and use leverage generated in one negotiation to inform the position in another. When one entity has strong competitive alternatives, make those alternatives visible across the entire portfolio discussion — not just within the single entity negotiation.
This approach requires more coordination but produces consistently better outcomes than uncoordinated single-EA management — and better terms than rushed consolidations that prioritise administrative simplicity over commercial rigour. Contact us to discuss which approach makes sense for your specific multi-agreement situation.