Summary
After twenty-five years of advising enterprises on Microsoft licensing, I've watched the software giant systematically dismantle the traditional Enterprise Agreement model. What began as whispers in partner channels has become a full-scale transformation that's catching many organisations off guard.
The writing has been on the wall since 2019, but Microsoft's recent acceleration of EA phase-outs has left thousands of mid-sized enterprises scrambling to understand their options. If you're among the growing number of organisations being pushed away from EA, you're facing a choice between Microsoft Customer Agreement for Enterprise (MCA-E) and Cloud Solution Provider (CSP) programmes, each with dramatically different cost structures and operational implications.
Having negotiated hundreds of these transitions, I can tell you that the wrong choice typically costs enterprises 15-30% more annually while introducing new complexities that most IT teams aren't prepared for. The good news? With proper planning and negotiation, you can often achieve better outcomes than your old EA ever delivered.
EA Phase-Out Reality Check
2,400+ users | 500-2,400 users | Under 500 users |
|---|---|---|
EA renewals are still possible, but under pressure | Being actively pushed to MCA-E or CSP | EA renewals routinely declined |
Timeline: Most transitions forced within 12 months of renewal
Cost impact: 15-30% increases without proper negotiation
The Enterprise Agreement: Understanding What You're Losing
Enterprise Agreement remains Microsoft's flagship volume licensing programme, though its days are numbered for many customers. Built around three-year commitments with minimum seat requirements (500+ users), EA provided something increasingly rare in software licensing: genuine price predictability.
The model was elegantly simple. You committed to specific volumes across Microsoft's product portfolio, received tiered discounts (Level A through D), and enjoyed three years of price protection. Software Assurance came bundled, providing upgrade rights, support benefits, and deployment planning services that many organisations never fully utilised but appreciated having.
EA’s true-up model gave enterprises rare cost flexibility without compromising compliance.
What made EA particularly attractive was its annual true-up process. Rather than paying for every possible user upfront, you could start with conservative estimates and reconcile actual usage each year. For growing organisations, this meant spreading licensing costs more evenly whilst maintaining compliance.
EA at a Glance
Contract term | 3 years fixed |
Minimum seats | 500+ users/devices |
Discounting | Tiered volume discounts (Level A-D) |
Software Assurance | Included (compulsory) |
Azure support | Limited |
Flexibility | Low - rigid structure |
Best for | Large enterprises wanting predictable costs |
But EA's rigidity, originally a feature, became a liability as cloud adoption accelerated. The programme wasn't designed for the consumption-based economics of Azure.
When Microsoft realised that forcing cloud services into traditional software licensing models was limiting their growth, they began the systematic phase-out we're witnessing today.
Microsoft Customer Agreement for Enterprise: The Cloud-First Alternative
MCA-E represents Microsoft's vision of modern enterprise licensing, if you can stomach the trade-offs. Unlike EA's fixed three-year terms, MCA-E operates as an evergreen agreement with flexible subscription periods ranging from one to three years.
The programme shines when dealing with Azure services. MCA-E supports Azure Plan natively, enabling trueconsumption-based billing for infrastructure services. MACC integration allows organisations to commit to specific Azure spending levels in exchange for discounts, effectively treating cloud consumption like traditional software licensing.
MCA-E Quick Facts
Contract term | Evergreen (1-3 year subscriptions) |
Minimum seats | None |
Discounting | Negotiated per subscription |
Software Assurance | Optional (separate purchase) |
Azure support | Full Azure Plan and MACC support |
Flexibility | High - subscription-based |
Best for | Cloud-first organisations with strong FinOps capabilities |
From a procurement perspective, MCA-E introduces several changes that Microsoft positions as modernisations. Digital contracting replaces the paper-heavy EA process, billing profiles provide granular cost allocation, and there's no minimum seat requirement. However, these "improvements" often come with hidden administrative costs and reduced negotiating power.
MCA-E modernises procurement—but shifts cost risk and admin burden onto the customer.
MCA-E's flexibility comes with hidden costs. Without EA's tiered discount structure, you're negotiating pricing product by product, subscription by subscription. The evergreen nature means constant renewal discussions rather than EA's predictable three-year cycles. Price protection becomes limited to individual subscription terms, exposing organisations to more frequent price increases.
Signs You Should Consider MCA-E
✓ Being forced out of the EA renewal
✓ Significant Azure consumption (>£100k annually)
✓ Strong financial operations team
✓ Comfortable with subscription economics
✓ Need modern digital procurement processes
✓ Want alignment with Azure Plan and MACC
Microsoft EA vs MCA-E – Key Differences
Feature | EA (Enterprise Agreement) | MCA-E (Microsoft Customer Agreement) |
|---|---|---|
Term | 3-year fixed | Evergreen (1–3-year subscriptions) |
Minimum Seats | ~500+ | No minimum |
Discounting | Tiered, locked for 3 years | Negotiated per subscription |
Software Assurance | Included | Optional |
Azure Plan & MACC | Limited support | Full support |
Flexibility | Low | High |
Price Protection | 3 years | Per subscription term only |
Custom Terms | Supported | Limited |
✅ Pros of EA | 🔴 Cons of EA | ✅ Pros of MCA-E | 🔴 Cons of MCA-E |
|---|---|---|---|
✓ Deep discounts for large volumes | - Rigid structure and true-up system | ✓ Flexible subscription model | - Higher long-term costs without volume tiers |
✓ Full Software Assurance benefits | - No longer supports Azure consumption commitments | ✓ Modernised digital purchasing | - Price protection limited to individual terms |
✓ High customisation and contract flexibility | - Being phased out for many mid-size clients | ✓ MACC and Azure-native billing | - Less room for contract negotiation |
CSP (Cloud Solution Provider): Maximum Flexibility, Maximum Complexity
CSP represents Microsoft's answer to the channel partner ecosystem, allowing authorised partners to resell Microsoft cloud services with their own pricing and support models. For certain organisations, CSP offers unmatched flexibility and partner-driven value.
CSP prioritises flexibility over structure—but convenience comes at a price.
The programme's strength lies in its lack of constraints, which Microsoft and partners heavily promote. No minimum seat requirements, monthly or annual subscription options, and the ability to easily add or remove licenses make CSP appealing for dynamic environments. Partners can bundle additional services, provide local support, and create custom billing arrangements that larger programmes can't accommodate, though you'll pay for these conveniences.
CSP Essentials
Contract term | Monthly or annual subscriptions |
Minimum seats | None |
Pricing | Set by partner (includes margin) |
Software Assurance | Not included |
Azure support | Full Azure Plan and MACC support |
Management | Fully partner-managed |
Best for | SMBs, startups, dynamic environments |
CSP also supports modern Microsoft services, including Azure Plan and MACC, though implementation varies significantly between partners. The best CSP partners provide genuine value through managed services, technical expertise, and billing consolidation that reduces administrative overhead.
However, CSP's flexibility introduces new challenges. Pricing becomes partner-dependent, often resulting in higher costs than direct Microsoft programmes due to partner margins. You're essentially trading Microsoft's enterprise-grade support for partner-provided alternatives, which vary dramatically in quality and scope.
Red Flags in CSP Negotiations
⚠️ Partner won't provide detailed pricing breakdown
⚠️ Margins above 15% without clear value-add
⚠️ Limited Azure expertise or certifications
⚠️ No clear SLA for support response times
⚠️ Restrictive contract terms for switching partners
⚠️ Poor references from similar-sized clients
Microsoft EA vs CSP – Flexibility vs Control
Feature | EA | CSP |
|---|---|---|
Seat Requirement | ~500+ | None |
Pricing | Microsoft-negotiated tiers | Set by partner |
Contract Term | 3 years | Monthly or annual |
Billing & Support | Microsoft/partner | Fully partner-managed |
Software Assurance | Included | Not included |
Ideal For | Large enterprises | SMBs, dynamic or project-based orgs |
EA Advantages | CSP Advantages |
|---|---|
✓ Central control and governance | ✓ No minimums |
✓ Stable pricing for 3 years | ✓ Ultimate flexibility |
✓ Better discount leverage | ✓ Partner-led management and support |
The Strategic Comparison That Matters
Rather than getting lost in feature comparisons, focus on the strategic implications of each programme choice.
Factor | EA | MCA-E | CSP |
|---|---|---|---|
Cost predictability | ✅ Excellent (3 years) | ⚠️ Moderate (per subscription) |