Negotiating the MCA Transition
Microsoft is migrating enterprises from Enterprise Agreements to the Microsoft Customer Agreement — and most organisations are losing critical commercial protections in the process. This paper provides a clause-by-clause comparison, identifies the 12 protections you lose by default, and delivers a negotiation strategy to reinstate favourable terms.
Executive Summary
Microsoft's transition from the Enterprise Agreement (EA) to the Microsoft Customer Agreement (MCA) represents the most significant change to enterprise Microsoft commercial terms in over a decade. While Microsoft positions the MCA as a modernised, simplified framework, our analysis of over 150 enterprise transitions reveals that the shift systematically removes protections that customers have relied upon for years.
Organisations that migrate to the MCA without a structured negotiation strategy are accepting materially inferior commercial terms — often unknowingly. The MCA eliminates fixed pricing, reduces true-up flexibility, shifts payment terms in Microsoft's favour, and introduces unilateral amendment rights that fundamentally alter the commercial balance.
5 Key Findings
The MCA removes 12 critical commercial protections that enterprises have relied upon under the EA, including price locks, step-up caps, true-up timing flexibility, and co-termination rights.
Most organisations are accepting the MCA without negotiation, unaware that amendments and side letters can reinstate many of the protections lost in the transition.
Unilateral amendment clauses in the MCA allow Microsoft to modify commercial terms, SLAs, and product definitions with 30 days' notice — a provision absent from the EA.
Cost exposure from the MCA transition averages 18–30% over a three-year period when price protection, step-up cap, and payment term changes are modelled together.
Structured negotiation can recover 60–80% of the lost protections through amendments, side letters, and escalation to Microsoft's deal desk — but only before migration is completed.
What is the MCA & Why Microsoft is Pushing It
The Microsoft Customer Agreement is a single, unified volume licensing framework designed to replace the Enterprise Agreement, the Microsoft Products and Services Agreement (MPSA), and other legacy contracting vehicles. Microsoft began the MCA rollout in earnest in 2023 and has progressively mandated its adoption at renewal for most enterprise accounts.
Microsoft's Stated Rationale
Microsoft positions the MCA as a simplification initiative. The EA framework — built up over two decades — included multiple amendment layers, enrolment forms, product-specific annexes, and country-specific terms. The MCA consolidates these into a single agreement with standardised product terms published at microsoft.com/licensing/terms.
Microsoft emphasises three benefits: reduced contract complexity, a single agreement across all Microsoft cloud services, and faster onboarding for new workloads. These benefits are real but obscure the commercial trade-offs that favour Microsoft.
The Commercial Reality
The MCA shifts the commercial balance in Microsoft's favour in several critical ways. By moving to online product terms that Microsoft can update at any time, the agreement creates a dynamic, unilaterally modifiable contract — a structure unprecedented in enterprise software. Fixed pricing gives way to list pricing with discretionary discounting, true-up timing is standardised rather than negotiated, and co-termination provisions are significantly constrained.
For enterprises with complex Microsoft estates — particularly those spanning Microsoft 365, Azure, Dynamics 365, and Power Platform — the MCA creates new commercial risks that must be addressed before migration is finalised.
Critical Timing: Once an organisation signs the MCA and its associated enrolments, the EA terms are permanently retired. All negotiation leverage must be exercised before migration, not after. Post-migration amendments are significantly harder to secure.
EA vs. MCA — Clause-by-Clause Commercial Comparison
The following comparison identifies the most commercially significant differences between the EA and MCA frameworks. Each provision is assessed for its financial and operational impact on the enterprise.
| Provision | Enterprise Agreement | MCA |
|---|---|---|
| Price Protection | Fixed pricing locked for the full 3-year term | No price lock; pricing subject to change at renewal or mid-term |
| Step-Up Cap | Annual price increases capped (typically 3–5%) | No step-up cap; Microsoft retains discretion on increases |
| True-Up Timing | Annual true-up on anniversary date with negotiable terms | Monthly billing/true-up with limited flexibility |
| Payment Terms | Net 60 standard; Net 90 negotiable | Net 30 standard; limited extension options |
| Unilateral Amendment | Not present; changes require mutual agreement | Microsoft may amend terms with 30 days' notice |
| Co-Termination | All enrolments co-terminate on EA anniversary | Individual subscription terms; co-termination not guaranteed |
| Product Terms | Locked to version at time of signing | Dynamic; references online terms that Microsoft can update |
| SLA Commitments | Contractually embedded with defined remedies | Referenced via online SLA page; subject to change |
| Termination for Convenience | Available with defined notice periods | More restrictive; subscription minimums may apply |
| Data Residency | Negotiable as part of EA amendments | Subject to standard DPA; amendment more difficult |
| Audit Rights | Defined scope and frequency with negotiable terms | Broader telemetry rights; less visibility into audit triggers |
| Discount Protection | Discount levels contractually fixed for term | Discounts discretionary and may not carry forward |
The 12 Protections You Lose by Default
When migrating from the EA to the MCA, the following protections are either explicitly removed or significantly weakened. Each represents a tangible financial or operational risk that must be assessed and, where possible, reinstated through negotiation.
Fixed-Price Lock
The EA guarantees pricing for the full agreement term. The MCA allows Microsoft to adjust pricing at renewal or when subscription terms change, exposing you to mid-cycle cost increases.
Step-Up Cap on Annual Increases
EA step-up caps limit year-over-year price increases to a negotiated percentage. The MCA contains no such cap, leaving pricing entirely at Microsoft's discretion.
Annual True-Up Flexibility
The EA's annual true-up cadence allows organisations to manage licence counts on a yearly basis. The MCA's monthly model reduces flexibility and accelerates cost recognition.
Extended Payment Terms
EA contracts commonly include Net 60 or Net 90 payment terms. The MCA defaults to Net 30, compressing cash flow cycles and increasing working capital requirements.
Mutual Amendment Requirement
EA modifications require mutual written consent. The MCA grants Microsoft unilateral amendment rights with only 30 days' notice — a fundamental shift in the contractual balance.
Co-Termination Rights
The EA allows all enrolments and subscriptions to co-terminate on a single date. The MCA fragments subscription terms, creating complex renewal calendars and reducing negotiation leverage.
Locked Product Terms
EA product terms are fixed at signing. The MCA references online product terms that Microsoft can modify at any time, creating a dynamic contractual obligation.
Embedded SLA Commitments
EA SLAs are contractually embedded with defined service credits. The MCA references an online SLA page, allowing Microsoft to modify service level commitments and remedies.
Flexible Termination for Convenience
The EA provides defined termination-for-convenience provisions. The MCA imposes stricter constraints, including minimum subscription commitments that survive termination.
Negotiable Data Residency Terms
Data processing and residency terms were negotiable as EA amendments. Under the MCA, data terms are standardised and significantly harder to customise.
Defined Audit Scope
EA audit provisions had negotiable scope and frequency. The MCA expands Microsoft's telemetry and compliance verification rights with less transparency around triggers and process.
Discount Carry-Forward
EA discount levels are contractually fixed for the term. MCA discounts are discretionary and may not carry forward at renewal, creating repricing risk at every cycle.
Negotiation Strategy: Amendments, Side Letters & Escalation Paths
The MCA is not a take-it-or-leave-it proposition for enterprises with significant Microsoft spend. Microsoft's deal desk and enterprise licensing teams have authority to approve amendments and side letters that reinstate many EA-era protections — but only when the customer drives a structured negotiation before migration.
Three-Layer Negotiation Framework
MCA Amendments
Formal modifications to the MCA itself, executed as addenda. These are the most durable form of protection and should be pursued for the highest-priority provisions: price protection, unilateral amendment limitation, and payment terms.
Side Letters
Supplementary agreements that sit alongside the MCA. Side letters are typically easier to secure than amendments and are effective for provisions like co-termination, SLA commitments, and audit scope definitions.
Escalation to Deal Desk
For high-value accounts, escalation to Microsoft's corporate deal desk unlocks approval authority that regional account teams do not possess. This path is essential for securing price locks, step-up caps, and custom termination provisions.
Negotiation Sequencing
Timing is critical. The optimal negotiation window opens 6–9 months before your EA renewal date and closes when the MCA is signed. Once the MCA is executed, amendment leverage decreases substantially.
Phase 1 (6–9 months out): Conduct a commercial impact assessment comparing your current EA terms against the standard MCA. Quantify the financial exposure across all 12 lost protections.
Phase 2 (4–6 months out): Present your amendment requirements to the Microsoft account team. Frame these as conditions for MCA migration, not requests. Anchor to your existing EA terms as the baseline.
Phase 3 (2–4 months out): Escalate unresolved provisions to the deal desk. Use competitive alternatives (Google Workspace, AWS, etc.) as legitimate leverage. Secure written commitments before signing.
Phase 4 (pre-signature): Execute amendments and side letters simultaneously with the MCA. Do not sign the MCA and negotiate amendments afterwards — this sequence dramatically reduces your leverage.
Template Amendment Language for Critical Provisions
The following template clauses are designed to be incorporated into MCA amendments or side letters. Each addresses one of the critical protections lost in the EA-to-MCA transition. These templates should be adapted to your specific commercial context and reviewed by legal counsel.
Price Protection Amendment
Step-Up Cap Amendment
Unilateral Amendment Limitation
Payment Terms Extension
Co-Termination Provision
Important: These templates represent starting positions. Microsoft's legal team will negotiate specific language. The key is ensuring the commercial intent — price certainty, mutual consent, co-termination — is preserved regardless of the final wording.
Common MCA Transition Traps
Our engagement experience across enterprise MCA transitions reveals recurring patterns of value erosion. These traps are avoidable with proper preparation but are routinely triggered when organisations approach the transition reactively.
Trap 1: Accepting the MCA as Non-Negotiable
Microsoft account teams often present the MCA as a standard agreement that all customers must sign as-is. In reality, amendments and side letters are routinely approved for enterprise accounts — but only when customers ask.
Trap 2: Signing Before Securing Amendments
Organisations that sign the MCA with the intention of negotiating amendments afterwards lose virtually all leverage. The sequence must be: negotiate first, sign together.
Trap 3: Ignoring the Unilateral Amendment Clause
The MCA's unilateral amendment provision is the single most commercially significant change from the EA. Organisations that fail to limit this clause are accepting a contract that Microsoft can modify with 30 days' notice.
Trap 4: Assuming Discounts Carry Forward
EA discount levels do not automatically transfer to the MCA. Each discount must be explicitly documented in the MCA enrolment or amendment. Undocumented discounts will revert to list pricing.
Trap 5: Overlooking Product Term Dynamics
The MCA references online product terms. Microsoft can modify these terms — including feature availability, usage rights, and licensing metrics — without customer consent. This is a material change from the EA's locked terms.
Trap 6: Failing to Model the Cost Impact
Without a detailed cost model comparing EA terms against MCA terms over a 3–5 year horizon, organisations cannot quantify the exposure. This model is essential for building the business case for negotiation.
Recommendations: 7 Priority Actions
The following actions should be initiated immediately for any organisation facing an EA-to-MCA transition within the next 12 months.
Conduct a Clause-by-Clause EA Audit
Document every commercial protection in your current EA, including amendments and side letters accumulated over previous terms. This becomes your negotiation baseline.
Model the Financial Impact of the MCA
Build a 3–5 year cost model comparing your current EA pricing and terms against the standard MCA. Quantify the exposure from each of the 12 lost protections.
Draft Your Amendment Requirements
Using the template language in Section 06 as a starting point, prepare specific amendment language for each protection you intend to reinstate. Prioritise: price lock, step-up cap, unilateral amendment limitation, and payment terms.
Engage Microsoft 6–9 Months Before Renewal
Begin the negotiation conversation well before your EA renewal date. Frame amendment requirements as conditions for migration, not post-signature requests.
Prepare Competitive Alternatives
Develop a credible assessment of competitive alternatives (Google Workspace, AWS, Slack, Zoom). You do not need to intend to switch — but you need Microsoft to believe you might.
Escalate to the Deal Desk for Critical Provisions
If your account team cannot approve price locks, step-up caps, or unilateral amendment limitations, escalate to Microsoft's corporate deal desk. These provisions require higher-level approval authority.
Execute Amendments Before Signing the MCA
Never sign the MCA without simultaneously executing all negotiated amendments and side letters. Post-signature negotiation leverage is dramatically reduced.
How Redress Can Help
Microsoft Practice
100% Independent — Zero Vendor Affiliations — No Reseller Agreements
Redress Compliance's Microsoft Practice provides independent advisory services across EA/MCA transition negotiation, Microsoft 365 licensing optimisation, Azure cost management, and compliance assurance. We represent your commercial interests — never Microsoft's.
Our Microsoft engagements typically deliver 20–35% cost reductions through a combination of term negotiation, licensing right-sizing, and deployment restructuring. Every recommendation is backed by contractual analysis and supported through implementation.
For MCA transition engagements specifically, we provide a full commercial impact assessment, draft all amendment and side letter language, and support your team through the negotiation process — including direct engagement with Microsoft's deal desk when escalation is required.
Book a Meeting
Speak with a Microsoft licensing specialist from our independent advisory team. We'll assess your current EA terms, quantify your MCA transition exposure, and outline a negotiation strategy tailored to your commercial position.
Redress Compliance
1314 E Las Olas Blvd, Fort Lauderdale, FL 33301
[email protected] | +1 (239) 402-7397