Microsoft EA Pricing & Cost Structure Guide

Understanding Microsoft EA Pricing in 2026: The Complete Enterprise Guide to Levels, Tiers, Cost Calculation, and How to Negotiate Beyond List Price

How Volume Levels A–D Worked, Why Microsoft Eliminated Them, What the New Pricing Reality Means for Your Organisation, and the Data-Driven Strategies That Still Deliver 10–20% Below List on Every SKU

February 202630 min readRedress Compliance Advisory
1

Executive Summary — Why Understanding EA Pricing Mechanics Is Worth Millions

+

Microsoft Enterprise Agreement pricing is deliberately complex. The combination of volume levels, per-SKU rates, on-premises vs cloud models, Azure consumption commitments, and layered discounting creates an environment where the difference between an informed buyer and an uninformed buyer is typically 10–20% of total contract value — representing $500K to $5M+ over a 3-year term for a mid-to-large enterprise.

The November 2025 elimination of volume pricing levels B, C, and D for online services has fundamentally changed the EA pricing landscape. Previously, larger organisations received automatic price reductions based on user count. Now, every organisation starts at Level A (list price) regardless of size. Microsoft positions this as transparency. In practice, it shifts the savings burden entirely onto the customer's ability to negotiate — and organisations that do not negotiate pay significantly more than those that do.

This guide provides the complete framework for understanding how EA pricing works: the historic volume tier system and why it mattered, the new pricing reality after the 2025 changes, how costs are calculated per SKU, the critical differences between on-premises, cloud, and Azure pricing models, the factors that determine your negotiable discount range, and the data-driven strategies that consistently deliver below-list pricing.

Pricing Knowledge GapCommon ConsequenceFinancial Impact (5,000-seat, 3-year EA)How This Guide Helps
Not understanding per-SKU pricing breakdownAccepting bundled TCV without unit cost visibility$200K–$500K in hidden overpricingSection 3: Per-SKU cost decomposition
Assuming Level A is the only price availablePaying full list price without requesting discount$500K–$2M above achievable priceSections 6–7: Discount benchmarks and negotiation
Not distinguishing on-prem vs cloud pricingMisallocating budget; missing SA benefit value$100K–$300K in misunderstood costSection 4: Pricing model comparison
Poor Azure commitment sizingUnder-consuming (wasted commitment) or overage billing$100K–$500K in sub-optimal Azure spendSection 5: Azure MACC mechanics
No discount benchmarkingAccepting Microsoft's first offer as reasonable5–15% above market rateSection 7: Benchmark targets by deal size
2

The Historic Volume Level System — How A–D Pricing Worked and What It Meant

+

For over two decades, Microsoft's EA programme used a four-tier volume pricing system that automatically adjusted per-user costs based on the number of licensed users. Understanding this system is essential for any organisation that had a pre-2025 EA, because it provides the baseline against which your new pricing should be evaluated.

1. The Four Levels:

Level A was the entry-level pricing tier for the smallest EA-eligible organisations (historically requiring a minimum of 250 users or devices for EA qualification). Level A pricing was essentially list price with minimal automatic discount — the baseline from which all other levels were discounted. Level B applied to organisations with 250–2,399 qualifying users, providing a moderate built-in discount (typically 5–8% below Level A on cloud services). Level C covered 2,400–5,999 users with a larger volume discount (typically 8–12% below Level A). Level D was the deepest discount tier for organisations with 6,000 or more users (typically 10–15% below Level A).

2. How Levels Were Determined:

The pricing level was determined by the total number of qualifying users or devices across the organisation — not just the number of licences purchased for a specific product. An organisation with 8,000 employees would qualify for Level D pricing across its entire EA, even if it only purchased 3,000 M365 licences. The level was set at the start of the EA term and remained fixed for the 3-year duration. This meant that once you qualified for Level C or D, every product in your EA benefited from that tier's discount for the entire term.

3. The Financial Impact of Levels:

The difference between Level A and Level D was substantial. On a 5,000-seat M365 E5 agreement, the Level D automatic discount (approximately 12%) represented roughly $1.2M in savings over 3 years compared to Level A pricing — and that was before any additional negotiated discounts. Many large enterprises took these level-based savings for granted, assuming they were a permanent feature of the EA programme.

