Your Enterprise Agreement Is Expiring: A Complete Guide to the EA-to-MCA Transition
The End of an Era: Microsoft Enterprise Agreements
If your organization runs Microsoft 365, Azure, or Dynamics 365 under an Enterprise Agreement (EA), you've likely heard the news: Microsoft is phasing out EA renewals in favor of the Microsoft Customer Agreement (MCA). For many IT leaders, this represents the biggest licensing shift in over a decade.
This isn't just a paperwork change. The move from EA to MCA fundamentally alters how you buy, manage, and optimize Microsoft licensing. Understanding these changes now — before your renewal date — is critical to avoiding unnecessary cost increases and ensuring a smooth transition.
What Is the Microsoft Customer Agreement (MCA)?
The MCA is Microsoft's simplified, standardized purchasing agreement designed to replace the patchwork of legacy agreements (EA, MPSA, and Open). Key characteristics include:
- Perpetual agreement: Unlike the EA's three-year term, the MCA doesn't expire. You sign it once and purchase subscriptions on top of it.
- Monthly or annual billing: More flexibility in payment terms compared to the EA's rigid annual payment schedule.
- No minimum seat counts: EAs typically required a 500-seat minimum. MCA has no such floor.
- Partner-mediated or direct: You can purchase through a Cloud Solution Provider (CSP) partner or directly from Microsoft.
Key Differences Between EA and MCA
Pricing Structure
Under an EA, you negotiated pricing upfront for a three-year term, often securing volume discounts and price protection. With MCA, pricing is typically based on Microsoft's published list prices, though CSP partners can offer discounted rates based on their own margin structure.
What this means for you: Without proactive negotiation, you could see price increases of 10–25% on your Microsoft stack. The days of automatic price locks are over.
True-Up vs. Pay-As-You-Go
EAs allowed organizations to "true up" annually — adding licenses throughout the year and reconciling the bill once per year. Under MCA through a CSP, licenses are billed monthly or annually as consumed.
What this means for you: Better cash flow management, but you need tighter license governance to avoid paying for unused seats.
Software Assurance and Hybrid Benefits
Software Assurance (SA) — the upgrade and support benefit bundled with EA licenses — doesn't carry over in the same way under MCA. However, Azure Hybrid Benefit remains available, letting you use existing Windows Server and SQL Server licenses to reduce Azure VM costs.
What this means for you: Audit your SA benefits before transition. Some organizations lose valuable training vouchers, planning services, and deployment support during the switch.
The Timeline: When Do You Need to Act?
Microsoft has been communicating EA sunset plans throughout 2025 and into 2026. Here's the general timeline:
- Now: Review your current EA terms, renewal date, and total licensing spend
- 6 months before expiry: Begin evaluating CSP partners and alternative licensing structures
- 3 months before expiry: Finalize your partner selection and negotiate pricing
- At renewal: Execute MCA with your chosen partner and migrate subscriptions
Organizations whose EAs expire in 2026 should already be in active evaluation mode. Waiting until the last minute severely limits your negotiating leverage.
How to Prepare for a Smooth Transition
1. Audit Your Current Licensing
Before you can negotiate effectively, you need a clear picture of what you're actually using. Common findings during licensing audits include:
- 15–30% of licenses sitting idle or underutilized
- Users on E5 licenses who only need E3 capabilities
- Duplicate licenses across departments
- Orphaned licenses from departed employees
2. Right-Size Before You Renew
The transition is the perfect opportunity to eliminate waste. Downgrade users who don't need premium features, reclaim unused licenses, and consolidate overlapping subscriptions. This alone can reduce your licensing bill by 15–20%.
3. Get Multiple Bids from CSP Partners
This is where most organizations leave money on the table. Many companies simply accept the first offer from their incumbent partner or Microsoft directly. But CSP partners have different margin structures, support capabilities, and value-added services.
Competitive bidding consistently saves organizations 15–30% on their Microsoft licensing costs. Platforms like License Bids make this easy by letting you submit your bill of materials anonymously and receive competitive proposals from multiple verified Microsoft partners — without the awkward vendor conversations.
4. Negotiate Beyond Price
Price per license is important, but it's not everything. When evaluating MCA proposals, also consider:
- Support SLAs: What response times and escalation paths are included?
- Billing flexibility: Can you scale seats up and down monthly?
- Azure optimization: Does the partner offer FinOps or cost management tools?
- Migration support: Will they help with the technical transition?
- Contract terms: What are the exit clauses and auto-renewal policies?
5. Plan for Ongoing Optimization
Under the EA model, you could somewhat "set it and forget it" for three years. MCA requires more active management. Build a quarterly review cadence to:
- Review license utilization reports
- Adjust seat counts based on headcount changes
- Evaluate new SKUs and feature releases
- Benchmark your pricing against market rates
The Bottom Line
The EA-to-MCA transition is happening whether you're ready or not. Organizations that treat this as a strategic opportunity — rather than a forced administrative exercise — consistently come out ahead. Audit your licenses, right-size your deployment, get competitive bids, and negotiate holistically.
The companies saving the most money through this transition are the ones that refuse to accept the first offer on the table. In a market where every CSP partner is hungry for your business, leverage is on your side — but only if you use it.
License Bids helps organizations navigate the EA-to-MCA transition by connecting them with competing Microsoft partners. Submit your licensing requirements to see what competitive bidding can save you.
While this article focuses on Microsoft licensing, License Bids supports competitive bidding across Microsoft 365, Google Workspace, and AWS. Whatever your cloud licensing needs, you can submit your requirements and get competing bids from verified partners.
About the Author
Steve Kelley
Steve Kelley is the founder of Software Licensing Advisors and License Bids. With over 15 years of experience in Microsoft licensing and cloud strategy, he helps organizations reduce licensing costs through competitive bidding and strategic partner selection.