Microsoft EA vs MCA-E vs CSP: Which Agreement is Right in 2026

Microsoft's licensing portfolio presents one of the most complex decisions in enterprise software procurement. Three primary agreement types dominate the market: Enterprise Agreements (EA), Microsoft Cloud Agreements for Enterprise (MCA-E), and Cloud Solution Provider (CSP) arrangements. Each delivers distinct commercial structures, flexibility profiles, and discount mechanisms. The choice between them will shape your software costs, negotiation leverage, and operational agility for years to come.

This guide dissects the mechanics of each agreement type, reveals the hidden cost drivers that most procurement teams miss, and provides a framework for selecting the model that maximises value for your specific situation.

Understanding the Three Agreement Types

Enterprise Agreement (EA)

The Enterprise Agreement is Microsoft's flagship offering for large organisations. Introduced in 1999 and refined continuously over two decades, the EA has become the de facto standard for companies with 250+ users and annual software spend above $50,000.

Structurally, an EA is a three-year non-perpetual licence agreement. You commit to a total spend volume across a licence pool, which you then distribute across products and users as needed. This flexibility is the EA's defining characteristic. Unlike perpetual licensing models, your portfolio evolves alongside your organisation's needs without licence reallocation penalties.

Discount tiers within EAs are determined by your total commitment value, not product-by-product negotiations. A company committing to $300,000 in annual spend receives discount multipliers that apply uniformly across the Windows, Office, and server products included in the pool. The Microsoft Enterprise Agreement guide explores these discount structures in depth.

The EA model also includes Software Assurance (SA), which grants rights to run multiple versions simultaneously, provides deployment flexibility, and includes annual product updates. SA is mandatory under EA and priced as a percentage of your licence cost—typically between 30 and 40 percent depending on discount tier.

Microsoft Cloud Agreement for Enterprise (MCA-E)

Launched in 2019 and significantly expanded since 2022, the MCA-E represents Microsoft's answer to the shift toward cloud consumption. This is a monthly commitment model, not a traditional licence purchase.

Under MCA-E, you establish a consumption commitment (typically USD 1 million or more annually) and select your preferred services: Microsoft 365, Azure, Dynamics, and modern security products. You pay monthly or annual fees, and Microsoft counts actual consumption against your commitment. If you exceed the commitment, you pay overage costs at published rates. Unused commitment does not roll forward — it expires at month end. For organisations with significant Azure workloads, the MCA-E commitment structure intersects directly with how you negotiate your Azure MACC commit-to-consume terms, where drawdown mechanics and shortfall risk are the primary cost levers.

The commercial flexibility here is substantial. Unlike an EA's three-year lock-in, MCA-E can be modified monthly within your commitment window. You can shift spend between services, add new services, or pause services without renegotiation penalties. This appeals to organisations with volatile workloads or strategic uncertainty.

Discounts in MCA-E are tied to your commitment size and usage predictability. The discount percentage is lower than comparable EA discounts because Microsoft assumes greater revenue risk. A company with a volatile footprint will negotiate materially less aggressive discounts than a company with stable, predictable consumption.

Cloud Solution Provider (CSP)

CSP is not primarily a Microsoft agreement—it is a channel agreement where a third-party reseller (the CSP partner) owns the commercial relationship with Microsoft, and you purchase through that partner.

In CSP, you pay per-user-per-month pricing set by the CSP partner. Pricing is published monthly by Microsoft, but partners can set their own margins. This creates a two-layer pricing structure: Microsoft's cost to the partner, plus partner margin, equals your effective cost. CSP partner margins typically run from 12 to 18 percent at base, rising above 50 percent when managed services are bundled — understanding this structure is essential for benchmarking what you are actually paying.

CSP agreements now include NCE (New Commerce Experience) term options. Under NCE, CSP subscriptions can be committed on monthly, annual, or 3-year terms rather than rolling month-to-month. The complete NCE guide covers how these tiers work and what the seat lock implications are for each. Annual and 3-year NCE terms provide price lock protection — a critical consideration ahead of Microsoft's July 2026 global price increase.

CSP is administratively simple—the partner handles licence provisioning, renewal notices, and compliance tracking. Your burden of contract management drops significantly. However, you sacrifice transparency into your effective discount rate and become dependent on partner service quality.

Pricing Structures: Where the Money Actually Goes

The three agreement types employ fundamentally different pricing architectures, and misunderstanding these differences costs organisations millions annually.

