Microsoft Licensing Models Explained

Introduction: Why Your Licensing Model Matters in 2026

Five years ago, Microsoft licensing felt like a simple binary choice: Enterprise Agreement or partner-led Cloud Solution Provider. Not anymore. Today, enterprises face five distinct licensing pathways, each with radically different economics, flexibility, and risk profiles. More importantly, Microsoft is actively pushing existing customers down specific paths—often the more profitable ones for Redmond.

The stakes are higher than ever. Global price increases are coming in July 2026, some plans rising by 33 percent. At the same time, Microsoft field teams are aggressively migrating customers from Enterprise Agreements to the newer Microsoft Customer Agreement (MCA-E), eliminating price protection in the process. Meanwhile, the cloud licensing market is fragmenting: new SKU tiers like E7 bundle capabilities that previously sold as standalone add-ons, making direct cost comparisons nearly impossible.

Your choice of licensing model will determine not just your annual spend, but your negotiation power, flexibility, and compliance risk for years to come. This guide walks through all five models, their mechanics, and the strategic decision framework you need to make an informed choice before your next renewal.

Enterprise Agreement (EA): The Traditional Foundation

The Enterprise Agreement remains the most common licensing vehicle for large Microsoft customers. It's a three-year fixed-term agreement with an annual "True-Up" mechanism, meaning you pay annually for what you consumed, not what you purchased upfront. This provides useful flexibility, but the commercial terms have shifted dramatically.

How EA True-Up Works

In an EA, you commit to an annual minimum spend in Year 1. Each year, Microsoft reconciles your actual consumption against that commitment. If you've consumed less, you lose the unspent amount—no rollover, no refund. If you've exceeded it, you pay true-up pricing on the overage. This structure incentivizes conservative initial purchases and creates annual renewal leverage for the buyer.

Historically, this mechanism protected buyers from overcommitting. Today, it's become a negotiation point: Microsoft field teams use true-up data from prior years to justify higher Year 2 commitments, often with limited discount improvement. The psychological pressure to "anchor" on last year's consumption is subtle but real.

EA Discount Structure: 10-20% (Down from 15-25%)

This is critical. Microsoft's standard EA discount band has narrowed significantly. Historically, volume discount tiers (Level A through Level D) created breakpoints where larger customers received better rates. Starting November 2025, Microsoft eliminated these fixed tiers for online services, moving to individualized discounts.

The practical effect: most large customers now see EA discounts in the 10-20 percent range. Only the largest accounts with exceptional leverage negotiate higher rates. If you're accustomed to 20-25 percent discounts, expect Microsoft to present 12-15 percent as their "standard offer." This is a meaningful compression that directly impacts your renewal economics.

Who Should Choose EA

EA remains the right fit if: you have predictable, stable consumption; you value the true-up mechanism for flexibility; you need three-year fixed pricing certainty; and you have sufficient scale to negotiate meaningful discounts. EA also remains the only model that preserves Software Assurance benefits, which still matter for on-premises products like Windows Server and SQL Server.

EA is increasingly a defensive choice, though. Customers renew into EA today primarily because they lack information about alternatives or because their existing Microsoft relationship is so embedded that switching feels risky.

Microsoft Customer Agreement Enterprise (MCA-E): The New Default

Microsoft is aggressively transitioning EA customers to the Microsoft Customer Agreement for Enterprise (MCA-E). This agreement represents a fundamental shift in Microsoft's commercial posture—and not in the buyer's favor.

Core Characteristics

Unlike EA's three-year fixed term, MCA-E is evergreen: there is no defined end date. Instead, either party can exit with 30 days' notice after an initial 12-month commitment. Microsoft presents this as flexibility; in practice, it's leverage transfer. You lose negotiation power because you can never credibly walk away at renewal—you're always 30 days from disconnection.

MCA-E eliminates Software Assurance entirely. This matters enormously for on-premises workloads. If you're running Windows Server, SQL Server, or Exchange Server, losing SA means losing Software Assurance benefits, including downgrade rights, license mobility, and replacement licenses. Microsoft's transition teams gloss over this point.

