Microsoft is accelerating the transition from traditional Enterprise Agreements to the Microsoft Customer Agreement as part of its New Commerce Experience. For enterprises, this shift fundamentally changes how Microsoft licensing is purchased, priced, managed, and negotiated. The MCA introduces evergreen subscription terms, eliminates multi-year price locks, removes automatic volume discount tiers, and standardises contract language that Microsoft can update unilaterally. This guide explains what the MCA is, how it compares to EAs and CSP, why Microsoft is pushing it, what enterprises gain and lose, and how to preserve negotiation leverage, pricing protections, and cost control in the new licensing landscape.
This advisory is part of the Microsoft Licensing Knowledge Hub. See also: EA vs CSP: Complete Guide, Mixing EA and CSP, EA to MCA/CSP Transition Checklist, and EA Negotiation Strategies.
Microsoft's push towards the MCA is not primarily about reducing licensing complexity for customers. It is about restructuring the commercial relationship in Microsoft's favour. Under traditional Enterprise Agreements, customers had three powerful levers: a fixed three-year term that created a renewal event where competitive alternatives could be evaluated, volume-based pricing tiers that rewarded commitment with significant discounts, and negotiable contract terms that allowed enterprises to secure custom protections.
The MCA eliminates or substantially weakens all three. The evergreen structure removes the renewal event, so Microsoft never faces the pressure of a customer walking away en masse. The absence of automatic volume tiers means discounts must be negotiated individually. And the standardised contract language means Microsoft controls the terms and can update them with notice.
Evergreen subscriptions create continuous billing without the revenue disruption of three-year renewal cycles. Microsoft no longer faces the risk that customers will use EA renewal as an opportunity to reduce commitments, negotiate deep discounts, or evaluate competitive alternatives. The subscription model smooths revenue recognition and reduces Microsoft's sales cycle costs.
Increased customer lock-in: Without a natural renewal event, there is no obvious moment for enterprises to reassess their Microsoft investment holistically. Under an EA, the three-year renewal was the trigger for competitive evaluations, usage audits, and negotiation preparation. Under MCA, the customer must create these moments artificially.
Annual price increase exposure: Microsoft regularly adjusts cloud service pricing. Under an EA, customers were insulated from price increases for three years. Under MCA, price increases apply at the next subscription renewal, typically annually. Microsoft's March 2022 M365 price increase (15 to 25% across SKUs) demonstrated the impact: EA customers with locked pricing were unaffected, while MCA/CSP customers faced immediate cost increases. Over three years, compounding annual increases can add 15 to 30% to total cost versus a price-locked EA.
Reduced reseller dependency: MCA-E is a direct Microsoft relationship, eliminating the licensing solution partner (LSP) that typically intermediated EA transactions. While some enterprises prefer direct engagement, others lose the added advocacy, support, and market intelligence that a strong LSP partner provided during EA negotiations.
The MCA is a standardised contract framework for purchasing Microsoft cloud services and software on a flexible, subscription basis. Unlike an EA's fixed three-year term, the MCA is an evergreen agreement signed once (typically via digital acceptance) and remaining in effect until either party terminates it. Microsoft can update the standard contract terms with notice, making it a living document that evolves at Microsoft's discretion.
The enterprise-focused variant, MCA-E (Microsoft Customer Agreement, Enterprise), is tailored for organisations that would traditionally have used Enterprise Agreements. Under MCA-E, the enterprise deals directly with Microsoft rather than through a reseller. Subscriptions can be mixed and matched (M365, Azure, Dynamics 365, Power Platform, Copilot) and paid monthly or annually, with no requirement for a company-wide commitment or upfront purchase of a fixed number of licences.
Evergreen subscription model: The MCA has no end date. You sign once and subscribe to services on an ongoing basis. Subscriptions can be added, removed, or modified at monthly or annual intervals. There is no three-year cycle, no big renewal event, and no annual true-up. Instead, compliance is continuous. Every deployed licence must be purchased at the point of deployment. This demands active, ongoing licence management rather than the annual reconciliation that characterised EA true-ups.
List-price default without volume tiers: MCA pricing defaults to Microsoft's retail rates (MSRP). There are no automatic volume discount tiers (the Level A through Level D structure that EAs used). Any discounts under MCA must be individually negotiated, typically through Azure consumption commitments, Copilot adoption incentives, or ad hoc pricing concessions from Microsoft's account team. Without proactive negotiation, MCA customers pay significantly more per user than their EA-equivalent pricing.
Standardised, non-negotiable language: The MCA is Microsoft's standard contract. Unlike EAs, where enterprises could negotiate custom amendments for data residency, price protection caps, audit provisions, and service level enhancements, the MCA's legal terms are Microsoft's boilerplate. Microsoft generally will not alter them for individual customers. Negotiation under MCA focuses primarily on pricing and commercial incentives rather than contract language.
The transition from EA to MCA represents a fundamental shift in how enterprises purchase, manage, and negotiate Microsoft technology. Understanding the specific differences is essential for any enterprise evaluating or being pushed towards MCA.
| Dimension | Enterprise Agreement (EA) | MCA / MCA-E | CSP |
|---|---|---|---|
| Contract term | 3-year fixed term | Evergreen (no end date) | Evergreen via partner |
| Pricing model | Volume tiers (Level A to D), 3-year price lock | List price default, no automatic tiers | List price + partner margin |
| Discounts | Automatic volume discounts, negotiable | Must be individually negotiated | Partner-dependent, usually small |
| Price protection | Locked for 3 years | Exposed to annual increases | Exposed to annual increases |
| True-up | Annual reconciliation | None: continuous compliance | None: continuous |
| Contract terms | Negotiable custom amendments | Standardised, non-negotiable | Standard Microsoft + partner terms |
| On-premises coverage | Yes, with Software Assurance | Cloud-only (no SA) | Limited perpetual, no SA |
| Billing | Annual (or upfront) | Monthly or annual | Monthly or annual |
| Minimum seats | 500+ (rising to 2,400+) | No minimum | No minimum |
| Relationship | Via LSP partner (Microsoft indirect) | Direct with Microsoft (MCA-E) | Via CSP partner |
EA gives you price protection, volume discounts, and negotiable contract terms in exchange for a fixed three-year commitment. MCA gives you subscription flexibility and rapid service adoption in exchange for list-price exposure, no automatic discounts, and non-negotiable contract language. The question is not which is universally better. The question is which trade-off aligns with your organisation's financial planning, workforce stability, and negotiation capacity. For full comparison details, see our EA vs CSP guide.
The MCA is not without merit. For certain enterprise profiles, particularly cloud-first organisations with variable workforces, rapid growth, or minimal on-premises requirements, the subscription flexibility can deliver genuine operational and financial benefits.
Month-to-month licence flexibility: MCA allows scaling licences up or down at monthly or annual intervals without waiting for an EA true-up or mid-term amendment. For companies with seasonal workforces, project-based hiring, or rapid M&A integration, this flexibility eliminates the shelfware that accumulates under EAs when headcount decreases during the fixed term.
Rapid service adoption: When Microsoft launches new services (Copilot, new Azure capabilities, Power Platform features), MCA customers can adopt them immediately by adding subscriptions. No EA amendment, reseller order form, or renewal window is required. For organisations that need to move quickly on emerging technology, this frictionless adoption can provide competitive advantage. See our Copilot licensing guide for the AI implications.
Unified billing and visibility: MCA consolidates all Microsoft subscriptions (M365, Azure, Dynamics 365, Power Platform, Copilot) into a single billing portal with cost centre allocation, department-level breakdowns, and subscription management capabilities. For organisations that previously managed purchases across EA, MPSA, CSP, and direct purchases, this consolidation provides clearer spending visibility.
OpEx-friendly billing model: Monthly billing aligns Microsoft costs with operational expenditure models rather than the large annual or upfront payments that characterised EAs. However, this flexibility comes at a premium. Monthly M365 subscriptions cost approximately 20% more than annual commitments.
The risks of MCA are substantial and, in many cases, more financially significant than the benefits. Enterprises that transition from EA to MCA without a comprehensive mitigation strategy typically experience cost increases of 20 to 30% over the equivalent EA term.
| Risk | Impact | Mitigation |
|---|---|---|
| Loss of volume discount tiers | 15 to 25% higher per-user cost versus EA Level C/D pricing | Negotiate pricing addenda with committed seat counts or Azure consumption commitments |
| Annual price increase exposure | 15 to 30% cumulative increase over 3 years versus EA price lock | Secure multi-year pricing addenda with escalation caps (2 to 5% max annual increase) |
| Loss of negotiation leverage | No natural renewal event to trigger competitive pricing discussions | Create artificial renewal events by consolidating subscription renewal dates |
| Immediate compliance obligations | No true-up reconciliation window; non-compliance risk during M&A or rapid growth | Implement continuous licence management and centralised procurement governance |
| No Software Assurance | Loss of SA benefits: version upgrades, hybrid use rights, training credits, planning services | Maintain separate MPSA or SCE for on-premises requirements; evaluate hybrid EA/MCA |
| Non-negotiable contract terms | Cannot secure custom data residency, audit, or price cap protections | Negotiate commercial amendments where possible; document compliance gaps for regulators |
| Incremental cost creep | Uncontrolled subscription provisioning: 25 to 35% spend increase within 18 months | Centralised procurement approval, mandatory cost centre tagging, quarterly optimisation reviews |
One enterprise we advised saw its annual Microsoft spend increase 35% within 18 months of transitioning to MCA. Not because of genuine business growth, but because the frictionless subscription model enabled uncontrolled provisioning across departments. The ease of adding subscriptions under MCA is a benefit only if your organisation has the governance to control it. Without governance, it is the fastest route to budget overrun. See our M365 cost per user 2026 analysis for current pricing benchmarks.
Microsoft's strategy for phasing out EAs is proceeding in stages, with the clearest impact felt by mid-market enterprises.
EAs below 2,400 seats being phased out (now): Microsoft has announced that Enterprise Agreements with fewer than approximately 2,400 users (the traditional Level A threshold) will not be renewed when their current term expires. These organisations are directed to MCA-E or CSP. If your EA is below this threshold and approaching renewal, you must prepare for transition. This affects thousands of mid-market enterprises globally.
Cloud-only EAs targeted for migration (next): Even above the 2,400-seat threshold, Microsoft is steering enterprises whose EAs contain only cloud subscriptions (no on-premises SA components) towards MCA-E. The argument is that these customers are already cloud-first and would benefit from MCA's flexibility. In practice, this removes the EA's three-year price lock and volume discount protections for organisations that still benefit from them financially.
EA becomes niche for largest enterprises (future): By the late 2020s, EAs are expected to become a niche instrument for the very largest enterprises (10,000+ users) and those with significant on-premises requirements. The trajectory is clear: Microsoft wants MCA-E as the standard commercial vehicle for the majority of enterprise customers. Enterprises that value EA's structural protections should begin developing MCA-equivalent safeguards now.
If your EA renews within the next 18 months and you are below 2,400 seats, Microsoft will direct you to MCA-E or CSP. Begin your transition analysis immediately: inventory all licences, quantify your EA pricing advantage, evaluate hybrid structures, and engage independent advisory to negotiate pricing protections before you lose the EA's structural leverage. The worst outcome is being forced onto MCA at list price because you ran out of time.
The transition to MCA does not mean enterprises must accept list pricing, annual price increases, and the loss of negotiation leverage. It means the negotiation must be structured differently.
Since MCA eliminates the natural EA renewal trigger, enterprises must create their own negotiation moments. Consolidate subscription renewal dates so that a critical mass of licences comes up for annual renewal simultaneously. This recreates the "all-or-nothing" dynamic that gave EA renewals their negotiation power. Communicate to Microsoft's account team, well in advance, that pricing, terms, and scope will be evaluated competitively.
While the MCA itself is evergreen, enterprises can negotiate supplemental pricing agreements (sometimes called pricing addenda or commercial amendments) that lock in per-unit prices for defined periods. These addenda sit alongside the MCA and commit Microsoft to specific pricing for 12, 24, or 36 months in exchange for volume or growth commitments. This recreates some of the EA's price-lock protection within the MCA framework. See our key leverage points guide for detailed tactics.
Under MCA, Azure consumption commitments (MACC) are the primary mechanism for securing meaningful discounts. By committing to a defined Azure spend level, enterprises can negotiate percentage discounts that apply across Azure services and potentially extend to M365 and Dynamics 365 subscriptions. The key is sizing the MACC to genuine consumption (not overcommitting) and ensuring the discount extends to the broadest possible product scope. See our MACC guide for Azure-specific strategies.
The absence of a renewal event makes competitive leverage even more important. Enterprises should maintain genuine, documented evaluations of Google Workspace, AWS, and other alternatives. The most effective leverage comes from actually running pilot deployments on alternative platforms so that Microsoft's account team understands the competitive threat is real. Competitive positioning is the single strongest lever for achieving non-standard MCA pricing concessions.
MCA's subscription flexibility demands permanent financial governance: centralised procurement approval for all Microsoft subscription additions, mandatory cost centre tagging, monthly spend reviews by business unit, and quarterly optimisation assessments. Assign a dedicated Microsoft licence manager (internal or through independent advisory) with authority to approve, deny, and optimise subscription changes.
For enterprises above the EA threshold that still have on-premises requirements, a hybrid approach may deliver the best outcome: an EA covering on-premises licences with Software Assurance, combined with MCA for cloud subscriptions where flexibility is genuinely needed. This preserves EA's volume pricing and price protection for the stable core while allowing MCA's flexibility for variable cloud workloads. The hybrid structure can deliver 10 to 20% better financial outcomes than a pure MCA transition. For the detailed comparison, see our Mixing EA and CSP guide.
Whether you are being directed to MCA because your EA falls below the 2,400-seat threshold, or you are proactively evaluating MCA for its flexibility benefits, the following preparation steps protect your organisation's financial and operational interests during the transition.
| Step | Action | Why It Matters |
|---|---|---|
| 1. Complete licence inventory | Audit every Microsoft licence, subscription, and entitlement across EA, MPSA, CSP, and direct purchases. Map each licence to its user, usage level, and business requirement. | Foundation for identifying waste before transition and establishing your genuine licensing baseline under MCA |
| 2. Quantify EA pricing advantage | Calculate the per-unit discount your current EA provides versus MCA list pricing for every product. Aggregate the total annual cost difference. | Establishes the financial risk of MCA transition and provides data to negotiate pricing addenda preserving EA-equivalent rates |
| 3. Document on-premises requirements | Identify all on-premises licences covered by SA. Determine which SA benefits you actively use (version upgrades, hybrid use rights, training, planning services). | Determines whether you need hybrid EA/MCA, separate MPSA, or subscription equivalents for on-premises coverage |
| 4. Establish internal governance | Implement centralised procurement approval, mandatory cost centre tagging, monthly spend reporting, and quarterly optimisation reviews before transitioning. | MCA's flexibility without governance creates cost creep. Governance must be in place before the transition, not after |
| 5. Develop competitive alternatives | Begin or expand evaluations of Google Workspace, AWS, and other platforms. Document these evaluations as factual competitive context. | The strongest negotiation lever under MCA is a genuine, demonstrated willingness to use alternative providers |
| 6. Negotiate pricing protections | Before accepting MCA, negotiate a pricing addendum that locks in per-unit rates for 24 to 36 months, establishes price escalation caps, and defines discount tiers. | Once you are on MCA without pricing protections, your leverage to secure them diminishes significantly |
| 7. Engage independent advisory | Engage a vendor-independent advisory firm for market intelligence, benchmarking, negotiation strategy, and specialised licensing expertise. | Microsoft's account team has deep knowledge of your licensing. Independent advisory provides the counterbalance needed for non-standard commercial terms |
The decision between EA and MCA is not one-size-fits-all. The optimal choice depends on the enterprise's size, on-premises requirements, workforce stability, financial planning preferences, and negotiation capacity.
You have 2,400+ users and Microsoft will renew your EA. You have significant on-premises requirements needing Software Assurance. You value three-year price locks and predictable budgeting. You benefit from Level C or Level D volume discounts. You have negotiated custom contract terms (data residency, audit limitations, price caps) that you need to preserve. Your workforce is stable and licence requirements are predictable. See our EA negotiation strategies for maximising your renewal outcome.
You fall below Microsoft's EA threshold and cannot renew. You are cloud-first with no on-premises SA requirements. Your workforce is highly variable (seasonal, project-based, M&A-intensive). You need to adopt new Microsoft services (Copilot, Azure AI) rapidly. You have the internal governance to control subscription spend. You are prepared to negotiate pricing addenda to mitigate list-price exposure. See our EA to MCA transition checklist for the step-by-step process.
Consider hybrid EA/MCA if: You have mixed on-premises and cloud requirements. You want EA's price lock and SA benefits for the stable core while using MCA's flexibility for variable cloud workloads. You are above the EA threshold but Microsoft is pushing cloud-only MCA. The hybrid structure preserves the best elements of both commercial vehicles while accommodating the realities of a mixed IT estate.
The shift from EA to MCA is the most significant change to Microsoft's enterprise commercial model in two decades. It removes structural protections that enterprises have relied on since the EA programme launched, and replaces them with a flexible but commercially aggressive subscription model that favours Microsoft in the absence of proactive negotiation.
The enterprises that will navigate this transition successfully are those that treat MCA as a commercial negotiation, not an administrative migration. Every protection the EA provided (price locks, volume discounts, custom terms, renewal leverage) can be approximated under MCA through pricing addenda, MACC commitments, consolidated renewal events, and competitive positioning. But none of these protections are automatic. They must be negotiated deliberately, with data, with market intelligence, and with the understanding that Microsoft's objective is to capture more value per customer, not less.
If your EA is approaching renewal and you are being directed to MCA, start now. Quantify your EA pricing advantage. Build your licence inventory. Establish governance. Develop competitive alternatives. And engage independent advisory to ensure that the transition preserves your commercial position rather than eroding it.
The MCA is a standardised, evergreen contract framework for purchasing Microsoft cloud services. Unlike the three-year fixed-term EA, the MCA has no end date. You sign once and subscribe to services on an ongoing basis. The enterprise variant, MCA-E, is for direct Microsoft relationships replacing the LSP-intermediated EA model.
Not entirely, but Microsoft is phasing out EAs for mid-market enterprises. Organisations with fewer than approximately 2,400 users will not be offered EA renewals when their current term expires. They are being directed to MCA-E or CSP. Larger enterprises (10,000+ users) and those with significant on-premises requirements can still renew EAs, but the long-term trend is towards MCA as the standard commercial vehicle.
By default, yes. MCA does not include automatic volume discount tiers (Level A through D). Without proactive negotiation, MCA customers pay list price, which can be 15 to 25% higher than EA Level C/D pricing. However, enterprises can negotiate pricing addenda, MACC commitments, and multi-year pricing locks that approximate EA-equivalent discounts. The key is negotiating these before signing MCA, not after.
The MCA's legal terms are standardised and generally non-negotiable. Custom amendments for data residency, audit provisions, and SLA enhancements that enterprises negotiated into their EAs cannot typically be replicated under MCA. However, commercial terms (pricing, discounts, escalation caps, reduction rights) can be negotiated through supplemental pricing agreements (addenda) that sit alongside the standard MCA.
MCA is cloud-only. It does not include Software Assurance or on-premises licence coverage. Enterprises with on-premises requirements (Windows Server, SQL Server, System Centre) must maintain a separate MPSA or Server and Cloud Enrolment (SCE) to retain SA benefits. Alternatively, a hybrid EA/MCA structure preserves SA for the stable on-premises core while using MCA for cloud subscriptions.
Six strategies: (1) consolidate subscription renewal dates to create artificial renewal events, (2) negotiate multi-year pricing addenda with escalation caps, (3) use Azure consumption commitments (MACC) as discount leverage, (4) maintain genuine competitive alternatives (Google Workspace, AWS), (5) implement FinOps governance to demonstrate controlled spend, and (6) evaluate hybrid EA/MCA structures to preserve EA protections where they add value.
Now. If your EA renews within the next 18 months and you are below 2,400 seats, Microsoft will direct you to MCA-E. Begin your transition analysis immediately: complete licence inventory, quantify EA pricing advantage, establish internal governance, develop competitive alternatives, and engage independent advisory. Waiting until the last three months before EA expiry leaves insufficient time to negotiate MCA pricing protections effectively.
Our Microsoft advisory team quantifies your EA pricing advantage, negotiates MCA pricing addenda, secures escalation caps and reduction rights, and ensures the transition preserves your commercial position. Independent, fixed-fee, vendor-neutral.
Microsoft Advisory ServicesIndependent Microsoft licensing advisory. Fixed-fee engagement models. 100% vendor-independent.