EA Pricing Mechanics

An EA price is built on three layers: base licence cost, discount multiplier, and Software Assurance percentage.

Microsoft publishes list prices for each product—Windows 10 Pro, Office 365, SQL Server Standard, and so on. These list prices are intentionally high and serve as the anchor point for discount negotiation. Your discount multiplier applies directly to these list prices. A 35 percent discount means you pay 65 cents on the dollar for each licence unit, where the dollar is the list price.

Software Assurance is priced as a percentage of your discounted licence cost. If you negotiate a 35 percent discount on Office 365 and SA costs 34 percent, your total cost per unit is approximately 86 percent of list price (65 percent for the licence, plus 34 percent of 65 percent for SA). This compounding effect is frequently missed in cost modelling.

EA pricing also includes a "True-Up" mechanism. After your agreement period ends (or during mid-term reviews), Microsoft counts actual usage and true-ups your licence positions. If you licensed 500 users but actually used 650, you pay true-up fees for the 150 additional user licences. The true-up price is usually 10 to 15 percent higher than your negotiated EA price, creating an implicit penalty for underestimation.

The true-up guide provides detailed strategies for managing this exposure during contract renewal negotiations.

MCA-E Pricing Mechanics

MCA-E pricing operates on commitment + overage structure. Microsoft calculates a blended per-unit price for your commitment based on your service mix, commitment size, and negotiated discount percentage.

For example, a $2 million annual commitment covering Azure, Microsoft 365, and security products might translate to an effective per-compute-unit cost on Azure of $0.080 versus $0.095 for a equivalent market price, reflecting your commitment discount. However, this pricing is only locked for the contract term—typically one or two years.

Consumption metering is where MCA-E becomes critical. Azure consumption is metered to the minute. Microsoft 365 is metered per user per day. Security products are metered per protected asset. At month-end, your actual consumption is totalled and compared against your commitment. If you consumed less than committed, the shortfall is lost (no carryover, no credit). If you exceeded commitment, you pay published overage rates, which typically run 5 to 15 percent higher than your blended commitment rate.

This creates a powerful incentive for accurate forecasting. Organisations that consistently overcommit to avoid true-up penalties on an EA often perform worse under MCA-E, because the operational burden of managing unused commitment becomes material.

CSP Pricing Mechanics

CSP pricing is straightforward but opaque. Microsoft publishes a Transactional Services Price List (TSPL) each month. This shows the price at which each CSP partner can purchase licences from Microsoft. Partners then add margin and resell to customers.

Microsoft 365 Business Standard, for example, might be $12.50 per user per month on the TSPL. A CSP partner might purchase at that rate and resell at $14 per user per month, capturing $1.50 margin per user per month. With 500 users, that's $9,000 monthly margin for the partner—but $9,000 monthly overhead cost for you versus the EA negotiated rate.

Transparency is the critical failure point here. Most organisations never learn what their CSP partner's actual margin is, because the partner simply sends an invoice showing the total monthly cost. Without access to the TSPL, you cannot verify whether you are paying market rates or subsidising your partner's other client relationships.

CSP does offer one pricing advantage: no true-up, no minimum commitment, and no Software Assurance premium. You pay the same per-unit rate every month, making budgeting predictable. This simplicity appeals to organisations with limited procurement sophistication, even if the per-unit rate is materially higher than an equivalent EA rate.

Flexibility and Agility: The Hidden Cost of Commitment

Each agreement type carries different constraints on how you can modify your licence portfolio over time.

EA Flexibility Constraints

An EA runs for three years. Within that period, you can add or remove users, shift spending between products, and pause products, all without formal renegotiation. This is the EA's primary flexibility advantage—your licence portfolio evolves freely.

However, you cannot materially reduce your total annual commitment without triggering a contract modification and potential penalty. If you commit to $300,000 annually and then reduce to $200,000 after year one, Microsoft will either enforce your $300,000 commitment or renegotiate at less favourable terms.

Adding net-new products (products not included in your original EA) requires addition to the existing agreement, typically at less aggressive discounts than your core commitment discount. If your core EA covers Windows, Office, and server products at a 35 percent discount, adding security products might come at 28 to 30 percent, because those products are "outside the pool."

Step-up licensing rules further constrain flexibility. If you have a Windows 10 Pro licence and want to move a user to Windows 10 Enterprise, Microsoft charges the differential cost at list price or your EA discount, depending on the product mix.

