EA — Enterprise Agreement
Category: licensing
Last reviewed by the MSLicenseHub Licensing Desk.
The Microsoft Enterprise Agreement (EA) is the primary volume licensing program designed for organizations with at least 500 users or devices. It offers a standardized, three-year commitment that allows for centralized management of software assets, bundled maintenance through Software Assurance, and the highest available volume discounts.
Operational Mechanics and Structure
The EA is built on the concept of "Platform Products"—specifically Windows Enterprise, Microsoft 365 (or Office 365), and the Enterprise Mobility + Security suite. To enter an EA, an organization must commit to an enterprise-wide purchase for all qualified users or devices. This "all-in" commitment is what triggers the deep price discounting compared to transactional programs like MPSA or CSP.
Key administrative features include:
- The Three-Year Term: Pricing is locked in at the start of the agreement, protecting the organization from retail price increases for the duration of the term.
- Annual True-Ups: Instead of purchasing licenses every time a new employee starts, organizations track their usage and perform a "True-Up" once a year. This allows for the deployment of software in real-time with payment reconciled annually.
- Software Assurance (SA): SA is mandatory and included in the EA. It provides benefits such as version upgrades, license mobility, and specialized support.
- Subscription vs. Perpetual: While a standard EA provides perpetual rights (you own the license after three years), the Enterprise Subscription Agreement (EAS) variant offers lower upfront costs but requires the return of licenses if the subscription is not renewed.
Common Misunderstandings
A frequent misconception is that an EA is always the cheapest option. While it offers the deepest unit discounts, the "enterprise-wide" requirement can lead to over-licensing if an organization has a high percentage of "deskless" workers who do not require full suites. Additionally, many users confuse EA licenses with OEM licenses; it is important to note that the Windows license in an EA is an upgrade only. The underlying base operating system must still be acquired via an OEM (pre-installed by hardware manufacturers) or Retail channel.
Documentation and Related Terms
On a formal quote or Microsoft Business and Services Agreement (MBSA), the EA will appear under several identifying numbers:
| Enrollment Number | The specific 7 or 8-digit identifier for the three-year purchase cycle. |
| L&SA | Line items marked as "License and Software Assurance," representing the combined cost of the product and maintenance. |
| CPS | The Customer Price Sheet, the definitive document listing your specific negotiated pricing. |
Practical Implications for Procurement
When buying through an EA, you are moving from a reactive procurement model to a strategic one. Because the True-Up process happens annually, IT departments have more flexibility in deployment but must maintain rigorous asset management to avoid "True-Up shock" (unexpectedly high year-end costs). For organizations planning a full transition to the cloud, the EA is often used as a vehicle for "M365 From SA" SKUs, which bridge the gap between legacy on-premises investments and modern cloud subscriptions.
Need this in a quote?
Our team translates glossary concepts into concrete licenses, part numbers and price lists.
Request a quote