Most critically, MCA-E includes no price protection. Under EA, your Year 1 commit is locked for the contract period—Microsoft cannot raise per-unit pricing. Under MCA-E, Microsoft can increase prices month-to-month, constrained only by "reasonable notice." In practice, Microsoft has used this power aggressively. Customers signing MCA-E in early 2024 are seeing 15-25 percent price increases within 18 months.

Why Microsoft Loves MCA-E

From Microsoft's perspective, MCA-E is ideal. The evergreen nature eliminates the negotiation cycle—you never have a hard expiry date to walk away from. The lack of price protection turns the customer into a captive base for quarterly price increases. The elimination of SA revenue consolidation means more SaaS licensing revenue, which trades at higher multiples on Microsoft's balance sheet.

Microsoft field teams have explicit quotas to migrate EA customers to MCA-E. Your account team will frame it as "modernization" and "alignment with cloud-first strategy." What they won't say: this increases their recurring revenue potential and decreases your negotiating leverage.

When MCA-E Makes Sense

MCA-E can be rational if: you have zero on-premises workloads and zero need for Software Assurance; you genuinely need sub-annual contract flexibility; your consumption is highly unpredictable and you want to avoid true-up risk; and you've secured explicit price-protection guarantees in writing (rare). For most enterprises, MCA-E is a migration to make only under duress or with exceptional negotiating power to extract concessions.

Cloud Solution Provider (CSP) and New Commerce Experience (NCE)

CSP is Microsoft's channel model: you buy through a certified reseller partner, not directly from Microsoft. In 2023, Microsoft overlaid the New Commerce Experience (NCE) framework on CSP, fundamentally changing the mechanics.

NCE Pricing Model

NCE offers two commit options: monthly and annual. Monthly commits carry list price—no discount. Annual commits offer up to 5 percent discount off list price. This is a dramatic change from traditional CSP, where resellers negotiated far steeper discounts.

The intent is clear: Microsoft wants to prevent resellers from competing on price. The NCE framework is designed to make direct EA customers and partner-led NCE customers roughly price-equivalent, eliminating the partner discount advantage and making the channel irrelevant for price negotiation.

Flexibility and Lock-In

NCE monthly commits allow 72-hour cancellation windows. This appears flexible, but in practice, NCE agreements are far more restrictive than EA. You cannot make mid-contract SKU changes without abandonment. You cannot mix-and-match billing across subscriptions. You have strict change windows for quantity or SKU adjustments.

Annual commits eliminate the 72-hour window and lock you in for 12 months. Since the discount is capped at 5 percent, the financial incentive for annual commitment is marginal—you save roughly 5 percent on list price, but lose all flexibility.

When CSP/NCE Makes Sense

CSP/NCE is appropriate if: you're a smaller organization without EA-scale leverage; you genuinely need monthly billing flexibility (most don't); you're testing Microsoft cloud services before larger commitments; or you have an exceptional reseller relationship that provides strategic advisory value beyond pricing. For most established enterprises, CSP/NCE is a model of last resort—you'll pay list price or near-list, with minimal flexibility.

MPSA: The Legacy Model in Decline

Microsoft Products and Services Agreement (MPSA) was once a middle ground: smaller than EA, more flexible, used primarily for smaller accounts and specific workloads. Microsoft is actively winding down MPSA. No new MPSA agreements are being offered for online services. Existing MPSA customers are being pushed toward either EA (if they have scale) or MCA-E (if Microsoft wants to deemphasize their account).

If you currently hold an MPSA for Microsoft cloud services, expect aggressive migration outreach at renewal. Unless you have contractual protection preventing forced migration, plan to move to either EA or MCA-E within the next 18-24 months.

MPSA still exists for on-premises software (Windows, Office, etc.), but even there, Microsoft is de-emphasizing it in favor of EA or large MCA-E deals.

Microsoft 365 SKU Tiers: E1, E3, E5, and E7

Your choice of SKU dramatically impacts your total cost of ownership and the functionality available to your workforce. Microsoft's SKU strategy has also shifted significantly.

The SKU Stack: E1 → E3 → E5 → E7

E1 ($4-6/user/month) is the foundational tier: Teams, Exchange Online, SharePoint Online, basic governance. It's suitable for frontline workers and light users. Most enterprises skip E1 entirely for most users.

