Enterprise organisations face a genuine licensing model decision at EA renewal. The three primary options — Enterprise Agreement (EA), Cloud Solution Provider (CSP), and Microsoft Customer Agreement (MCA) — have materially different commercial structures, and the right answer is not the same for every organisation. What is consistent is that the analyses presented by parties with financial interests in the outcome (Microsoft account teams, CSP partners, LSPs) tend to understate the relevant complexity and overstate the case for the model that generates the most revenue for the presenting party.
This article builds a rigorous three-year cost comparison framework. We use a representative 2,000-user organisation as the worked example, but the methodology applies regardless of your scale. Understanding this framework before engaging Microsoft or partners in a licensing model discussion is the commercial prerequisite for making a well-informed decision.
How Each Model Works Commercially
Enterprise Agreement (EA)
The EA is a three-year, upfront-commitment agreement. You commit to a minimum user count, Microsoft applies a product-level discount based on your platform designation (Enterprise Platform, Core Infrastructure, Productivity), and you pay annually in advance. The EA includes Software Assurance on all perpetual products and provides access to a significant range of SA benefits — training vouchers, step-up rights, licence mobility, disaster recovery rights, home use programme, and others. EA also enables Microsoft Azure Consumption Commitments (MACC), which provide Azure pricing advantages unavailable in CSP or standard MCA.
The EA's commercial advantages are: negotiated pricing (typically 15–35% below list for well-managed deals), price lock for three years, Software Assurance value, MACC access, and the ability to negotiate non-standard commercial terms. Its disadvantages are: three-year commitment with limited flexibility to reduce seat count mid-term, annual true-up obligation, upfront annual payment, and administrative overhead.
Cloud Solution Provider (CSP)
CSP is a monthly or annual subscription model transacted through a Microsoft partner (either Direct Bill Tier 1 or Indirect Reseller Tier 2 — see our guide to direct vs indirect CSP). Pricing is based on Microsoft's NCE (New Commerce Experience) list pricing plus partner margin. CSP does not include Software Assurance on perpetual products. CSP does not provide EA-equivalent MACC access. CSP provides seat-by-seat flexibility (monthly terms allow seat count adjustments; annual terms lock the commitment for 12 months).
CSP's nominal advantages are: flexibility to scale up and down (monthly terms), no multi-year commitment, faster provisioning for new products. Its commercial disadvantages are: prices are structurally higher than EA negotiated prices, monthly terms carry a 20% NCE premium, no Software Assurance, limited Azure pricing advantages, partner margin adds 8–18% above Microsoft's wholesale price, and no ability to negotiate non-standard terms. The NCE framework has significantly eroded the flexibility advantage that CSP historically offered.
Microsoft Customer Agreement (MCA)
MCA is Microsoft's non-negotiated, digitally-accepted agreement. It is the default agreement for Azure consumption and is increasingly proposed as an EA alternative for M365. MCA has no minimum commitment, no negotiated pricing, and evergreen terms that Microsoft can modify with 30 days' notice. MCA does not include Software Assurance, does not provide EA-equivalent MACC pricing, and offers no price protection.
For most enterprise organisations, MCA for M365 represents a significant commercial step backward from an EA — higher prices, no price lock, no negotiation, and unilateral term change rights. The only scenario where MCA makes sense for M365 is when seat count is very small, highly variable, or the organisation's Microsoft relationship is genuinely transitional. See our MCA enterprise guide for detailed analysis.
The Complete Three-Year Cost Model: Components
A valid cost comparison must include all of the following components. Omitting any of them produces a misleading result.
Component 1: Licence Fees
The headline number. EA negotiated pricing is typically set at a discount to list price — for a well-managed 2,000-seat M365 E3 deal, expect 20–28% below list. CSP pricing via a Direct Bill partner for the same product at the same seat count will be 8–15% above EA-equivalent pricing (partner margin on top of Microsoft's wholesale, which is itself above the EA negotiated price). MCA pricing is list price with no discount.
Component 2: Software Assurance Value
EA includes Software Assurance on perpetual Microsoft products (Windows Server, SQL Server, Office perpetual, etc.). SA provides licence mobility rights, step-up entitlements, disaster recovery rights, training vouchers, and other benefits. For organisations with a significant on-premises footprint, SA value can be substantial — often £50,000–£200,000 annually for a 2,000-user organisation with a meaningful server estate. CSP and MCA do not include SA on perpetual products. CSP customers who want SA on perpetual products must purchase it separately (if available) or via EA.
Component 3: Azure MACC Economics
EA enables MACC — a committed Azure spend arrangement that provides pricing benefits beyond standard Azure consumption rates. MACC pricing advantages include Unified Support credit application, Reserved Instance pricing, Savings Plan access, and Azure Hybrid Benefit. For organisations with significant Azure consumption (£200,000+ annually), MACC provides material savings unavailable in CSP or standard MCA. Our analysis of Azure-heavy organisations shows MACC typically delivers 12–22% lower effective Azure cost versus CSP or MCA consumption billing. See our MACC negotiation guide for the full framework.
Component 4: Price Increase Exposure
EA provides a three-year price lock. CSP annual terms provide a 12-month price lock. CSP monthly terms and MCA provide no price lock. Microsoft has implemented significant price increases since 2021: the commercial price increase of 15–25% on M365 products in 2022, the Teams unbundling in Europe in 2023, and ongoing Copilot and AI product pricing additions. An organisation that transitions from EA to CSP or MCA during a period of price increase activity will crystallise those increases immediately rather than at the next EA renewal. See our price increase history for the full timeline.
Component 5: Partner Margin (CSP Only)
CSP pricing includes partner margin. This is not separately disclosed in most CSP invoices — it is embedded in the per-seat price. For M365 E3 at 2,000 seats, partner margin of 8–12% represents £28,000–£42,000 annually that is not present in an EA arrangement. Over three years, this is £84,000–£126,000 in commercial intermediary cost above EA pricing.
Component 6: Switching Costs
Transitioning between licensing models is not free. EA to CSP transition costs include: perpetual licence entitlement documentation (typically 40–80 hours of specialist work), VLSC key management, SA benefit consumption and expiry management, Azure re-billing under CSP, partner integration work, and billing reconciliation for the transition period. EA to MCA transition costs are similar for M365 but more complex for Azure due to MACC unwinding. These switching costs are real and are typically not modelled in partner-generated CSP migration proposals.
Component 7: Administrative Burden
EA requires annual true-up — an inventory exercise, gap identification, and reporting process that typically consumes 80–160 hours of IT and finance time annually. This is a real cost that CSP (which bills automatically on provisioned seats) does not impose. For organisations with a well-managed deployment, this burden is lower; for those with complex environments, it is higher. CSP's automatic billing model does eliminate true-up overhead but creates its own administrative requirement: monthly bill reconciliation and governance to prevent seat over-provisioning.
Worked Example: 2,000-User Organisation, Three-Year View
The following model uses representative market rates. Individual organisations will have different variables; the methodology is the point, not the specific figures.
Assumptions: 2,000 users, M365 E3, Azure consumption £400,000/year, on-premises estate with Windows Server and SQL Server under SA, stable headcount (±5% per year), 3-year period.
Three-Year Cost Comparison: 2,000 Users, M365 E3 + Azure
| Cost Component | EA (Negotiated) | CSP (Direct Bill) | MCA (List) |
|---|---|---|---|
| M365 E3 licences (3 years) | £1,296,000 (22% disc.) | £1,530,000 (+10% mkt.) | £1,662,000 (list) |
| Azure consumption (3 years) | £1,080,000 (10% MACC disc.) | £1,200,000 (no MACC) | £1,200,000 (no MACC) |
| Software Assurance value (3 yrs) | −£240,000 (included benefit) | £0 (not included) | £0 (not included) |
| Partner margin (CSP only) | £0 | £108,000 (embedded) | £0 |
| Price increase exposure | £0 (locked) | £60,000–£90,000 (est.) | £90,000–£120,000 (est.) |
| Switching cost (one-time) | £0 (baseline) | £25,000–£45,000 | £20,000–£35,000 |
| Admin burden delta | +£30,000 (true-up) | £0 (baseline) | £0 (baseline) |
| Three-Year Total Cost | £2,166,000 | £2,923,000–£2,983,000 | £2,972,000–£3,017,000 |
In this representative example, the three-year cost difference between a well-negotiated EA and a CSP alternative is approximately £757,000–£817,000 for a 2,000-user organisation. The EA advantage narrows when headcount is highly volatile, the on-premises SA footprint is small, Azure consumption is low, or the EA negotiation is poorly executed. It widens when headcount is stable, the SA estate is substantial, and Azure commitments are large.
When CSP Is Actually the Better Model
CSP does win the comparison in specific, genuine scenarios. The conditions under which CSP makes commercial sense are:
- Rapid headcount growth (30%+ per year): EA true-up mechanics mean rapid growth organisations pay for the full incremental seat count at list price at each anniversary. CSP allows proportional monthly billing. For organisations genuinely growing at 30%+ annually, CSP's flexibility advantage can offset the base price premium.
- Volatile or uncertain seat count: If headcount is genuinely difficult to predict — post-acquisition integrations, major restructurings, organisations with high contractor populations — CSP's month-by-month flexibility has real value. EA over-commitment risk is real when the future headcount trajectory is uncertain.
- No meaningful on-premises SA estate: For a cloud-native organisation with no Windows Server, SQL Server, or other SA-eligible on-premises products, the SA benefit component of the EA comparison becomes irrelevant, which shifts the balance toward CSP for smaller deployments.
- Low Azure consumption (below £150,000/year): Below this threshold, the MACC advantage is limited. The EA premium for Azure-heavy organisations largely disappears when Azure consumption is low.
- Sub-500 seat deployments: EA minimum commitment requirements and administrative overhead make EA less commercially attractive at small scale. Below 500 seats, CSP is typically the appropriate model even when EA is nominally available.
A Note on MCA as an EA Alternative
Microsoft increasingly proposes MCA as an EA alternative, particularly for organisations that are primarily cloud-first and have minimal on-premises requirements. The MCA proposition from Microsoft is framed as "simplicity" — no commitment, digital terms, easy provisioning. The commercial reality is considerably less attractive for enterprise buyers.
MCA for M365 means paying list price with no negotiation, accepting evergreen terms that Microsoft can change with 30 days' notice, receiving no Software Assurance benefits, and losing the ability to negotiate non-standard commercial protections. For Azure, MCA is the standard agreement — but Azure MCA does not include the MACC pricing advantages that EA enables. The MCA-E (enterprise variant) closes some of these gaps but does so at the cost of additional commitments that reduce the flexibility advantage MCA is sold on. Our MCA enterprise analysis covers this in detail.
For most organisations above 200 seats with any on-premises estate and Azure consumption, MCA is not a commercially rational EA alternative. The analysis should be EA vs CSP, with MCA reserved for specific Azure-only or transitional scenarios.
The Hybrid Approach: EA Core, CSP at the Margins
The correct answer for many enterprise organisations is not a clean EA vs CSP choice — it is a structured hybrid model. The principle: use EA for stable, high-volume, SA-eligible, and Azure-intensive workloads; use CSP for products that are genuinely better suited to per-seat monthly billing (emerging technology pilots, highly seasonal workloads, rapid-growth product lines). Our hybrid EA/CSP model guide provides the full product allocation framework.
The hybrid approach captures the best commercial terms for each segment of your Microsoft estate. It requires more governance — dual contract management, partner relationship alongside Microsoft account team, billing reconciliation — but for organisations with more than £1M annual Microsoft spend and a mixed-maturity deployment landscape, the commercial benefit typically justifies the administrative overhead.
Get the Cost Comparison Right for Your Organisation
The EA vs CSP vs MCA comparison is not a generic calculation — it requires your specific headcount, product mix, Azure consumption, SA estate, and headcount trajectory. We build these models for enterprise organisations as part of our advisory practice.
Custom Three-Year Cost Model
We build a rigorous EA vs CSP vs MCA cost model using your actual licensing data — not representative figures. The result is a defensible basis for your licensing model decision.
Request Cost ModelEA Renewal Advisory
If EA is the right model, ensure you are negotiating it well. Our EA renewal advisory covers benchmarking, leverage identification, negotiation strategy, and clause-level review.
EA Advisory ServicesEA to MCA/CSP Transition
If CSP or MCA genuinely is the right model, our transition advisory covers entitlement protection, partner selection, migration sequencing, and SA exit strategy.
Transition AdvisorySummary: How to Use This Framework
The EA vs CSP vs MCA decision is one of the most commercially significant choices a large organisation makes in its technology procurement cycle. The correct methodology is to model all seven cost components over three years, using your specific data. The outcome of that analysis will differ by organisation, but the starting assumptions in the absence of organisation-specific data should be: EA is almost always cheaper for stable organisations above 500 seats with an on-premises estate and meaningful Azure consumption; CSP wins in specific high-volatility scenarios; MCA is not a commercially rational EA alternative for most enterprise organisations.
Before committing to any model transition, verify the analysis with independent advice. The entities who will present you with a comparison — your LSP, your CSP partner, your Microsoft account team — all have financial interests that are not aligned with your total cost minimisation. An independent advisor with no transaction incentive is the only party whose analysis you can take at face value on this decision.