For a long time, Microsoft Enterprise Agreements (EA) provided a predictable path for organizations that wanted volume discounts, contract consistency, and long-term budgeting certainty. That model is changing. Many organizations are now discovering that the assumptions they built into their Microsoft licensing strategy no longer apply.

If you're responsible for Microsoft licensing, procurement, IT operations, or technology budgeting, understanding these changes is critical because they may affect renewal costs, contract options, procurement flexibility, and long-term governance of your Microsoft environment.

This guide answers the most common questions organizations are asking today.

Key Terms Explained

Before diving into the changes, it's important to understand the key terms most organizations are discussing today.

Term Definition Best Understood As
EA (Enterprise Agreement) Microsoft's traditional volume licensing agreement historically designed for organizations with 500 or more users or devices, which has now risen to 2400. A contractual purchasing vehicle.
MCA-E (Microsoft Customer Agreement for Enterprise) Microsoft's digital purchasing agreement designed around modern billing administration and cost management. A billing and governance framework.
CSP (Cloud Solution Provider) A partner-led purchasing model through a Microsoft partner. A relationship model.
Unified Support Microsoft's support offering, priced based on historical Microsoft product spend. A spend-linked support model.


The easiest way to think about these models is this:

  • EA is a contract.
  • MCA-E is a commercial framework.
  • CSP is a partner relationship.
  • Unified Support is a spend-based service model.

Understanding those distinctions makes the rest of Microsoft's licensing evolution much easier to navigate.

What changed with Microsoft licensing?

Microsoft's commercial licensing model has undergone several significant changes affecting Enterprise Agreement customers. The most impactful changes include:

  • Elimination of EA volume discount tiers (Levels B, C, and D)
  • Movement away from traditional Enterprise Agreement structures
  • Rising minimum seat requirements for EAs
  • Increased scrutiny around Unified Support costs
  • Greater emphasis on Azure consumption commitments and growth requirements

Taken together, these changes are forcing many organizations to reevaluate long-established purchasing strategies and renewal assumptions. For many years, renewing an Enterprise Agreement was largely a procurement exercise. Increasingly, organizations are discovering that renewal decisions now involve governance, support strategy, financial management, and long-term operational accountability.

Are Microsoft Enterprise Agreements still available?

The answer increasingly depends on organization size. Microsoft's EA minimum threshold is rising to approximately 2,400 users. Organizations below that level may find it difficult, or impossible, to renew into a traditional Enterprise Agreement. In many cases, they may be directed toward alternative purchasing models such as CSP (Cloud Solution Provider).  

This primarily impacts mid-market organizations that historically qualified for EA but may no longer meet Microsoft's evolving qualification criteria. Organizations now have more commercial options, more purchasing motions, and more governance considerations than they did when EA was the dominant enterprise purchasing vehicle.

What happened to Microsoft Enterprise Agreement discounts?

One of the most significant developments occurred in August 2025 when Microsoft announced changes to pricing for Online Services sold through Enterprise Agreements and other volume licensing programs.

Published reports citing Microsoft's announcement state that automatic price-level discounts for Online Services were flattened to Level A pricing beginning in November 2025. The change affects products including Microsoft 365, Azure, Dynamics 365, Windows 365, and Microsoft's security and compliance offerings.  

Organizations that previously benefited from volume-based discounts are now finding that many of those pricing advantages have disappeared, resulting in higher renewal costs and reduced negotiating leverage.

Why are so many organizations evaluating CSP now?

As Microsoft's purchasing ecosystem evolves, organizations are increasingly evaluating partner-led purchasing models alongside Microsoft-direct agreements.

This changes the nature of the licensing discussion. Historically, organizations focused primarily on contract terms and pricing, making Enterprise Agreements natural decisions. Increasingly, they're evaluating the broader relationship and investment that surrounds the Microsoft environment, including licensing administration, support experiences, optimization guidance, and operational accountability.

Because CSP is fundamentally a partner-led model, the quality and capabilities of the partner become an important part of the overall decision, especially for those seeking greater flexibility, visibility, and operational support.

Why is Microsoft Support getting talked about in licensing discussions?

Microsoft's Unified Support is based on historical annual product spend. For example, Unified Support often represents approximately 8–12% of total Microsoft spend. Because costs are tied to overall Microsoft consumption, support costs may continue increasing as organizations add licenses and cloud services. This has led many procurement and finance leaders to ask:

  • Are support costs aligned with business value?
  • Can support spending be better controlled?
  • Are there alternative support models available?

As a result, support strategy has become part of broader Microsoft licensing conversations rather than a standalone discussion. This also leads organizations to seek partners who can provide licensing and support under one umbrella.

What is MCA-E and why is everyone talking about it?

MCA-E (Microsoft Customer Agreement for Enterprise) is Microsoft's newer licensing framework that is increasingly replacing traditional Enterprise Agreements. The transition began in March 2026 for many enterprise customers. The transition matters because MCA-E introduces several structural changes:

Under EA:

  • Long-term agreement structure
  • Established pricing protections
  • Annual true-up and true-down mechanisms
  • Partner-assisted account management

Under MCA-E:

  • Term-based pricing
  • Standardized contractual provisions
  • Account management increasingly handled directly by Microsoft
  • Reduced partner involvement in the overall relationship

For many organizations, the shift is less about licensing products and more about changes in governance, administration, and commercial flexibility. Additionally, while MCA-E is becoming more prominent in Microsoft's commercial ecosystem, organizations evaluating renewal options are often comparing it alongside other purchasing approaches, including CSP, to determine which model best aligns with their operational and governance requirements.

Why are Procurement, IT, and Finance all part of the licensing conversation?

  • Microsoft's commercial evolution affects multiple stakeholders simultaneously.
  • Procurement is evaluating contracts, purchasing models, and commercial flexibility.
  • IT is evaluating operational impact, administration, support experiences, and governance requirements.
  • Finance is evaluating forecasting accuracy, cost predictability, and long-term budget management.
  • While each group approaches the issue from a different perspective, all three are ultimately trying to answer the same question:
  • How do we create greater visibility, predictability, and control over Microsoft's role within the organization?

What This Means for Organizations

The most important takeaway is this: Microsoft licensing is no longer just about licenses. The changes occurring across Enterprise Agreements, MCA-E, support models, and cloud consumption requirements are pushing organizations to think more holistically about how Microsoft investments are managed. Organizations evaluating their Microsoft future should consider five questions:

  1. Is our current purchasing model still the right fit?
  2. How have Microsoft's pricing changes affected our renewal economics?
  3. Do we have sufficient visibility into Microsoft spend and consumption?
  4. How will support costs behave as our Microsoft footprint grows?
  5. Who is accountable for governing our Microsoft investment over the next three to five years?

Those questions are ultimately more important than any individual licensing program because they shift the conversation from procurement mechanics to long-term business outcomes. Microsoft's commercial landscape continues to evolve, but the organizations that navigate it most successfully will be those that view licensing, support, budgeting, and governance as part of a single strategy rather than separate decisions.