EA LevelUser Count RangeApproximate Automatic Discount (Cloud Services)Example: M365 E5 Per-User/Month3-Year Cost (5,000 Seats)Status (2026)
A (Baseline)<250 usersNone — list price$57.00$10,260,000Active — default for all customers
B250–2,399~5–8%~$53.00–$54.15~$9,540,000–$9,747,000Retired November 2025
C2,400–5,999~8–12%~$50.16–$52.44~$9,028,800–$9,439,200Retired November 2025
D6,000+~10–15%~$48.45–$51.30~$8,721,000–$9,234,000Retired November 2025

4. Important Exceptions:

The tier retirement applies only to commercial online/cloud services. On-premises licence pricing retains the traditional volume discount structure (for now). Government (GCC) and Education programmes are excluded from the change and continue with their own pricing structures. Azure consumption pricing was never directly tied to A–D levels and remains unchanged.

3

How EA Pricing Is Calculated — Per-SKU, Per-User, Per-Year Decomposition

+

Understanding exactly how Microsoft calculates EA costs is the foundation for effective negotiation. Every EA price can be decomposed into individual components that should be visible and verifiable.

1. The Core Formula:

For each product (SKU) in the EA: Annual Cost = Per-User-Per-Year Price × Number of Users. The 3-Year Total Contract Value (TCV) = Sum of (Annual Cost × 3) for all SKUs. Microsoft or your Licensing Solution Provider (LSP) typically presents the TCV as a single number. This bundled presentation obscures the per-unit economics and makes it difficult to identify which products are priced competitively and which are overpriced.

2. Breaking Down the TCV:

Always request a line-item breakdown showing: every SKU in the agreement, the quantity (number of users or devices), the per-unit annual price, the per-unit monthly price (for comparison with published list prices), any discount applied and the discount percentage, and the annual and 3-year subtotal per SKU. This decomposition allows you to compare each SKU's price against the published list price, benchmark individual products against market rates, identify products where the discount is insufficient, and spot products that may have been added at list price while others were discounted (a common Microsoft tactic — discounting the high-volume products to lower the headline rate while keeping add-ons and smaller products at full list).

3. Example Decomposition:

SKUQtyList Price (Per User/Month)Quoted Price (Per User/Month)Discount %Annual Cost3-Year Cost
Microsoft 365 E53,000$57.00$49.0014%$1,764,000$5,292,000
Microsoft 365 E32,000$36.00$31.0014%$744,000$2,232,000
Microsoft 365 F35,000$8.00$7.506%$450,000$1,350,000
Copilot for M365500$30.00$30.000%$180,000$540,000
Teams Phone Standard2,000$8.00$8.000%$192,000$576,000
Power BI Pro500$10.00$10.000%$60,000$180,000
Total$3,390,000$10,170,000

In this example, the headline discount looks reasonable (14% on the major M365 SKUs), but the add-on products (Copilot, Teams Phone, Power BI Pro) are at full list price with zero discount. These add-ons represent $1.3M over 3 years — a significant cost centre that is completely un-negotiated. A savvy buyer would target 10–15% on the add-ons as well, potentially saving an additional $130K–$195K over the term.

What Procurement Must Do — Demand the Line-Item Breakdown

Never accept a bundled TCV as the basis for negotiation: If Microsoft or your LSP presents a single total contract number, request the full per-SKU, per-unit breakdown before any commercial discussion. You cannot negotiate what you cannot see.

Check every add-on and secondary SKU: Microsoft's discounting strategy often focuses on the high-volume core SKUs while leaving add-ons at list. Ensure your discount targets cover the entire product portfolio, not just the headline products.

4

On-Premises vs Cloud Pricing Models — Two Different Economies Under One Agreement

+

A Microsoft EA can contain both on-premises perpetual licences and cloud subscriptions, and these two models work very differently in terms of cost structure, ownership, and negotiation dynamics.

1. On-Premises: Perpetual Licence + Software Assurance

On-premises products (Windows Server, SQL Server, Office on-premises, System Center, CALs) are licensed as perpetual purchases paid over the 3-year EA term. The annual EA payment covers approximately one-third of the perpetual licence cost plus Software Assurance (SA) at approximately 25% of the licence value per year. At the end of the EA, you own the licence perpetually (regardless of whether you continue SA). SA provides upgrade rights (to new versions released during the SA period), deployment planning services, training vouchers, Azure Hybrid Benefit, licence mobility, and disaster recovery rights.