MCA-E Flexibility Advantages

This is where MCA-E shines. Your commitment commitment is set monthly, and you can modify it within 90 days (depending on your agreement terms). You can shift spending between services month-to-month. You can pause services for non-consecutive months without penalties. This operational flexibility is invaluable for organisations running pilots, managing M&A integrations, or operating in volatile markets.

The cost of this flexibility is lower discount rates. A company that can commit to stable, predictable consumption for three years deserves better terms than a company that might pause services. This is why MCA-E discounts typically run 5 to 10 percentage points lower than equivalent EA discounts.

CSP Flexibility Advantages

CSP offers month-to-month operation without commitment. You can add users, remove users, pause services, or cancel entirely with a single month's notice. This appeals to organisations with high churn, seasonal workloads, or extreme uncertainty.

The cost is paid in per-unit pricing. A CSP arrangement often costs 15 to 25 percent more per user per month than an equivalent EA rate when you model the cost across comparable user counts and products.

Discount Structures and Negotiation Levers

Understanding how discounts are calculated and what you can negotiate is essential for maximising your commercial position.

EA Discounts

Microsoft applies discount multipliers based on your total commitment value and your organisation's profile (public sector, education, for-profit, and so on). Tier breakpoints typically fall around $25,000, $75,000, $150,000, $300,000, and $500,000+ annual commitments.

The discount percentage is applied uniformly to all products in your pool, though Microsoft reserves the right to apply product-specific adjustments for strategic reasons. A company negotiating a $500,000 commitment might receive a 35 percent base discount, but newer products like Copilot or advanced security offerings might come at 22 to 28 percent until they become part of the core pool.

The critical negotiation lever is competitive pressure. Microsoft's discount boundaries are not rigid—they are guidance for account teams. If you obtain a credible alternative quote from another vendor (Oracle, Salesforce, SAP) or another Microsoft option (MCA-E, CSP at published rates), you can use that to compress Microsoft's proposed discount. We recommend organisations obtain competitive quotations even if they intend to remain with Microsoft, because the threat of alternatives often unlocks 2 to 4 percentage points of additional discount.

The negotiation levers guide details specific tactics for using competitive alternatives, volume growth commitments, and multi-year terms to improve your discount position.

MCA-E Discounts

MCA-E discounts are negotiated as a percentage applied to published list prices, similar to EAs. However, the discount is typically lower because the monthly commitment structure reduces Microsoft's revenue visibility and increases churn risk in their model.

The negotiation lever in MCA-E is commitment stability and multi-year terms. Microsoft will apply better discounts if you commit to a two-year term (versus month-to-month modifications) and demonstrate usage stability. If your forecasts show high volatility, expect lower discounts to compensate for Microsoft's revenue risk.

CSP Discounts

There are no direct discounts to negotiate in CSP—the CSP partner sets their margin on top of Microsoft's published TSPL. However, you can negotiate the partner's margin if you are a large customer or have multi-year visibility.

A CSP partner might offer a preferred customer rate of $13.50 per user per month (versus $14 standard) if you commit to 500+ users or three-year volumes. This is margin compression, not a true discount, but the economic effect is identical.

Comparative Pricing Analysis: Numbers to Drive Decision-Making

Here is how the three models compare on a real cost basis for a representative organisation.

Dimension	Enterprise Agreement	MCA-E	CSP
User Count	1,000 users	1,000 users	1,000 users
Product Mix	Microsoft 365 E5, Windows 11 Pro, SQL Server Standard	Microsoft 365 E5, Windows 11 Pro, Azure IaaS	Microsoft 365 E5 (CSP pricing)
List Price (Annual)	$420,000	$380,000	$252,000
Discount %	35%	30%	N/A (partner margin)
Software Assurance %	34%	Included	N/A
Effective Annual Cost	$235,800	$266,000	$228,000
Cost per User Per Month	$19.65	$22.17	$19.00
Term	3 years	Monthly with annual commitment	Month-to-month
True-Up Risk	High (10-15% overage premium)	Medium (5% overage premium)	None

This model shows that CSP pricing can appear attractive on a per-user-per-month basis, but that calculation obscures operational costs. The EA requires three-year commitment but offers the lowest per-unit cost if you forecast accurately. MCA-E provides flexibility at a middle-ground price point, making it attractive for organisations prioritising agility over lowest-unit cost.

