The next Microsoft renewal is a fork. Stay on the Enterprise Agreement, or step onto the Microsoft Customer Agreement. This is the buyer side guide to the decision, the discount math, and the timing.
The Enterprise Agreement and the Microsoft Customer Agreement are the two enterprise vehicles you choose between at a 2026 renewal. The EA is a 36 month commitment with a price lock. The MCA is direct, monthly billed, and flexible. Each carries a different discount, audit, and renewal shape.
This is the renewal framework. Pair it with the EA renewal playbook, the EA renewals guide, and the CSP versus EA comparison.
The fork is the biggest commercial decision on the next Microsoft renewal. Three forces drive the choice: Microsoft strategy, your cash structure, and audit posture. Get the route wrong and the discount work that follows is built on the wrong base.
The decision lives at renewal. Open the analysis 9 to 12 months before the EA anniversary. That window covers a usage baseline, an MCA quote, EA renewal anchoring, and the move decision itself.
An Enterprise Agreement is a 36 month commitment between Microsoft and a customer. You commit to a product set at a level. Microsoft delivers a discount band and a price lock for the term.
The EA wins for large, stable estates with predictable growth. The price lock protects against annual list uplift. The annual true up adds users at the same rate. The negotiated level holds for the full term.
The Microsoft Customer Agreement is a direct, open ended agreement. Subscriptions and consumption attach to it. Billing is monthly. Commitment is optional but unlocks deeper discount levels.
MCA comes in three variants. MCA Enterprise is the direct enterprise contract Microsoft positions as the EA replacement. MCA Online is the click through agreement behind Azure subscriptions. MCA Partner is the partner managed variant. The renewal conversation centers on MCA Enterprise.
The decision framework reads six factors. Each weights the choice toward EA or MCA. The summed weight points to the right route before any price talk begins.
Six factor EA versus MCA framework
| Factor | Weights EA | Weights MCA |
|---|---|---|
| Estate size | 5,000+ stable seats | Variable estate size |
| Growth profile | Predictable, steady | Variable, acquisitive |
| Cash structure | Annual budget | Monthly budget |
| Discount appetite | Deep and locked | Flex with commitment |
| Audit posture | Annual true up fine | Renewal true up preferred |
| Partner role | Strong LSP partner | Direct or alternative partner |
No single factor decides it. Score each toward EA or MCA, then read the balance. A 5,000 seat estate with steady growth and an annual budget points to the EA. An acquisitive estate with monthly budgeting and variable headcount points to the MCA.
EA and MCA produce different mechanics. Compare them apples to apples before deciding. Microsoft publishes 365 plan pricing and Azure pricing as the list baseline both routes discount from.
The standard account team pitch is that moving to MCA at renewal is simpler and modern, so you should just migrate. We disagree. Across the renewals we benchmarked in 2024 to 2025, a default MCA migration without a priced EA renewal beside it cost buyers 6 to 15 percent more on like for like seats, because the price lock and the negotiated level were quietly given up. The buyer side move is to demand both quotes at the same commitment level, in writing, and let Microsoft compete against its own alternative. The route is a negotiating asset, not a foregone conclusion, and treating it as inevitable hands the discount back.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
We modeled both routes at once, anchored Microsoft against a real MCA migration quote, and renewed on the EA at 18 percent below the first number across 12,500 seats.Group VP of IT Procurement · Global enterprise
The checklist below moves the next Microsoft renewal from the incumbent default quote to a buyer side framework.
The EA is not retired in 2026, but Microsoft is steering most customers toward the MCA at renewal. The EA remains available, particularly above 2,400 seats and in regions where MCA Enterprise is less mature. No public retirement date exists. Plan the MCA option, do not assume the EA disappears.
Not by default. MCA list rates run higher than a negotiated EA level discount. MCA becomes cheaper only when paired with Azure prepay and Microsoft 365 commitments that unlock deeper tiers. Model both routes at the same commitment level over 36 months before deciding.
Price protection means the negotiated EA price holds for the 36 month term. Users added at the annual true up come in at the locked price, not the current list price. MCA does not carry automatic price protection, though multi year MCA Enterprise deals can negotiate it.
Yes, and many do during transition. A common pattern keeps Microsoft 365 on the EA for the price lock while Azure consumption moves to the MCA for monthly flexibility. The split also lets a buyer test MCA billing before committing the full estate at the next anniversary.
Under an EA the licensing partner is the contractual seller and adds a margin layer. Under MCA Enterprise the contract is direct with Microsoft, so that margin compresses. Partners still deliver advisory, deployment, and managed services, and the MCA Partner variant keeps a partner of record.
Open the renewal 9 to 12 months before the anniversary. That window covers a usage baseline, an EA renewal quote, an MCA migration quote, and the negotiation itself. Teams that open at 90 days lose the leverage that comes from a credible alternative route.
Across our engagements the well negotiated delta runs 4 to 12 percent in favor of whichever route fits the estate. Stable, predictable estates favor the EA price lock. Variable or acquisitive estates favor MCA flexibility. The seat mix and Azure profile decide the number.
Moving to MCA does not erase prior under licensing. It changes where the true up lands, shifting it to subscription renewal rather than an annual EA true up. Reconcile entitlement against deployment before any migration, because the transition is exactly when Microsoft reviews the estate.
We run the EA versus MCA decision as a 6 to 9 month engagement aligned to the renewal cadence. The work pulls the inventory, scores usage, models both routes, anchors the negotiation, and prepares the red line list. Read Vendor Shield, the Renewal Program, and the Microsoft Knowledge Hub.
A buyer side framework for the Microsoft commercial estate, EA and MCA included. Decision model, discount math, true up posture, price file negotiation, and the red line list used across 500+ enterprise software engagements.
Independent. Buyer side. Built for CIOs and procurement leads renewing the EA, weighing the MCA migration, or building the cadence around the next Microsoft anniversary.
Open the white paper in your browser. Corporate email only.
Open the Paper →
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
EA level discount benchmarks, MCA discount file movement, Azure prepay rates, 365 commitment patterns, and the wider Microsoft commercial leverage signals across every renewal cycle.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