On-premises pricing retains the traditional volume discount structure — the A–D tier retirement does not apply to on-premises licences. This means larger organisations still receive automatic volume discounts on on-premises products, and additional negotiated discounts can be layered on top.

2. Cloud: Subscription Only

Cloud products (Microsoft 365, Office 365, Dynamics 365, Power Platform, EMS, Defender) are pure subscriptions. You pay per user per year and do not own the software. If you stop paying, access ends. The subscription includes hosting, maintenance, support, and automatic quarterly updates. There is no separate SA component because the subscription inherently provides continuous access to the latest version. Cloud pricing starts at Level A (list price) for all organisations post-November 2025. Any discount must be individually negotiated. The EA provides price protection (your negotiated rate is locked for the 3-year term), which is valuable given Microsoft's pattern of annual list price increases (typically 5–15% per cycle).

3. The Hybrid EA — Where Complexity Creates Opportunity:

Most enterprise EAs contain both on-premises and cloud products, creating a hybrid cost structure. This hybrid nature creates negotiation opportunity: Microsoft values cloud migration highly (it drives recurring revenue and strategic metrics), so offering to move from on-premises to cloud equivalents can unlock additional discounts or migration credits. Conversely, if you are retaining on-premises products, you have leverage to negotiate better SA rates or perpetual licence pricing.

DimensionOn-Premises (Perpetual + SA)Cloud (Subscription)Implication
OwnershipYou own the licence perpetuallyYou rent access; stopping payments ends accessOn-prem has lower long-term lock-in risk
Cost modelCapEx + OpEx (licence amortised + SA annually)Pure OpEx (annual subscription)Budget and accounting treatment differs
Volume pricing (post-2025)A–D tiers still applyAll at Level A; discount must be negotiatedOn-prem retains automatic volume discounts
Updates and upgradesSA provides upgrade rights; must install yourselfAutomatic quarterly updates includedCloud is operationally simpler
Price protectionSA rate typically fixed for EA termSubscription rate locked for EA termBoth provide term-based price lock
End-of-term optionsKeep licences; optionally renew SAMust renew subscription or lose accessOn-prem provides more exit flexibility
Microsoft's strategic preferenceDeemphasised; lower Microsoft priorityStrongly preferred; key growth metricLeverage: offering cloud adoption for discounts
5

Azure Pricing Within the EA — MACC, Consumption, and Commitment Mechanics

+

Azure pricing operates on a fundamentally different model from the per-user licensing that covers M365 and other cloud services. Understanding Azure's EA mechanics is essential because Azure often represents 30–60% of total EA value for cloud-mature organisations.

1. Microsoft Azure Consumption Commitment (MACC):

The MACC is a financial commitment to consume a minimum amount of Azure services over a defined period (typically aligning with the EA term). In exchange for the commitment, Microsoft provides a discount off pay-as-you-go (PAYG) Azure rates. The MACC is not a prepayment for specific services — it is a commitment to reach a minimum consumption threshold. If you consume less than the committed amount, you still owe the full commitment. If you consume more, overage is billed at your negotiated rates (which may or may not be the same as your committed rates — verify this in the contract).

2. MACC Discount Mechanics:

MACC discounts vary by commitment size and negotiation. Typical ranges: $500K–$1M annual commitment may yield 5–10% discount off PAYG rates, $1M–$5M may yield 8–15%, and $5M+ commitments can achieve 12–20% or more. These discounts are not published — they are entirely negotiated. The discount applies to Azure consumption meters (compute, storage, networking, PaaS services). Some services are excluded from MACC eligibility (third-party marketplace purchases, certain preview services). Always verify which services are MACC-eligible and which are not.

3. Azure Was Never on the A–D Tier System:

Unlike M365, Azure pricing was never directly tied to the A–D volume levels. Azure has always been priced on a flat global rate card with negotiated discounts based on commitment size. The November 2025 tier elimination does not change Azure pricing mechanics. Azure discounts continue to be individually negotiated based on commitment value, workload type, competitive alternatives, and Microsoft's strategic priorities.