When Each Agreement Type Makes Sense

Choose Enterprise Agreement When:

• Your organisation has 250+ users and over $75,000 annual Microsoft spend.
• You can forecast your licence needs with reasonable accuracy (within 10-15 percent) for three years.
• You value operational flexibility within a commitment window more than maximum month-to-month agility.
• You intend to use Software Assurance rights (version hop, deployment rights, concurrent use).
• Your procurement team has capacity to manage true-up reconciliation and licence true-up exposure.
• You are running on-premises infrastructure or hybrid workloads where deployment flexibility is operationally critical.

Choose MCA-E When:

• Your workloads or user count fluctuates significantly month-to-month.
• You are migrating to cloud and your consumption profile is uncertain.
• You have multi-year visibility into commitment size but need operational flexibility to shift between services.
• You are managing an M&A integration or significant organisational restructure and cannot commit to rigid three-year terms.
• Your primary spend is on cloud services (Azure, Microsoft 365) rather than on-premises products.
• You have strong forecasting capabilities and can manage monthly consumption tracking to avoid overage penalties.

Choose CSP When:

• Your organisation has fewer than 100 users or less than $50,000 annual Microsoft spend.
• You value operational simplicity (partner manages all compliance tracking and licence provisioning) over lowest total cost.
• Your user count is highly volatile—you may need to add or remove 20 percent of users in any given month.
• You are running a pilot project or temporary workload where long-term licence planning is inappropriate.
• Your IT team lacks capacity for EA compliance management and true-up tracking.
• You are unwilling to commit to multi-year terms and accept the pricing premium that month-to-month operation requires.

Migration Paths: Moving Between Agreement Types

Organisations sometimes need to transition from one agreement type to another. These transitions are complex and carry hidden costs if not managed carefully.

EA to MCA-E Migration

This is increasingly common as organisations move workloads to Azure. The transition typically occurs at EA renewal. Your negotiating position is strongest 180 days before EA expiration, when Microsoft begins renewal discussions.

The key negotiation point is the runoff period. When you transition from EA to MCA-E, your EA typically runs through its end date, then MCA-E begins. This creates a potential gap in coverage if not planned explicitly. Ensure your MCA-E start date aligns with your EA end date, with zero-day continuity.

Also negotiate a "runway" discount on your MCA-E for the first year or two, to reflect that you are moving from EA to a less-committed model. Many organisations accept MCA-E at 2 to 3 percentage points higher discount than they would normally receive, because transitioning at EA renewal creates a temporary negotiating advantage.

EA to CSP Migration

Migrating from EA to CSP is less common, because it typically represents a move to lower commitment and higher per-unit cost. However, some organisations do this when they acquire a CSP partner (bringing CSP relationships in-house) or when they dramatically downsize.

The EA-to-CSP transition requires careful timing around true-up. If you are currently in an EA true-up window, you cannot cancel until true-up is complete. Plan your CSP transition 120 days after your most recent EA true-up to maximise flexibility.

MCA-E to EA Migration

This migration occurs when an organisation's consumption stabilises and commitment visibility improves. After running on MCA-E for 18 to 24 months with predictable monthly consumption, moving to an EA can unlock significant discount improvements—often 5 to 8 percentage points—because you are now demonstrating the commitment stability that drives EA discounts.

The commercial opportunity here is substantial. If you operated on MCA-E at 25 percent discount with $2 million annual consumption ($1.5 million net cost), moving to an EA at 32 percent discount (as you now have proof of consumption stability) reduces your cost to $1.36 million—a $140,000 annual saving.

Audit Risk and Compliance Across Agreement Types

Each agreement type carries different audit exposure and compliance obligations.

EA Audit Risk

Enterprise Agreements carry the highest audit risk. Microsoft audits EA customers extensively, on average once every 18 to 24 months. The audit scope covers actual user counts, device counts, product deployments, and Software Assurance eligibility.

True-up penalties are the main exposure. If you audited out and found you were using 1,200 users when you licensed 1,000, the true-up cost is applied retroactively—potentially across multiple years. This can result in $50,000 to $500,000+ exposure for mid-market organisations.

Mitigation requires rigorous licence position documentation. You should maintain a monthly licence tracking spreadsheet (automated where possible) showing your actual user count, device count, and product deployment against your EA licence positions. When Microsoft audits, having auditable, contemporaneous records dramatically reduces both audit scope and penalties.

