Microsoft is moving large enterprises off the Enterprise Agreement and onto the Microsoft Customer Agreement for Enterprise (MCA-E). The account team will frame the migration as administrative — a paperwork swap with no commercial consequence. It is not. An EA to MCA-E migration quietly drops price locks, resets discount levels, and rewrites the terms that protected you. This 26-page report names the seven concessions you can still negotiate before you sign, and the exact language that keeps your EA-era economics intact.
Written for CIOs, procurement leaders, and general counsel staring at an EA expiry and an account team pushing MCA-E. No spam. Unsubscribe anytime.
Enter your details for immediate access. Your information is never shared or sold.
Joined 2,400+ IT, legal, and procurement professionals who rely on our buyer-side research
Est. 2016 · 500+ engagements · $2.1B managed · 32% avg cost reduction · 100% independent · 100% buyer-side.
A forced migration is not a neutral event. It is a renegotiation that Microsoft would prefer you not treat as one. Each of these seven concessions is achievable in 2026 — but only if you raise it before the new agreement is countersigned, and only with the contractual language that holds.
The EA locked your per-unit pricing for the term. MCA-E pricing is transactional and re-quoted at migration. The single most valuable concession is a written commitment that your current EA unit prices carry forward for a defined period — not Microsoft's prevailing MCA-E rate card. The report gives the clause structure and the duration most achievable in a 2026 migration.
Your EA discount reflects accumulated A/B/C/D level standing earned over years. MCA-E does not inherit it automatically. Without a preservation clause, you start the new agreement at a worse effective discount. How to document your historical level and bind it into the migration terms.
MCA-E removes the EA true-up rhythm and pushes toward upfront or annual commitments. A negotiated ramp lets you phase Copilot, E5, or Azure commitments to actual adoption rather than paying for day-one capacity. The ramp structures Microsoft will accept under MCA-E.
EA annual payments are predictable. MCA-E billing can shift cash forward — monthly arrears, annual prepay, or consumption true-forwards. The payment-cadence concessions that protect working capital, and the language that prevents Microsoft from re-timing invoices mid-term.
EA audit rights are narrow and well-litigated. MCA-E verification language is broader and less tested. Migrating without porting your negotiated audit protections hands Microsoft a wider verification surface. The specific clauses to carry over and the ones to redline.
A migration can fragment your renewal calendar into staggered MCA-E subscription end dates, destroying your single point of negotiating leverage. How to co-terminate the migrated estate so you keep one renewal moment — and the leverage that comes with it.
EA assignment and divestiture rights protect you through M&A. MCA-E defaults are thinner. The transferability, true-down, and exit provisions worth negotiating now, before a future reorganization turns a paperwork gap into a seven-figure problem.
Each is the kind of thing an account team is happy to let you believe. Each is corrected in the report with the contractual basis and the negotiated alternative.
The migration is a fresh transaction priced against the current MCA-E rate card, not your EA economics. Enterprises that accept the "administrative" framing routinely discover their effective discount eroded by 8–15% at the first MCA-E quote, because no carry-forward clause was negotiated before signature.
Leverage exists only before you countersign. Once the estate is on MCA-E, the account team has no mandate to retroactively restore EA-era protections. Every concession in this report is negotiable pre-migration and substantially harder afterward. The window is the gap between EA expiry notice and MCA-E execution.
It matters more than ever. MCA-E subscriptions can land on different anniversary dates, splitting your estate into multiple small renewals Microsoft handles individually. A co-termination anchor preserves the single, large, leverage-rich renewal moment that an EA gave you by default.
This report is written for the team that owns the Microsoft relationship when the EA renewal notice arrives with an MCA-E proposal attached. It assumes you know your estate and want the negotiating positions, not a primer on what MCA-E is.
It reflects Microsoft's commercial posture after the November 2025 removal of programmatic EA volume discounts, the documented push toward MCA-E and CSP, and the migration concession patterns observed across enterprise engagements through the first half of 2026.
Related resources: our EA renewal strategy explainer, the EA to MCA transition advisory service, and the CSP versus EA decision guide.
"Microsoft told us the move to MCA-E was a formality. The first quote came back nearly fifteen percent more expensive on identical SKUs. We paused, negotiated a carry-forward and a level-preservation clause, and landed back on our EA economics — with a co-termination date that keeps all our leverage in one place."
VP IT Procurement, Global Logistics GroupThe migration window is the one moment your EA-era protections are still on the table. Our advisors model the MCA-E quote, expose the erosion, and negotiate the carry-forward, level-preservation, and continuity clauses that keep your economics intact.