4. Optimising Azure Commitment Sizing:

Setting the right MACC level is critical. Over-committing means paying for consumption you do not use (wasted spend). Under-committing means paying PAYG rates for usage above the commitment (potentially higher cost). The optimal MACC is 90–95% of projected consumption — close enough to maximise the discount without significant over-commitment risk. Build the commitment based on 12–18 months of historical consumption data, plus known new workload migrations, minus projected optimisation savings (right-sizing, reserved instances).

MACC Annual CommitmentTypical Discount Range3-Year Savings vs PAYGRisk LevelBest For
$250K–$500K3–7%$22K–$105KLowOrganisations early in Azure adoption
$500K–$1M5–10%$75K–$300KLow–MediumMid-size Azure estates with predictable consumption
$1M–$5M8–15%$240K–$2.25MMediumEnterprise cloud-first organisations
$5M+12–20%$1.8M–$6M+Medium–High (if over-committed)Large enterprises with major Azure footprints
6

Factors That Determine Your Negotiable Discount — Beyond the List Price

+

With volume tiers eliminated, every discount on cloud services must be individually negotiated. Understanding the factors that influence Microsoft's willingness to discount helps you position your negotiation for maximum impact.

1. Deal Size and Total Contract Value:

Larger deals command larger discounts. Microsoft's internal discount authorisation thresholds are tied to TCV. A $2M EA gives the account team limited discount authority. A $10M+ EA escalates to regional or corporate deal desks with significantly more flexibility. Even within the same TCV range, bundling more products (M365 + Azure + Dynamics + security) gives Microsoft a larger strategic win, unlocking additional discount capacity.

2. Strategic Product Adoption:

Microsoft prioritises cloud adoption metrics. Committing to strategically important products — Copilot, Defender, Purview, Teams Phone, Power Platform — gives you negotiation leverage because Microsoft values adoption of these products for competitive positioning, analyst perception, and market share growth. Offering to pilot or deploy strategic products can unlock 15–30% introductory discounts on those products, plus improved pricing on core M365 SKUs.

3. Competitive Pressure:

The most effective negotiation lever is credible competitive alternatives. Google Workspace for productivity, AWS/GCP for cloud infrastructure, Slack for collaboration, CrowdStrike/Palo Alto for security, Salesforce for CRM — all create pricing pressure on Microsoft. The key word is credible: Microsoft's sales team can tell the difference between a genuine competitive evaluation and a bluff. Conducting a real proof-of-concept with a competitor, even on a limited scope, creates the credibility that unlocks Microsoft's best pricing.

4. Customer Segment and Profile:

Government and education customers operate under separate pricing programmes with built-in discounts. Commercial customers who are high-profile brands, early adopters, or reference-able accounts may receive additional consideration. Microsoft also values customers who will provide case studies, speak at events, or participate in advisory boards — these non-financial contributions can be traded for pricing concessions.

5. Microsoft's Fiscal Calendar:

Microsoft's fiscal year ends June 30. Deals closed in Q4 (April–June) benefit from sales team quota pressure and are more likely to receive aggressive pricing. Renewals that can be timed to align with Microsoft's fiscal year end often achieve 5–10% better outcomes than those negotiated in Q1 or Q2.

FactorLow LeverageHigh LeveragePotential Discount Impact
Deal size (TCV)$1M–$3M$10M++3–8% additional discount at higher TCV
Strategic product adoptionCore M365 only; no new productsCopilot, Defender, Azure, Dynamics commitment+5–15% on strategic products; +2–5% on core
Competitive pressureNo alternatives evaluated; Microsoft onlyActive Google Workspace or AWS POC+5–15% when competition is credible
Fiscal timingQ1–Q2 (July–December)Q4 (April–June; fiscal year end)+3–8% from quota pressure
Customer profileStandard commercial customerHigh-profile brand; referenceable; early adopter+2–5% for strategic value
7

Discount Benchmarks by Deal Size — What Organisations Like Yours Are Actually Paying

+

One of the most valuable pieces of information in EA negotiation is knowing what comparable organisations are paying. Microsoft's pricing is opaque by design — they rely on information asymmetry to maintain margin. Breaking that asymmetry with benchmark data transforms the negotiation.

