The Microsoft Enterprise Agreement is the cornerstone three-year licensing contract for large enterprises. This independent advisory explains EA structure, cloud-era pricing mechanics, true-up strategies, renewal negotiation best practices, and how to position your organisation for the best possible outcome when Microsoft comes knocking.
Part of our Microsoft Licensing Knowledge Hub. For renewal-specific guidance, see the Microsoft EA Renewal Preparation Toolkit.
A Microsoft Enterprise Agreement (EA) is a multi-year volume licensing programme designed for organisations with 500 or more users or devices. It bundles software and services under one contract, simplifying procurement and often reducing per-unit costs compared to ad-hoc purchasing.
| EA Feature | How It Works | Implication for Buyers |
|---|---|---|
| Three-Year Fixed Term | Prices locked at signing for full duration. Payments split into three equal annual instalments. | Budget predictability and protection against price increases, but locks you in for 36 months. |
| Software Assurance (SA) | Included for all licences. Grants rights to new versions, deployment planning services, training credits, and support incidents. | You are paying for SA. Make sure your organisation actually uses it. Unused SA benefits are a common source of waste. |
| Enterprise-Wide Scope | You agree to cover a "qualified" scope, typically all users or all devices, for core products like Windows and Office. | Ensures consistency but means licensing broadly, even for users who may not need every product. |
| Annual True-Up | Each anniversary, report additional users or devices added during the year and pay for additional licences. | True-ups only go up in a standard EA. You cannot reduce counts mid-term, even if headcount drops. |
| Perpetual vs. Subscription | Standard EA grants perpetual licences + SA. Enterprise Subscription Agreement (ESA) is subscription-only but allows downsizing at anniversaries. | ESA provides flexibility for shrinking organisations, but you own nothing when it ends. Choose based on risk profile. |
The EA is a commitment, not just a discount vehicle. Many enterprises think of the EA primarily as a way to get volume discounts. But it is equally a commitment that locks your Microsoft spend for three years. You cannot reduce licence counts mid-term in a standard EA, even if your workforce shrinks or you retire a system. This makes upfront planning crucial. The organisations that get the best outcomes are those who treat the EA as a strategic project, not a routine procurement event. See Microsoft Contract Terms & Negotiation.
Microsoft's enterprise licensing has evolved, and the Enterprise Agreement now centres on cloud services, particularly Microsoft 365 and Azure consumption commitments.
| Cloud Component | What It Covers | Key Pricing Consideration |
|---|---|---|
| Microsoft 365 E3 | Core productivity: Office apps, Exchange, Teams, SharePoint, Windows Enterprise, basic security (Intune, Entra ID P1). | Standard enterprise tier. List price ~$36/user/month. Sufficient for most knowledge workers. |
| Microsoft 365 E5 | Everything in E3 plus advanced security (Defender for Office/Endpoint), compliance (eDiscovery, DLP), analytics (Power BI), and Teams Phone. | ~50% more expensive (~$57/user/month list). Only invest if you will utilise advanced security and compliance features. |
| Azure Consumption | Pre-committed Azure spend (annual monetary commitment) at enterprise discount rates. | Overcommit = wasted budget. Undercommit = higher overage rates. Start conservatively and increase later. |
| Dynamics 365 | Per-user or per-app licensing for CRM, ERP, and business application modules. | Complex mix of base + attach licences. Ensure you understand which modules are included and which carry additional per-user costs. |
| Add-Ons (Copilot, Power Platform) | Microsoft 365 Copilot ($30/user/month), Power BI Pro/Premium, Power Apps per-user plans. | New upsell vector. Evaluate ROI carefully before committing to Copilot at scale. Pilot first. |
Do not buy "shelfware" for a bundle discount. Microsoft may offer extra incentives if you commit to additional Azure spend or upgrade users to E5. Only take such bundle deals if those services are genuinely part of your IT strategy. Otherwise, you risk paying for capacity you will never use, just to get a discount on something else. See Microsoft Licensing Trends 2025–2026.
Microsoft is transitioning its licensing models toward more cloud-centric agreements, particularly the Microsoft Customer Agreement (MCA). For now, the EA remains the primary vehicle for large customers, but the landscape is evolving.
One of the key benefits of an EA is volume-based pricing. Microsoft uses tiered price levels (A, B, C, D) based on the number of users or devices covered:
| Pricing Level | Seat Threshold | Typical Discount | Notes |
|---|---|---|---|
| Level A | 500–2,399 seats | ~15% off list | Entry tier. Modest discount. Microsoft may move smaller customers to MCA/CSP from 2025. |
| Level B | 2,400–5,999 seats | ~20–25% off list | Mid-market enterprise. Meaningful volume pricing kicks in here. |
| Level C | 6,000–14,999 seats | ~25–35% off list | Large enterprise. Significant leverage for negotiated discounts beyond standard tiers. |
| Level D | 15,000+ seats | ~35–45% off list | Largest enterprises. Steepest base discounts, but Microsoft is eliminating volume tiers for cloud services from late 2025. |
Major change: Volume-based cloud discounts are disappearing. From November 2025, Microsoft is eliminating volume-based pricing tiers for online services (Microsoft 365, Dynamics 365, Power Platform) under EA. Whether you have 300 seats or 30,000, you will pay the Level A list price for cloud services. For large enterprises previously at Level D, this represents an effective price increase of 8–15% or more. This makes negotiation of custom discounts more important than ever. See Microsoft Licensing Trends 2025–2026.
| Cost Driver | Impact & Management Strategy |
|---|---|
| User/Device Count Growth | More users = more licences. Budget for expected growth. If anticipating significant expansion or contraction, consider an ESA for flexibility. |
| Product Edition Selection | E5 costs ~50% more than E3 per user. Only licence premium editions for users who genuinely need advanced security, compliance, or analytics. Adopt a mixed-tier approach. |
| Azure Consumption Commitments | Committed Azure spend unlocks discounts, but unused commitment is wasted budget. Track usage closely. Start conservative and negotiate the ability to adjust or carry over unused funds. |
| Negotiated Discount Level | The standard tier discount can be improved. Benchmark pricing. Large enterprises can push for 30%+ off Microsoft's initial quote. Ensure discounts apply evenly across all years. |
| Underutilised Licences | Paying for unused subscriptions inflates costs. Audit usage regularly and eliminate dormant licences before true-ups and renewals. Also utilise the SA benefits you have paid for. |
Pricing is typically locked for the three-year term for products included in the EA, protecting your budget against Microsoft's periodic increases. But if you add a new product mid-term that was not in your original agreement, it may be priced at the then-current rate. Plan your needs early and include all likely products from the start. See Microsoft EA vs MPSA for Large Enterprises.
Managing an Enterprise Agreement is an ongoing process, not a one-time set-and-forget. Renewals are the critical juncture to realign your contract with current business needs, and where the most money is won or lost.
Gain a detailed view of every licence and subscription in use. Identify excess: unused Visio licences, M365 seats assigned to ex-employees, dormant Power BI seats. This cleanup reduces your renewal baseline costs.
Engage department heads and IT architects. Will you expand Azure? Roll out Dynamics 365? Upgrade from E3 to E5 for security teams? Also question whether you still need everything you currently have.
Project growth or contraction. Growth can be handled via true-ups. Negotiate pricing upfront. Planned reductions are trickier: consider ESA or negotiate a contractual flexibility clause for special cases.
Initiate formal discussions with your Microsoft account manager or LSP. Drive negotiation according to your strategy. Have legal review the final contract to ensure all negotiated terms are captured.
The annual true-up is a strategic review, not a compliance exercise. Each year, verify internally the need for any new licences and ensure assignments are optimised before submitting a true-up count. Large true-ups can sometimes be leveraged to renegotiate or secure a discount on added units, especially if they are part of a broader expansion. Treat each true-up as a mini-renewal event. Read Microsoft EA True-Up: Cost Reduction Strategies.
Microsoft's sales teams are under pressure to secure renewals on time. Use that to your advantage. In recent years, Microsoft has encouraged customers to finalise renewals early, sometimes offering price incentives to sign months before the deadline. Weigh these offers carefully: an early renewal extends your commitment sooner than necessary, but meaningful discounts or favourable terms could make it worthwhile.
Conversely, do not be afraid to let the expiration date draw near if you need leverage. Microsoft is keen to close deals by their fiscal year-end (June 30) or quarter-end. The closer you get, the more flexibility you might see. Ensure you have executive backing if you employ this tactic.
A global manufacturer with 12,000 Microsoft 365 E3 seats was approaching its EA renewal. Microsoft's initial proposal included an 8% cost increase, an E5 "upgrade" for all users, and a $4.5M Azure commitment, a total spend of $28M over three years.
By engaging independent advisers, the company conducted a thorough usage audit, discovering 1,800 unused M365 seats and 3,200 users who did not need the proposed E5 features. They negotiated a mixed-tier approach (E5 for security teams only), a right-sized Azure commitment with unused-funds carryover, and a price cap clause.
Final outcome: $19.4M over three years, a savings of $8.6M (31%) versus Microsoft's initial proposal.
Negotiating a Microsoft Enterprise Agreement is a high-stakes endeavour. With the right approach, you can significantly tilt the outcome in your favour.
| Best Practice | What to Do | Why It Matters |
|---|---|---|
| Form a cross-functional team | Include IT, procurement, finance, and legal. Designate an executive sponsor (CIO or CFO). | A united front is crucial. Microsoft reps will notice internal divisions and may exploit them. Align on must-haves and walk-away points before discussions. |
| Start early with clear objectives | Begin preparations 9–12 months before renewal. Define target cost reduction, specific products, and contractual flexibility terms. | Defined goals prevent you from being sidetracked by offers that do not meet core objectives. |
| Leverage data and benchmarks | Use deployment and usage data as a fact base. Reference industry benchmarks to challenge high quotes. | Data-driven negotiations signal to Microsoft that you have done your homework and will not accept status quo pricing. |
| Negotiate beyond price | Request price protections for next renewal, licence swap rights, Azure credit carryover, migration funding, or training and deployment support. | Non-price concessions often cost Microsoft less to grant, making them more willing to concede. They can add significant long-term value. |
| Be wary of pressure tactics | Resist imposed deadlines. Maintain your timeline. If Microsoft courts your CEO with "strategic partnership" talk, steer toward tangible benefits. | Large contract decisions should happen on your timeline. Turn Microsoft's urgency into your leverage. |
| Maintain a credible "Plan B" | Evaluate alternatives: CSP licensing, Google Workspace for some users, AWS for cloud workloads. | Microsoft negotiates more aggressively when they know you are willing to redirect spend. |
| Get everything in writing | Translate verbal promises into contract language. Double-check fine print before signing. | Microsoft will honour what is in the contract, not what was mentioned in a meeting. |
Microsoft is gradually shifting the enterprise licensing landscape from traditional Enterprise Agreements toward the Microsoft Customer Agreement (MCA), a simpler, cloud-optimised contract structure.
| Aspect | Enterprise Agreement (EA) | Microsoft Customer Agreement (MCA) |
|---|---|---|
| Contract Type | Negotiated, multi-year contract with custom terms. | Standardised online agreement. Less negotiation flexibility by default. |
| Term | 3-year fixed commitment. | Flexible: monthly, annual, or multi-year subscriptions. Mix and match. |
| Pricing | Volume-tiered discounts (A–D) with ability to negotiate custom pricing. | Starts at list price. Custom discounts must be negotiated harder. |
| Flexibility | Limited mid-term flexibility. True-ups only go up. | Greater operational flexibility. Add or remove licences more frequently. |
| Billing | Annual payments in thirds. Predictable. | Monthly or annual billing. More flexible but less predictable. |
| Eligibility | 500+ users/devices. From 2025, Microsoft may raise this threshold. | No minimum. MCA-E (Enterprise) for larger organisations dealing directly with Microsoft. |
The EA is not dead yet, but plan for MCA. For now, the EA remains available for large customers and often delivers better pricing for organisations with significant on-premises requirements or those who negotiate effectively. However, Microsoft is clearly steering toward MCA as the future default. The key risk with MCA is that baseline pricing is higher and discounts require more aggressive negotiation. Read MCA Explained: Is It Replacing EAs?
Treat the EA renewal like a major project with a formal timeline, stakeholder alignment, and milestone tracking.
Remove unused licences, downgrade expensive subscriptions that are not fully utilised, and eliminate overlap between products.
Only include products and cloud services that fit your strategic plans. Resist upsells for capabilities you will not use.
Sales teams are more flexible near fiscal year-end (June 30) and quarter-ends. Do not base your entire strategy on timing, but use it for final concessions.
Push for the right to reduce cloud subscription counts at each anniversary, or to substitute products of equal value if priorities shift.
You are paying for SA. Use the planning services days, support incidents, and training vouchers. If you have not used them, negotiate a lower price or additional concessions.
A well-timed CEO-to-Microsoft-executive conversation can unlock concessions reserved for high-level engagement.
Independent Microsoft licensing advisers provide benchmark data, negotiation insights, and objective assessment of Microsoft's proposals.
Keep clear records of proposals, counter-proposals, and promises. Archive the final agreement and a summary of key negotiated points for the next renewal cycle.
Gather data on all licences and subscriptions, utilisation rates, user counts, deployed software versions, and cloud consumption (Azure, M365, Dynamics). This establishes your baseline and highlights under-utilisation.
Determine what your organisation will require from Microsoft over the next three years. Map upcoming projects, cloud migrations, and user growth. Also identify products that can be phased out.
Assemble a team with IT, finance, procurement, and legal. Define roles clearly. Establish a regular meeting cadence and ensure alignment on objectives and messaging.
Determine key goals: contain cost growth to X%, secure Y% more value, achieve specific contractual flexibilities. Research benchmarks. Prepare a negotiation timeline with escalation milestones.
Initiate conversations well in advance. Solicit Microsoft's initial proposal, then drive negotiation methodically. Have legal review the final contract to ensure all negotiated items are captured.
A Microsoft Enterprise Agreement is a volume licensing contract for organisations with 500+ users that offers discounted, predictable pricing for a wide range of Microsoft products over a three-year term. Enterprises that want to standardise their Microsoft software and cloud subscriptions, and benefit from centralised management and budget stability, should consider an EA. It simplifies licence administration and can save money at scale, though it requires committing to a defined scope of products and users for the full term.
The EA can include Microsoft 365 subscriptions and Azure cloud services alongside traditional on-premises licences. For Microsoft 365, you enrol the number of user subscriptions (E1/E3/E5) needed, with the ability at each anniversary to adjust quantities. For Azure, an EA typically involves committing to a specific annual consumption amount, drawing down against that commitment as you use services. Both are subject to negotiated pricing and terms, meaning you can secure enterprise discounts and price locks.
Built-in volume discounts range from roughly 15% off list (Level A, ~500 seats) to 35–45% off (Level D, 15,000+ seats) before any special negotiation. With effective negotiation, many enterprises achieve an additional 5–15% beyond the standard tier, or get Microsoft to include bonus services at no extra cost. However, note that Microsoft is eliminating volume tiers for cloud services from late 2025, making negotiated custom discounts more critical.
Growth is straightforward: you add licences via the annual true-up process. Shrinking is harder, as a standard EA does not let you reduce counts or get money back mid-term. An Enterprise Subscription Agreement (ESA) allows decreases at yearly anniversaries. For mergers or acquisitions, the EA can typically accommodate new users via true-up or transfer to a new entity, but these situations require discussion with Microsoft. Negotiate clauses for merger/divestiture scenarios if you anticipate them.
Yes, renewal is optional. If you do not renew, any perpetual licences remain yours at their current version, but you lose the right to upgrade once Software Assurance lapses. Subscription services (Microsoft 365, Dynamics 365, Azure) would need to transition to another programme (CSP or MCA) or be discontinued. Many organisations use the threat of non-renewal as legitimate leverage during negotiations.
The EA is a negotiated three-year volume agreement for 500+ users with fixed pricing and volume discounts. CSP (Cloud Solution Provider) is a partner-managed programme offering flexible monthly or annual subscriptions, generally at or near list price. MCA (Microsoft Customer Agreement) is Microsoft's newer standardised agreement, gradually replacing EA for smaller enterprises and cloud-first customers. MCA-E (Enterprise) is the direct-to-Microsoft variant for larger organisations. See MCA Explained: Is It Replacing EAs?
Treat the true-up as a strategic review. Before each anniversary, verify internally whether new licences are genuinely needed and ensure assignments are optimised. Remove or reassign unused licences before submitting your count. Large true-ups can be leveraged to negotiate discounts on added units. In a standard EA, true-ups only go up. An ESA variant allows downsizing at anniversaries. See Microsoft EA True-Up Guide.
Almost certainly not. E5 costs roughly 50% more per user than E3, so a blanket upgrade adds significant cost. E5 makes sense for users who genuinely need advanced security, compliance, analytics, or Teams Phone. For most knowledge workers, E3 provides more than sufficient capability. Adopt a mixed-tier approach: E5 for users who need it, E3 for everyone else.
Your primary leverage is volume (the more seats, the more Microsoft wants your renewal), timing (Microsoft's fiscal year-end and quarter-end create quota pressure), and optionality (a credible alternative strategy makes Microsoft more flexible). Additional leverage comes from data: demonstrating usage patterns that justify lower quantities, benchmarking pricing against peers, and having independent advisory support.
Yes. From November 2025, Microsoft is eliminating volume-based pricing tiers (A–D) for online services under EA and similar agreements. All cloud subscriptions will be priced at Level A list price regardless of seat count. For large enterprises previously at Level D, this is an effective 8–15% price increase. This makes negotiating custom discounts critical. See Microsoft Licensing Trends 2025–2026.