E3 ($12-16/user/month) adds advanced compliance, eDiscovery, advanced auditing, and advanced security features like advanced threat protection. E3 has historically been the "standard" tier for knowledge workers. It's where most organizations land without specific governance.

E5 ($20-28/user/month) adds advanced analytics, advanced AI features, and premium voice/telephony integration. E5 has been positioned as Microsoft's premium tier.

E7 (pricing varies, typically $40-60/user/month) is NEW and is Microsoft's new top-tier SKU. This is critical: do not assume E5 is the top tier. E7 bundles advanced AI capabilities, Copilot integration, advanced security intelligence, and compliance features that previously sold as separate add-ons or premium licenses. E7 is designed to be an all-in-one bundle for security-sensitive and AI-forward organizations.

E7 and the Add-On Consolidation Strategy

Historically, Microsoft sold premium features as SKU add-ons. A customer might buy E5 + Advanced Threat Protection + Advanced Auditing + Copilot Pro, totaling $50-70/user/month. E7 bundles these into one SKU at a fixed price point, reducing the customer's transparency into what they're actually paying for what capability.

More importantly, Microsoft field teams are aggressively pushing E5 customers toward E7 at renewal. The pitch: "You're already spending this much on add-ons. Why not consolidate into E7 and simplify your licensing?" In practice, E7 adoption eliminates leverage over individual feature pricing and locks customers into an all-or-nothing bundle.

Copilot Pricing: $30/Month Add-On (or Included in E7)

Microsoft Copilot (the generative AI assistant integrated into Microsoft 365) is available as a $30/user/month add-on for E1, E3, and E5 licenses. However, Copilot is included in E7. This creates a subtle but important pricing dynamic: once Copilot adoption reaches a critical mass in your organization, the per-user cost of moving to E7 approaches parity with E5 + Copilot add-ons, making E7 migration appear inevitable.

This is strategic. Microsoft is using Copilot as a gateway to consolidate customers into higher-value SKUs, especially E7.

Decision Framework: Choosing the Right Licensing Model

How do you decide between EA, MCA-E, and CSP/NCE? Your choice depends on three variables: scale, consumption stability, and whether you value on-premises software support.

Scale Considerations

If you have fewer than 300 Microsoft 365 users or fewer than $500,000 in annual Microsoft cloud spend, EA is unlikely to be available to you. Microsoft only offers EA to accounts with sufficient minimum spend. Below this threshold, CSP/NCE is your primary option.

If you have 300+ users or $500K+ annual spend, you qualify for EA. At this scale, compare EA discounts against MCA-E pricing—but factor in the price-protection loss and Software Assurance elimination from MCA-E.

If you have $2M+ annual Microsoft spend, you have genuine negotiating leverage. At this scale, you can negotiate either EA with solid discounts (15-20 percent) or demand explicit price-protection guarantees in MCA-E language before accepting it.

Consumption Stability

If your consumption is stable and predictable, EA's three-year fixed pricing and true-up mechanism are valuable. You lock in discounts and avoid surprise costs.

If consumption is volatile—rapid scaling, frequent SKU changes, uncertain user growth—MCA-E's month-to-month option appears attractive. But factor in the price-increase risk. Month-to-month flexibility has little value if Microsoft uses price increases to force you upward regardless.

On-Premises Dependency

If you run significant on-premises workloads (Windows Server, SQL Server, Exchange Server), you need Software Assurance. This alone makes EA the right choice. MCA-E's elimination of SA is disqualifying for hybrid environments.

Strategic Negotiation Considerations for Each Model

Negotiating EA: Focus on True-Up Risk and Discount Preservation

When renewing an EA, your leverage exists in two places: (1) true-up data, and (2) willingness to walk. If you've had minimal true-ups in past years, Microsoft cannot credibly argue you need a higher Year 1 commitment. Use historical consumption data to anchor your renewal commitment at actual consumption levels, not Microsoft's extrapolations.

Second, preserve the discount. If Microsoft offers 12 percent on renewal and you've historically received 18 percent, push back with data on competitive alternatives (including CSP/MCA-E pricing). Make clear that a meaningful discount reduction will force evaluation of other models. Most field teams have discretion to negotiate 1-3 percentage points above their initial offer.

Third, lock in your discount for the full three-year term. Don't accept annual discount reviews—this creates unnecessary renegotiation cycles and gives Microsoft annual leverage.