1. Cloud Services (M365, Dynamics 365) Discount Benchmarks:

Organisation SizeCore M365 SKUs (E3/E5)Add-on ProductsOverall Blended DiscountNotes
500–2,000 users5–10% off list0–5% off list4–8%Limited leverage; focus on competitive pressure
2,000–5,000 users8–14% off list5–10% off list7–12%Moderate leverage; bundle for better rates
5,000–15,000 users12–18% off list8–15% off list10–16%Strong leverage; should recover historic Level C/D pricing
15,000–50,000 users15–22% off list10–18% off list13–20%Significant leverage; demand deal desk involvement
50,000+ users18–25%+ off list15–22%+ off list16–23%+Maximum leverage; corporate-level deal approval

2. On-Premises Licence Discount Benchmarks:

On-premises products (Windows Server, SQL Server, CALs) retain volume tier pricing plus negotiated discounts. Typical achieved discounts on on-premises products range from 10–15% for Level A/B organisations to 20–35% for Level C/D organisations, with the automatic tier discount plus an additional negotiated component. SQL Server Enterprise Edition, in particular, is one of the most deeply discounted Microsoft products — organisations with large SQL estates routinely achieve 25–40% off list.

3. What These Benchmarks Mean for Your Negotiation:

If Microsoft's initial offer is at or near list price (0–5% discount), they are testing your willingness to negotiate. For a mid-to-large enterprise (2,000+ seats), achieving 10–15% on core M365 SKUs is a reasonable target and well within Microsoft's discount authority. If you are offered less than these benchmarks, it means either your negotiation strategy needs strengthening (competitive pressure, fiscal timing, strategic product commitment) or your LSP/reseller is retaining margin that should flow to you. Ask your LSP to disclose their Microsoft-provided pricing — some LSPs add margin on top of the EA pricing they receive from Microsoft.

What the CFO Should Know — Discount Expectations

Microsoft's first offer is never their best offer: Initial EA quotes typically include 0–5% discount. Expect 2–4 rounds of negotiation to reach market-rate pricing. Budget the time for proper negotiation — rushing to sign at the first offer can cost hundreds of thousands of dollars.

The November 2025 tier changes increase the importance of negotiation: Organisations that previously relied on automatic Level C/D discounts must now explicitly negotiate to achieve equivalent pricing. Without negotiation, you will pay 10–15% more than before for the same products.

8

Microsoft's Internal Margin and Deal Approval Mechanics — How They Price and Approve Discounts

+

Understanding how Microsoft's internal pricing and approval process works gives you a strategic advantage in negotiation — it helps you calibrate your requests, understand the account team's constraints, and identify when to escalate.

1. The Discount Authorisation Hierarchy:

Microsoft's account teams have tiered discount authority. The account executive (AE) typically has authority to offer 5–10% on standard cloud products without additional approval. Discounts of 10–15% may require approval from the AE's sales manager or the regional sales leader. Discounts above 15–20% typically require deal desk or corporate pricing approval. Exceptional discounts (20%+) require executive-level approval and are reserved for strategically important deals. When Microsoft says they cannot offer a larger discount, it often means the AE does not have the authority — not that the discount is impossible. Requesting that the deal be escalated to the deal desk or that a senior Microsoft executive joins the discussion can unlock additional discount capacity.

2. What Motivates Microsoft's Pricing Decisions:

Microsoft's sales teams are measured on several metrics beyond pure revenue: cloud consumption growth (Azure monthly consumption revenue is a key metric), cloud seat adoption (M365 and Dynamics seat counts), strategic product penetration (Copilot, Defender, Purview adoption), competitive wins (displacing Google, AWS, Salesforce), and customer retention (preventing downsizing or departures). Understanding which metrics your deal addresses helps you position requests. If your deal involves significant Azure consumption growth, frame your discount request in terms of how it enables you to consume more Azure. If you are adopting Copilot, frame it as an adoption win that Microsoft can reference.

3. The Role of the Licensing Solution Provider (LSP):

