Microsoft is accelerating the transition from traditional Enterprise Agreements to the Microsoft Customer Agreement (MCA) 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 — critically — how to preserve negotiation leverage, pricing protections, and cost control in the new licensing landscape.
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 for data residency, price caps, and compliance provisions.
The MCA eliminates or substantially weakens all three of these levers. The evergreen structure removes the renewal event, so Microsoft never faces the existential pressure of a customer walking away en masse. The absence of automatic volume tiers means discounts must be negotiated individually for each subscription rather than flowing automatically from committed seat counts. And the standardised, non-negotiable contract language means Microsoft controls the terms and can update them with notice, shifting contractual power to the vendor.
From Microsoft’s perspective, the benefits are compelling. Revenue becomes more predictable with continuous subscription billing rather than lumpy three-year commitments. Customer switching costs increase because there is no natural break point for competitive evaluation. Annual price increases can be applied to the entire MCA customer base simultaneously, rather than being deferred until individual EA renewal dates. And the direct billing relationship under MCA-E reduces reseller margins, improving Microsoft’s profitability per customer.
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.
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 — and without a contractual deadline, internal momentum for competitive evaluation is harder to generate.
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. If Microsoft raises M365 E5 pricing by 5–10%, MCA customers absorb that increase within 12 months, whereas EA customers would not have been affected until their next renewal. Over three years, this exposure can compound to 15–30% above what an EA would have cost.
MCA-E is a direct Microsoft relationship, eliminating the licensing solution partner (LSP) that typically intermediated EA transactions. This reduces Microsoft’s channel costs and gives Microsoft more direct control over the customer relationship. 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 Microsoft Customer Agreement 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. Under MCA, 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.
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 — if you add a user, you must licence them immediately. This demands active, ongoing licence management rather than the annual reconciliation that characterised EA true-ups.
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.
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 — and their financial and operational implications — is essential for any enterprise evaluating or being pushed towards MCA.
| Dimension | Enterprise Agreement (EA) | Microsoft Customer Agreement (MCA/MCA-E) | CSP (Cloud Solution Provider) |
|---|---|---|---|
| Contract term | 3-year fixed term | Evergreen (no end date) | Evergreen via partner |
| Pricing model | Volume tiers (Level A–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 |
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. The key is understanding where MCA’s strengths align with the enterprise’s actual requirements rather than accepting Microsoft’s universal positioning that MCA is better for everyone.
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. Each licence is paid for only when it is needed.
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.
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 Microsoft purchases across EA, MPSA, CSP, and direct purchases, this consolidation provides clearer spending visibility.
Monthly billing aligns Microsoft costs with operational expenditure models rather than the large annual or upfront payments that characterised EAs. For organisations managing cash flow carefully or transitioning to cloud-native financial models, the MCA’s pay-as-you-go approach can improve working capital management. 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–30% over the equivalent EA term, driven by the loss of volume discounts, exposure to annual price increases, and the incremental cost creep that accompanies subscription flexibility without governance.
EA’s Level A through Level D pricing tiers provided automatic discounts based on seat count. A 5,000-user enterprise at Level C might achieve 15–20% below list price automatically. Under MCA, there are no automatic tiers. The same enterprise pays list price by default and must negotiate every discount individually. Without proactive negotiation, MCA customers routinely pay 15–25% more per user than they did under their EA.
Microsoft adjusts cloud pricing annually — typically upward. EA customers were insulated by three-year price locks. MCA customers absorb increases at each subscription renewal. Microsoft’s March 2022 M365 price increase (15–25% across SKUs) demonstrated the impact: EA customers with locked pricing were unaffected, while MCA/CSP customers faced immediate cost increases. Over a three-year period, compounding annual increases can add 15–30% to total cost versus a price-locked EA.
The EA renewal event was the enterprise’s most powerful negotiation lever. The implicit threat — that the customer could reduce scope, switch vendors, or let the EA lapse — created pressure for Microsoft to offer competitive terms. MCA’s evergreen structure eliminates this event. Without a natural negotiation trigger, enterprises must create their own leverage through Azure consumption commitments, competitive evaluations, or deliberate scope consolidation to force meaningful pricing discussions.
EA true-ups provided an annual reconciliation window — if the enterprise deployed additional licences during the year, it paid for them at true-up rather than immediately. MCA requires immediate compliance: every deployed licence must be purchased at the point of deployment. This demands continuous licence management, faster procurement processes, and more disciplined internal governance. The risk of inadvertent non-compliance increases substantially, particularly during M&A integration, reorganisations, or rapid headcount changes.
MCA is cloud-only. Enterprises with on-premises servers, SQL Server, Windows Server, or other perpetual licence requirements must maintain a separate MPSA or Server and Cloud Enrolment (SCE). This fragmentation creates administrative overhead, potential licence gaps, and the loss of SA benefits (version upgrade rights, training credits, planning services days, and hybrid use rights) that EAs bundled into a single agreement.
The MCA is Microsoft’s standard form. Custom amendments for data residency, audit limitations, price escalation caps, service level enhancements, and termination protections that enterprises negotiated into their EAs cannot be replicated under MCA. Microsoft can update MCA terms unilaterally with notice, and the customer’s only recourse is to accept or terminate. For regulated industries (financial services, healthcare, government), the inability to secure custom contractual protections may create compliance challenges.
The ease of adding subscriptions under MCA creates a persistent cost-creep risk. Without the discipline of an EA’s fixed commitment, individual business units and IT teams can add licences, upgrade tiers, or adopt new services without centralised approval. 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.
Microsoft’s strategy for phasing out EAs is proceeding in stages, with the clearest impact felt by mid-market enterprises. Understanding the timeline and thresholds is essential for planning.
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 (direct with Microsoft) or CSP (through a partner). If your EA is below this threshold and approaching renewal, you must prepare for transition — Microsoft will not offer a new EA. This affects thousands of mid-market enterprises globally.
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. Enterprises with cloud-only EAs should evaluate whether their EA pricing advantage justifies insisting on EA renewal.
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 — through negotiated pricing addenda, Azure consumption commitments with discount protections, and multi-year subscription commitments that recreate some of the EA’s price-lock benefits within the MCA framework.
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. The following strategies are designed to recreate EA-equivalent protections within the MCA commercial framework.
Since MCA eliminates the natural EA renewal trigger, enterprises must create their own negotiation moments. The most effective approach is to 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 of the consolidated renewal date, that pricing, terms, and scope will be evaluated competitively. Without this discipline, Microsoft has no commercial incentive to offer improved terms.
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. Microsoft’s willingness to grant pricing addenda depends on the enterprise’s volume, growth trajectory, and competitive positioning — independent advisory significantly improves outcomes.
Under MCA, Azure consumption commitments (Microsoft Azure Consumption Commitment — 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. Azure commitments replace the volume-tier mechanism of EAs as the primary discount lever under MCA.
Under MCA, 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 — not as negotiation bluffs, but as factual competitive context. 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. Without this discipline, the cost creep that MCA enables can offset any negotiated discounts within 12–18 months. 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 (preserving SA benefits and price locks), combined with MCA for cloud subscriptions where flexibility is genuinely needed. This structure preserves EA’s volume pricing and price protection for the stable core while allowing MCA’s flexibility for variable cloud workloads. The hybrid structure is complex to manage but can deliver 10–20% better financial outcomes than a pure MCA transition.
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 checklist will help protect your organisation’s financial and operational interests during the transition.
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.
Stay on EA if: 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.
Consider MCA if: 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.
The shift from EA to MCA is fundamentally a transfer of commercial power from the customer to Microsoft. Independent advisory exists to rebalance this dynamic — providing enterprises with the market intelligence, licensing expertise, and negotiation strategy needed to secure MCA terms that protect their financial and operational interests.
Redress Compliance maintains current benchmarking data on MCA pricing addenda, Azure consumption commitment discounts, and commercial terms achieved by comparable enterprises. This intelligence ensures our clients negotiate with full awareness of what is achievable — not the conservative initial offers that Microsoft presents as their best available terms. The gap between Microsoft’s initial offer and achievable pricing under MCA is typically 15–25%.
We conduct comprehensive licence inventories, quantify the financial impact of transitioning from EA to MCA, design optimal structures (pure MCA, hybrid EA/MCA, or CSP combinations), and implement governance frameworks before the transition. Our approach ensures enterprises do not lose pricing advantages, SA benefits, or custom contractual protections during the migration without equivalent safeguards in the MCA framework.
Redress Compliance has no commercial relationship with Microsoft — no partner status, no resale revenue, no referral commissions. Our recommendations on EA vs MCA, pricing negotiations, and competitive positioning are exclusively aligned with the enterprise’s interests. This independence is particularly critical during the MCA transition, where Microsoft’s account teams are incentivised to migrate customers to MCA regardless of whether it serves the customer’s financial interests.
“The transition from EA to MCA is not a licensing administrative change — it is a fundamental restructuring of the commercial relationship with Microsoft. Enterprises that treat it as a routine migration will lose 20–30% in pricing advantages, negotiation leverage, and contractual protections. Enterprises that approach it strategically, with independent advisory and data-driven negotiation, can preserve EA-equivalent outcomes within the MCA framework.”
Redress Compliance delivers independent Microsoft licensing advisory for enterprises facing the transition from EA to MCA — licence inventory, financial impact analysis, pricing addendum negotiation, hybrid structure design, governance implementation, and strategic positioning that preserves EA-equivalent protections within the new commercial framework. Complete vendor independence.