Why Organisations End Up with Multiple Enterprise Agreements
Multiple Microsoft Enterprise Agreements inside a single organisation are more common than most people admit. They arise from three primary causes: post-merger integration where an acquired entity retains its own Microsoft relationship, divisional or subsidiary structures that historically negotiated independently, and legacy agreements signed before a corporate restructuring brought previously separate legal entities under one parent.
A manufacturing conglomerate with three operational divisions might have three separate EAs — each signed at different times, at different per-seat rates, with different product mixes and renewal dates. A private equity portfolio company that has undergone a roll-up strategy may inherit five or six agreements from acquired businesses, each with a different Microsoft account team, different SAM (Software Asset Management) reporting obligations, and completely different licence true-up dates. The administrative overhead is substantial; the commercial inefficiency is worse.
The instinct to consolidate is correct in most cases. But the mechanics matter enormously. Handled poorly, a consolidation can lock you into unfavourable terms at scale, eliminate product flexibility you currently have across separate agreements, or trigger a commercial reset that Microsoft uses to push an E5 upgrade you had previously resisted. This guide covers the process, the leverage, and the traps.
When Consolidation Makes Commercial Sense
Consolidation delivers a genuine commercial benefit when two conditions are met simultaneously: the combined user count across all agreements would qualify for a higher Microsoft volume discount tier than any individual agreement achieves alone, and the product mix across agreements is sufficiently similar that a consolidated structure does not force you to purchase products that only a subset of users actually need.
Microsoft's enterprise discount tiers operate on total enrolled user count. An organisation with two EAs of 800 users each sits in the 500–999 tier on both agreements. Consolidated to 1,600 users, it enters the 1,000–1,999 tier — a price reduction of roughly 6–12% on standard SKUs depending on product mix. At higher volumes the tier jumps are more dramatic. Two 2,500-user agreements sit below the 5,000-user threshold; combined, they cross into pricing territory that is meaningfully better.
Consolidation is less compelling when the product mixes diverge significantly. If one entity is standardised on M365 E3 and a second entity acquired through M&A is on a legacy Office 365 E1 arrangement with a different suite of add-ons, forcing a single product structure creates under-licensing risk in one population and over-licensing cost in another. In these cases, a phased approach — harmonising to a common product set over 12–18 months before renegotiating on a single agreement — produces better outcomes than an immediate merge. See the EA negotiation complete guide for how to sequence these discussions with Microsoft.
The Mechanics of EA Consolidation
Microsoft facilitates EA consolidation through what they internally call an "EA amendment" or "master agreement update." The process involves your Microsoft account team, your reseller channel (Large Account Reseller or direct), and potentially Microsoft's Volume Licensing Service Centre (VLSC) administrative team. The sequence is as follows:
Step 1: Conduct a Full Licence Inventory Across All Agreements
Before approaching Microsoft, you need a consolidated view of every product, quantity, Software Assurance status, and renewal date across all existing EAs. Pull the current enrolment details from VLSC for each agreement. Map every product line against actual deployment data — what is deployed, what is in use, what is shelfware. This inventory becomes the baseline for your consolidated proposal and your primary evidence for renegotiating quantities downward where over-licensing exists.
This step is consistently underestimated. Organisations that rush it go into consolidation discussions with inflated licence counts, which Microsoft treats as the starting point for the new agreement. The EA renewal preparation guide covers the inventory methodology in detail.
Step 2: Identify the Anchor Agreement
When consolidating, one existing EA typically becomes the "anchor" into which others are merged. The anchor agreement should be the one with the most favourable base terms, the earliest renewal date (so you are not locked into a long wait to renegotiate), or — if renewal dates can be aligned — the agreement with the most advantageous committed user count. The anchor agreement's terms form the contractual foundation of the consolidated structure.
If the anchor agreement has a renewal coming within 12 months, consolidation timing works in your favour: you negotiate the combined deal at renewal, using the combined volume as negotiating leverage without being forced to absorb an immediate cost increase. See the EA renewal timeline guide for how to sequence this.
Step 3: Co-Term Non-Anchor Agreements
The non-anchor agreements need to be co-terminated — their end dates aligned with the anchor agreement's renewal date. Microsoft charges a pro-rata uplift to extend shorter agreements to the anchor renewal date, and applies a pro-rata credit for the unused term of any agreement that terminates early. This co-terming calculation is a frequent source of disputes and errors; always request a written calculation from your LAR before signing any amendment. The EA co-terming guide covers the arithmetic and the common errors in detail.
Step 4: Negotiate the Consolidated Commercial Terms
Once the structure is agreed, the commercial negotiation begins. Your leverage at this stage is the combined volume you are now committing at a single point, the competitive alternatives you have evaluated, and the fact that Microsoft's account team has an internal incentive to consolidate the account — simplified management, reduced churn risk, and a single renewal event they control. Use all three explicitly.
Key terms to negotiate include: the effective per-seat price at the combined volume tier, the true-up mechanism (annual vs. anniversary; see the true-up methodology guide), step-down rights if user counts decrease, and pricing protection for the full three-year term. Microsoft will often propose a three-year price lock on specific products as a concession during consolidation — accept it only on products where your deployment is stable and unlikely to be displaced by a competing solution.
Consolidation Traps to Avoid
Microsoft's account teams are skilled at turning consolidation discussions to their advantage. The most common commercial traps encountered across our 500+ engagements are:
The Forced E5 Upgrade
Microsoft will often present consolidation as an opportunity to "standardise the estate" on a single product tier — and that tier will almost always be M365 E5 or an E5-equivalent bundle. The economics rarely support this. If your current estate includes a mix of E3, E1, and standalone licences with specialised add-ons, a single-SKU E5 consolidation will cost significantly more and include entitlements most of your user base will never activate. Insist on a per-user product analysis before accepting any proposed unified SKU. The E3 vs E5 cost comparison provides the financial model for this evaluation.
The Legacy Rate Reset
Some organisations maintain favourable per-seat rates on older agreements that were negotiated before Microsoft's price list increases. Consolidation into a new agreement resets these rates to current list pricing, minus the new volume discount. If your legacy agreement contains embedded pricing below current list price for a product you depend on, model the consolidated price carefully. It is sometimes better to maintain a legacy agreement in parallel for a specific product subset than to consolidate everything and lose a historical pricing advantage.
Ignoring Existing Software Assurance Benefits
When agreements are merged, Software Assurance benefit balances can be reset, lost, or improperly transferred. Before any consolidation is finalised, extract a full SA benefits statement from VLSC for every agreement — including Planning Services days, Training Vouchers, License Mobility rights, and Step-Up entitlements. Document every balance in writing. The Software Assurance guide explains which benefits transfer automatically and which require explicit documentation in the amendment.
Consolidating During an Active True-Up Period
If one or more agreements are mid-cycle with an active true-up pending, consolidating during this period can create ambiguity about how the true-up is calculated — whether it is assessed against the pre-consolidation agreement terms or the new consolidated terms. Microsoft's standard position is that the true-up is calculated on whichever terms are commercially advantageous to them. Pin down in writing exactly which price list and agreement terms govern any in-flight true-up before the consolidation amendment is signed. The true-up negotiation leverage guide covers how to protect your position.
Post-M&A Integration: A Realistic Timeline
When consolidation follows a merger or acquisition, the commercial reality is that immediate consolidation is rarely possible or advisable. Microsoft requires evidence of corporate integration before it will permit agreement mergers — legal entity consolidation, shared domain structures, and in some cases evidence of consolidated financial reporting. The process typically runs on this timeline:
| Phase | Timeframe | Activity | Commercial Impact |
|---|---|---|---|
| Immediate post-close | 0–3 months | Notify Microsoft of ownership change; confirm reseller relationships | No commercial benefit yet; avoid commitment changes |
| Integration planning | 3–9 months | Full licence inventory; harmonise product mix; identify consolidation target | Cost neutral; laying groundwork for negotiation |
| Co-terming and alignment | 9–18 months | Align renewal dates; prepare consolidated commercial position | Some administrative simplification |
| Consolidation negotiation | 18–30 months | Renegotiate consolidated EA at combined volume; optimise product mix | Full pricing benefit realised |
| Steady state | 30+ months | Single agreement; annual true-up management; next renewal planning | Maximum efficiency and leverage |
Organisations that attempt to accelerate this timeline — typically under pressure from CFOs seeking immediate synergies — often create commercial problems that take years to unwind. The leverage is at the consolidation negotiation stage; rushing to that stage before the inventory and harmonisation work is complete produces agreements that look consolidated on the surface but contain structural problems that surface at the next true-up.
When Not to Consolidate
Consolidation is not always the right answer. Specific scenarios where maintaining separate agreements is commercially superior include: where one entity has negotiated future pricing commitments or MACCs that are more favourable than current market rates; where a subsidiary is being prepared for divestiture (consolidating it into a parent EA creates contractual complications when the entity is sold); where geographic or regulatory separation requires distinct data residency commitments that a single global EA cannot accommodate; and where separate entities have genuinely different compliance obligations that necessitate different product configurations.
The EA consolidation decision framework provides a structured analysis for evaluating whether consolidation is appropriate for your specific circumstances.
Microsoft account teams almost universally advocate for consolidation because it creates a larger, simpler account for them to manage and a single renewal event they control. That does not mean consolidation is wrong — but it does mean you should validate the economics independently before accepting their consolidation proposal at face value. We have reviewed cases where Microsoft's proposed consolidation would have increased total cost by 18% despite the appearance of volume discount benefits.
The Negotiation Strategy for Consolidated Deals
A consolidated EA negotiation differs from a standard renewal in one important respect: you have more leverage, but Microsoft also has more at stake. A consolidation that fails commercially for the customer typically results in aggressive use of competitive alternatives at the next renewal, which Microsoft's account team will be held accountable for. Use this dynamic explicitly in the negotiation.
Prepare a competitive baseline before entering negotiations. Document what it would cost to run the same workloads on alternative platforms — Google Workspace for collaboration, AWS or GCP for cloud infrastructure, and alternative productivity suites. You do not need to intend to switch; you need Microsoft's account team to understand that you have the analysis and the willingness to use it. The competitive pressure guide covers how to frame this without making commitments you do not intend to keep.
For large consolidations — above 3,000 users or above £2M annual contract value — engage Microsoft's senior commercial team, not just the account team. Request a commercial review with the regional sales leader. Consolidated deals of this size have internal approval thresholds that give senior Microsoft commercial leaders discretion to offer concessions that account teams cannot. Our EA negotiation service manages this escalation process on behalf of clients.