In most markets, EA transactions flow through an LSP (reseller). The LSP receives pricing from Microsoft and may add margin before presenting to you. This layered structure means the price you see may not be Microsoft's price — the LSP's margin is embedded. Ask your LSP to provide full transparency on their margin. Some LSPs operate on a fixed administrative fee model (which is more customer-friendly), while others retain a percentage of the deal value (which increases your cost). If the LSP's margin is opaque, consider requesting direct pricing from Microsoft for comparison, or engage an independent advisory firm to benchmark the LSP's offer.

4. Strategic Value vs Pure Margin:

Microsoft is sometimes willing to sacrifice margin on specific products to drive strategic outcomes. Copilot, for example, is a product Microsoft wants to see widely adopted — they may offer significant introductory discounts (20–30%) to secure adoption wins. Security products (Defender, Purview) are products where Microsoft is competing aggressively against incumbents — competitive displacement opportunities may unlock exceptional pricing. Azure migrations from AWS or GCP are strategically valuable to Microsoft and can command migration credits or consumption commitments at below-standard rates. Identify where your deal aligns with Microsoft's strategic priorities and use those alignment points to request better pricing on those specific products.

Discount Request LevelLikely Approval AuthorityTypical AchievabilityHow to Unlock
0–5%Account executive (standard authority)Automatic — any customer who asksSimply request it
5–10%AE with manager approvalAchievable for most enterprise dealsDemonstrate deal value; bundle products
10–15%Regional sales leaderAchievable with competitive pressure or strategic valueCompetitive evaluation; large TCV; strategic products
15–20%Deal desk / corporate pricingAchievable for large or strategically important dealsExecutive escalation; credible competitive threat; fiscal timing
20%+Executive approval (VP-level)Reserved for exceptional circumstancesCompetitive win; massive TCV; strategic reference account
9

Negotiation Strategies for Achieving Below-List Pricing — The Practical Playbook

+

With the theoretical framework established, these are the practical negotiation strategies that consistently deliver below-list pricing on Microsoft EA agreements.

1. Establish Your Baseline Before Engaging Microsoft:

Before receiving any Microsoft quote, build your own pricing model. Identify every SKU you need and the quantity. Calculate the total at published list prices (Level A). Research benchmark discounts for your organisation size and deal type. Set target pricing per SKU based on benchmarks. Calculate your target TCV. Present this target to Microsoft as your opening position, not the other way around. This prevents anchoring on Microsoft's first offer (which will always be higher than your target).

2. Create Credible Competitive Pressure:

The single most effective negotiation lever is a credible alternative. Conduct a genuine evaluation of Google Workspace for productivity (even if you ultimately prefer Microsoft). Request pricing from AWS or GCP for Azure workloads. Evaluate CrowdStrike or Palo Alto as alternatives to Defender. The evaluation does not need to be comprehensive — even a limited proof-of-concept creates the credibility that unlocks Microsoft's competitive pricing programmes. Inform your Microsoft account team about the evaluation. Microsoft has specific competitive response pricing programmes that are only activated when a genuine competitive threat exists.

3. Bundle Strategically:

Bundling more products into a single EA increases TCV and gives Microsoft a larger strategic win, which unlocks additional discount capacity. However, do not add products you do not need just to inflate the deal. Instead, consolidate existing Microsoft purchases from multiple channels (CSP, MOSP, separate agreements) into the EA. Add products that are genuinely on your roadmap (Copilot, Defender, Azure migration). Present the consolidated deal as a single large commitment, maximising TCV-based discount leverage.

4. Time the Negotiation:

Microsoft's fiscal year ends June 30. Deals closed in Q4 (April–June) benefit from quota pressure. If your EA renewal is naturally in Q4, use this timing advantage. If not, explore whether you can accelerate or defer the renewal to align with Q4. Even a 1–2 month shift can be worthwhile if it moves the close date into Microsoft's high-pressure sales period.

5. Negotiate the Full Product Portfolio:

Do not accept discounts only on core M365 SKUs while add-ons remain at list price. Negotiate discounts across every SKU in the agreement. Microsoft's standard tactic is to focus discount conversation on the highest-volume products while keeping secondary products at full margin. Insist that the discount percentage applies broadly, or negotiate individual discounts for each product category.

