The MCA is the contract Microsoft wants every customer on. Three flavours. Three buyer side routes. Read the framework, the EA to MCA migration math, and the levers that beat the default quote.
The Microsoft Customer Agreement is Microsoft's modern commercial framework. The MCA is replacing the Enterprise Agreement, the MPSA, and the older online subscription agreements. The buyer side question for 2026 is not whether to move to MCA but which MCA flavour fits the estate and on what route.
This piece reads as a buyer side framework. Pair it with the EA negotiation guide, the MCA transition landing piece, and the EA vs MCA Enterprise comparison before the next renewal cycle opens with Microsoft.
Microsoft is steering every commercial conversation toward the MCA. EA buyers face renewal envelopes that include an MCA migration option. Smaller buyers are already on MCA Online or MCA Partner. The MCA is now the central reference point for any Microsoft commercial decision.
MCA conversations appear at every EA renewal cycle now. They also surface when a buyer adds a new SKU, opens a new region, or onboards a new entity. Microsoft uses each touch point to nudge the buyer toward an MCA agreement.
There are three MCA flavours. Each carries different commercial terms, different billing routes, and different discount mechanics. The flavour choice is the first buyer side decision.
The large enterprise default. Direct billing from Microsoft. Multi year term. Custom pricing through a Microsoft account team. Price protection negotiated as a clause. This is the EA replacement for buyers above the EA threshold.
The smaller customer default. Direct from Microsoft online. Mostly month to month or annual. Catalog price. Limited customization. Used by SMB and by enterprises for incremental add ons.
Billed through a Microsoft Cloud Solution Provider partner. Annual or monthly term. The partner sets the discount and provides commercial wrap. Common route for mid market and for enterprises that want a single throat to choke on the Microsoft estate.
| Element | MCA Enterprise | MCA Online | MCA Partner |
|---|---|---|---|
| Billing party | Microsoft direct | Microsoft direct | CSP partner |
| Term | Multi year | Monthly or annual | Monthly or annual |
| Pricing | Negotiated, account team led | Catalog | Partner negotiated |
| Price protection | Negotiable clause | None | Partner specific |
| Volume credits | EA style commitments supported | Limited | Partner specific |
| Marketplace | Counts toward Azure commit | Available | Partner specific |
| Typical buyer | Large enterprise | SMB and add ons | Mid market and outsourced |
Most large enterprises will land on MCA Enterprise. Some run a hybrid posture with MCA Enterprise on Azure and MCA Partner on Microsoft 365. The buyer side route reads the workload split, the support need, and the partner ecosystem before locking the flavour mix.
The migration math turns on five inputs. The current EA discount, the MCA list price catalog, the MACC commit, the partner margin if going CSP, and the price protection clause. Compare all five before signing.
MCA opens three billing routes. The route shapes the invoice, the support model, and the discount path.
One Microsoft invoice. Microsoft account team owns the commercial relationship. Best for buyers with a strong internal Microsoft estate management team and direct Premier or Unified Support.
One partner invoice. Partner owns the commercial wrap, the support, and often the managed services. Best for buyers that want a single throat to choke and partner level managed services on Azure or Microsoft 365.
Specific to ISV software and SaaS purchased via Marketplace. Counts toward Azure consumption commit on most agreements. Best for routing third party software spend into the Azure envelope.
The MCA opens seven buyer side levers. The first three sit in the agreement structure. The last four sit in the renewal cycle.
The MCA template carries clauses that the EA buyer takes for granted. Read price protection, term, audit, and data residency carefully.
The biggest difference between the EA and the MCA is the price protection. The EA carried a three year price lock by default. The MCA does not. Buyers who do not negotiate price protection see catalog price changes flow through at the next anniversary. Negotiate the clause explicitly.
The eight step checklist below moves the Microsoft estate from the EA renewal envelope to a defensible MCA route. Open it 12 months before the EA anniversary, earlier on multi entity estates.
Microsoft has not officially retired the EA for the largest enterprise buyers. The MCA is the modern path forward and Microsoft routes most new commercial conversations toward MCA Enterprise. EA renewals continue, but the buyer side default is to evaluate the MCA route in parallel with any EA renewal.
Not by default. The EA carried a three year price lock in the standard terms. The MCA does not. Buyers who want a price lock under the MCA negotiate it as an explicit clause for a defined term. Without the clause, list price changes flow through at each subscription anniversary.
Yes. A common pattern places MCA Enterprise on Azure with direct billing and a MACC commit, while Microsoft 365 sits on MCA Partner through a CSP. The CSP brings managed services on Microsoft 365 and a single partner invoice. The split is supported when the partner ecosystem brings managed services value.
Yes. Azure Marketplace operates under all three MCA flavours. On MCA Enterprise, Marketplace spend typically counts toward the Azure consumption commit. On MCA Online and MCA Partner the Marketplace draw rules depend on the agreement and the partner. Get the Marketplace draw treatment in writing before pushing ISV spend through Marketplace at scale.
The estate transitions to subscription terms on the next anniversary. Microsoft continues to service the existing licenses but the buyer loses the EA discount and the price lock. New SKUs go onto MCA Online or MCA Partner by default. Start the MCA conversation 12 months ahead of EA expiry.
The Microsoft Azure Consumption Commitment lets the buyer commit to multi year Azure spend in exchange for a discount. The commit is denominated in dollars or local currency. Marketplace ISV spend counts toward the commit on most MCA Enterprise agreements. Right sizing the MACC against the validated baseline is a central buyer side lever.
Redress runs the MCA decision as a four to six week assessment. The work pulls the EA baseline, scores the workload mix, quotes the MCA flavours and the partner options, and tests the MACC commit against actual Azure consumption. The deliverable is an MCA route recommendation, the negotiation envelope, and the price protection clause checklist.
Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.
A buyer side framework for the Microsoft commercial cycle. EA to MCA migration math, MACC sizing, price protection clause language, and the partner versus direct route assessment used across five hundred plus enterprise software engagements.
Independent. Buyer side. Built for enterprise Microsoft customers running EA renewals, MCA Enterprise migrations, and CSP partner routes in 2026.
Open the white paper in your browser. Corporate email only.
Open the Paper →We mapped every Microsoft workload against the right MCA flavour, split Azure onto MCA Enterprise direct and Microsoft 365 onto MCA Partner, and negotiated a contract term price lock. The combined route reduced the Microsoft envelope by 22 percent across the term.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
EA to MCA migration patterns, MACC commit benchmarks, CSP partner margins, Microsoft 365 tier movement, 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.