The audit defence kit provides templates and processes for maintaining the documentation Microsoft expects during audits.

MCA-E Audit Risk

MCA-E audits are less frequent than EA audits but more focused. Microsoft typically audits MCA-E customer consumption accuracy—verifying that your metered consumption matches your actual service usage. The risk here is overstating consumption (to justify commitment) or understating it (to claim refunds).

Audit exposure on MCA-E is typically lower than EA because you are not committing upfront to user counts. You commit to a consumption amount, and your actual consumption is metered by Azure, Microsoft 365 services, and other telemetry. Microsoft has direct visibility into your actual consumption, reducing audit risk for usage-based compliance.

CSP Audit Risk

CSP audit risk is minimal from Microsoft's perspective, because your CSP partner is responsible for compliance. However, your CSP partner may audit your actual usage to verify that you are not using licences beyond your purchased count. This is typically straightforward because CSP is licensed per user per month, and provisioning controls limit you to your purchased count.

The operational risk in CSP is partner churn or insolvency. If your CSP partner exits the market or goes bankrupt, your licence relationship transfers to another partner. You may lose pricing continuity or require re-provisioning of your services during the transition.

Decision Framework: Which Agreement Fits Your Organisation

Here is a structured framework for evaluating which agreement type best fits your situation.

Practical Negotiation Tactics

When you are actively negotiating your Microsoft agreement, these tactics can unlock additional value.

Competitive Alternative Positioning

Obtain a credible alternative quotation—either from Oracle, Salesforce, or another cloud vendor, or from Microsoft in a different agreement type (EA versus MCA-E). Use this alternative quotation as a negotiation lever. You do not need to switch—you just need to demonstrate that you have evaluated alternatives. Microsoft's negotiating authority increases dramatically when they perceive competitive threat.

Volume Commitment Leverage

If your organisation has growth plans (hiring 30 percent more users, launching a new line of business requiring new products), use this visibility to negotiate lower discounts today. Microsoft will accept tighter margins now if they see multiyear volume growth ahead.

Multi-Year Terms

Committing to a four or five-year EA term (versus the standard three years) typically unlocks an additional 1 to 2 percentage points of discount. This is valuable if your forecast confidence is high and you do not anticipate major business disruption in the extended term.

Bundling Leverage

If you are purchasing both on-premises products (Windows, Office, servers) and cloud services (Azure, Microsoft 365), you have leverage to negotiate a blended discount rate. Account teams are incentivised to grow cloud spend, so they will compress margins on core products to win larger cloud commitments.

Implementation: Getting the Agreement Right

Once you have decided on an agreement type, ensure implementation does not create surprises.

For EA implementations, begin licence reconciliation 90 days before the agreement starts. Audit your current user count, device count, and product deployments. Align these actual numbers with your EA licence positions to avoid underestimating true-up exposure on day one of the agreement.

For MCA-E implementations, map your service consumption to expected monthly spend. Build a forecast model showing expected monthly consumption by service (Azure compute, storage, Microsoft 365 per-user cost, security products). Compare this forecast to your committed amount. If your forecast exceeds commitment by more than 10 percent, renegotiate the commitment before signing.

For CSP implementations, establish a monthly review meeting with your CSP partner to confirm billing accuracy and plan future utilisation. CSP relationships are most healthy when both parties have transparent monthly communication.

Next Steps: Building Your Microsoft Strategy

Your Microsoft agreement choice will shape your technology costs and operational flexibility for years. This decision warrants rigorous analysis and negotiation preparation.

Redress Compliance works with procurement teams to evaluate all three agreement types, model real-world costs, and develop negotiation strategies that maximise value. Our assessment programme includes a confidential benchmarking analysis comparing your current agreement terms against market rates for your organisation size and industry.

If you are within 180 days of a Microsoft licence renewal, we recommend engaging now. Renewal negotiations are most productive when you have 120 plus days to evaluate alternatives, build competitive tension, and structure the final negotiation. Waiting until 30 days before renewal severely constrains your negotiating position.

Our Microsoft advisory services include renewal preparation, competitive alternative development, and on-call support during final negotiation. We also provide Vendor Shield, which gives you continuous access to our Microsoft licensing experts as your workload or business situation changes.

Contact our team to discuss your current Microsoft agreement and explore whether EA, MCA-E, or CSP best fits your strategic and financial requirements.