StrategyEffort LevelTypical Discount ImpactWhen to Use
Demand line-item breakdown + target pricingLow+3–5% (prevents anchoring on Microsoft's first offer)Always — first step in every negotiation
Competitive evaluation (Google, AWS, etc.)Medium+5–15% (unlocks competitive response pricing)When deal >$2M or discount target >10%
Strategic product adoption commitmentLow–Medium+5–15% on strategic products; +2–5% on coreWhen Copilot, Defender, or Azure are on roadmap
Fiscal year end timingLow (if timing aligns)+3–8%When renewal can be aligned to April–June
Multi-product bundling / consolidationMedium+3–5% (from increased TCV leverage)When multiple Microsoft channels can be consolidated
Executive escalation / deal desk engagementLow+3–8% (unlocks higher approval authority)When AE's initial offer is below benchmark
10

Final Action Plan — 10-Step EA Pricing Analysis Checklist

+

This consolidated checklist provides the step-by-step framework for analysing and negotiating Microsoft EA pricing.

#ActionOwnerTimelineKey Outcome
1Gather current Microsoft list prices for every SKU in scope; build complete product and quantity listProcurement / ITWeek 1–2Complete list-price baseline for all products
2Calculate total at list price (Level A); this is the maximum you should pay under any scenarioProcurementWeek 2Level A ceiling established; no EA should exceed this
3Compare previous EA pricing to current list; quantify the impact of tier elimination on your renewal costProcurementWeek 2–3Gap analysis showing cost increase without negotiation
4Research discount benchmarks for your organisation size and deal type using advisory data or peer networksProcurement / AdvisoryWeek 3–4Target discount percentage per SKU and overall blended target
5Build target pricing model: per-SKU pricing at benchmark discount levels; calculate target TCVProcurementWeek 4Data-driven negotiation target — your opening position
6Identify negotiation levers: competitive alternatives, strategic product adoption, fiscal timing, bundling opportunitiesProcurement / IT LeadershipWeek 4–6Leverage strategy aligned with Microsoft's priorities
7Initiate competitive evaluation if deal warrants it; request Google Workspace, AWS, or alternative pricingIT / ProcurementWeek 4–8Credible competitive pressure; activates Microsoft's competitive response
8Engage Microsoft with target pricing; request line-item quote with per-SKU, per-unit breakdownProcurementWeek 6–8Microsoft's initial offer to compare against targets
9Negotiate across 2–4 rounds; escalate to deal desk if initial offers are below benchmark; use all identified leversProcurement / IT Leadership / AdvisoryWeek 8–14Final pricing at or below benchmark targets
10Document final pricing per SKU; verify in Microsoft portals after signing; establish monitoring for the EA termProcurement / IT AdminAt signing + Week 1 post-signingVerified agreement; monitoring in place; next renewal preparation begins

Organisations that follow a structured pricing analysis and negotiation framework consistently achieve 10–20% below list price on Microsoft EA agreements — even in the post-tier-elimination environment. The savings come from understanding the per-SKU cost structure, benchmarking against market rates, creating credible competitive pressure, leveraging Microsoft's strategic priorities, and timing the negotiation to maximise discount authority.

For enterprises analysing EA pricing, preparing for renewal negotiation, or seeking to understand how the November 2025 tier elimination affects their Microsoft costs, Redress Compliance provides independent advisory with deep expertise in Microsoft's pricing mechanics, discount benchmarking, and the negotiation strategies that deliver below-list outcomes.

Frequently Asked Questions

What are Microsoft EA pricing levels A through D?+

Levels A through D were Microsoft's historic volume pricing tiers for Enterprise Agreements. Level A was the baseline (list price) for the smallest organisations. Levels B, C, and D offered progressively deeper automatic discounts for larger user counts: B for 250–2,399 users (~5–8% discount), C for 2,400–5,999 (~8–12%), and D for 6,000+ (~10–15%). As of November 2025, Levels B through D have been retired for cloud services, and all customers start at Level A.

Why did Microsoft eliminate volume pricing levels?+

Microsoft positions the change as simplification and transparency. In practice, the elimination removes automatic discounts that larger organisations previously received, increasing Microsoft's cloud margin. Every discount must now be individually negotiated rather than automatically applied based on user count. This benefits Microsoft commercially while shifting the burden of achieving fair pricing entirely to the customer.

Does the tier elimination affect on-premises licence pricing?+

No. The A–D volume tier retirement applies only to commercial online/cloud services (M365, Office 365, Dynamics 365, etc.). On-premises perpetual licence pricing retains the traditional volume discount structure. Government and Education programme pricing is also unaffected by the change.

How is Microsoft EA pricing calculated per SKU?+

Each SKU in the EA has a per-user-per-year price multiplied by the number of users. The 3-year Total Contract Value is the sum of all SKU annual costs multiplied by 3. Always request a line-item breakdown showing per-SKU quantity, per-unit price, discount percentage, and subtotals. Never negotiate based on a bundled TCV alone — it obscures overpricing on individual products.

What discount can I realistically achieve on my EA?+

Discount achievability depends on deal size, competitive pressure, strategic product adoption, and fiscal timing. Typical benchmarks: 500–2,000 users can achieve 5–10% on core M365 SKUs; 2,000–5,000 users 8–14%; 5,000–15,000 users 12–18%; 15,000–50,000 users 15–22%; 50,000+ users 18–25% or more. Add-on products typically receive 3–8% less discount than core SKUs unless specifically negotiated.

How does Azure pricing work within an EA?+

Azure uses a consumption-based model with a Microsoft Azure Consumption Commitment (MACC). You commit to a minimum consumption amount in exchange for discounted rates off pay-as-you-go pricing. Typical discounts range from 5–10% for $500K–$1M commitments to 12–20% for $5M+ commitments. Azure was never on the A–D tier system and is unaffected by the November 2025 changes.

What is the difference between on-premises and cloud pricing in an EA?+

On-premises products are perpetual licences with Software Assurance, paid over the EA term. You own the licence indefinitely. Cloud products are subscriptions — you rent access and lose it if payments stop. On-premises pricing retains volume tier discounts. Cloud pricing starts at Level A (list) for all organisations post-November 2025. Cloud includes hosting and updates; on-premises does not.

How do I know if my LSP is adding margin to my EA pricing?+

Ask your LSP to disclose their margin structure. Some LSPs operate on a fixed administrative fee (more transparent), while others retain a percentage of deal value (increasing your cost). You can request direct pricing from Microsoft for comparison, or engage an independent advisory firm to benchmark the LSP's offer against Microsoft's actual pricing.

When is the best time to negotiate a Microsoft EA?+

Microsoft's fiscal year ends June 30. Deals closed in Q4 (April–June) benefit from sales team quota pressure and are 5–10% more likely to achieve aggressive pricing than deals negotiated in Q1–Q2. If your renewal timing is flexible, aligning the close date with Microsoft's fiscal year end can deliver meaningful additional savings.

How do I recover the discounts I lost from tier elimination?+

To recover historic Level B/C/D equivalent discounts, you must now explicitly negotiate. Build a target pricing model based on your previous EA's effective per-user rates. Present this to Microsoft as your benchmark and make clear that you expect equivalent or better pricing on renewal. Create competitive pressure (Google Workspace evaluation), bundle strategically, time the negotiation for fiscal year end, and commit to strategic products to maximise discount leverage.

More in This Series: Microsoft Advisory Services

This article is part of our Microsoft Advisory Services pillar. Explore related guides:

⭐ Microsoft Advisory Services — Complete Guide → Microsoft EA Pricing Changes 2025 → Strategies to Maximise Your Microsoft EA Discount → Benchmarking Microsoft EA Discounts → Eliminating Redundant Microsoft Software → Microsoft EA Renewal Strategies → Microsoft Contract Terms & Negotiation → After the Ink Dries: Post-Renewal Transition → Microsoft EA Optimisation Service → Microsoft Contract Negotiation Service → Microsoft Licensing Knowledge Hub →

Microsoft Tools & Resources

📋 Microsoft Assessment Tools 🛡️ Microsoft Audit Preparation Toolkit 🔒 All Audit Defence Kits (6) 📖 All Renewal Playbooks (7) 🏢 Enterprise Assessment Tools (12)

Need Help With Your Microsoft Licensing?

Redress Compliance has helped hundreds of enterprises negotiate better Microsoft EA, CSP, and Azure terms — typically saving 15–30% on renewals.

Microsoft Contract Negotiation → Microsoft EA Optimization →

100% vendor-independent · No commercial relationships with any software vendor