Evaluating MCA-E: Price Protection is Non-Negotiable

If Microsoft proposes MCA-E, do not accept the default evergreen language. Negotiate explicitly for price-cap guarantees: "List prices will not increase more than X percent annually for the first 24 months of this agreement." This is not standard MCA-E language, but it's negotiable if you have leverage.

Without price protection written into MCA-E, you're signing up for annual price ratchets. Plan for 10-15 percent annual increases after Year 1. This is not paranoia—this is what Microsoft has done with existing MCA-E customers.

Also negotiate a true exit clause. "30 days' notice" is theoretically flexible but operationally difficult. Try to negotiate 60-90 days' notice at the annual anniversary, so you have a genuine renegotiation window.

CSP/NCE: Accept List Price, Focus on Coverage and Support

In CSP/NCE, you're unlikely to negotiate discounts below the 5 percent cap for annual commits. Accept this. Instead, negotiate around coverage: What's included in your reseller's managed services? Do they offer quarterly business reviews? Will they provide consumption forecasting? These non-price elements often have more value than marginal discount negotiations.

Also negotiate for advance notice of price increases. NCE allows monthly price changes, but you can negotiate for 60 days' notice, giving you planning time.

The Q4 2026 Negotiation Window: Your Highest Leverage Point

Microsoft's fiscal year ends June 30. Q4 (April–June) is when Microsoft field representatives face the most intense quota pressure. This is your highest-leverage negotiation window.

If your renewal falls between April and June, you have genuine negotiating power. Microsoft's field teams would rather close deals at better terms than risk missing quota. Use this window aggressively:

• Request and win EA discounts above Microsoft's standard offer. Field teams have discretion for 2-3 points above their initial offer, and more if you're walking away otherwise.
• Demand longer commitment terms if you're going MCA-E. Use the quota pressure to negotiate a 24-month price protection guarantee.
• Consolidate fragmented agreements. If you have multiple EA or MCA-E agreements, use Q4 negotiations to consolidate into a single contract with better terms.
• Lock in E3 or E5 for longer-term users. If you anticipate E7 migration pressure, negotiate multi-year pricing locks on E3/E5 as alternative to E7 migration.

If your renewal falls in Q1-Q3, you have less leverage. Consider timing your renewal to coincide with Q4 if contractually possible. This is not standard, but it's worth requesting—Microsoft sometimes accommodates to move revenue into high-pressure quarters.

Looking Ahead: July 2026 Price Increases and Beyond

Global price increases are coming in July 2026. Some Microsoft 365 plans are increasing by up to 33 percent. This is significant and immediate.

If your EA or MCA-E renewal is after July 2026, these new prices become your baseline. If your renewal is before July 2026, lock in renewal agreements immediately. You'll freeze pricing for 12 months (EA) or secure written price-cap guarantees (MCA-E) before the increase takes effect.

This creates a narrow window: if your renewal is scheduled for August 2026 or later, negotiate to pull it forward to June 2026 or earlier. The cost of a 60-90 day acceleration pales beside 33 percent price increases.

Conclusion: Choose Strategically, Negotiate Aggressively

Your Microsoft licensing model is not a commodity decision—it's a strategic choice that shapes your annual spend, negotiating power, and operational flexibility for years. The shift from EA to MCA-E, the compression of EA discounts from 15-25 percent to 10-20 percent, and the introduction of E7 as a consolidation vehicle all signal Microsoft's intention to reduce buyer leverage and increase vendor lock-in.

Your response must be equally strategic. Understand your scale and consumption patterns. Choose the licensing model that maximizes your flexibility, not Microsoft's. Use Q4 negotiation windows to extract concessions. Lock in pricing before July 2026 increases take effect. And if Microsoft proposes MCA-E migration, do not accept it without explicit, written price-protection guarantees.

For most enterprises, EA remains the superior choice if you have the scale to qualify. It preserves Software Assurance, locks in discounts, and provides true-up flexibility. If you're forced into MCA-E, negotiate ruthlessly on price protection and exit terms before signing.

Ready to evaluate your specific licensing position? Download our Microsoft audit defence kit for a detailed cost-analysis framework and negotiation playbook tailored to your agreement type.