The Microsoft EA Document Architecture
A Microsoft Enterprise Agreement is not a single document. It is a layered contractual structure comprising six interconnected documents, each serving a distinct function. Understanding this architecture is essential before you can evaluate what you are signing or what you can negotiate.
| Document | Function | Negotiable? |
|---|---|---|
| Microsoft Enterprise Enrolment | The operative agreement — identifies parties, term, products, and counts. This is what you actually sign. | Yes — counts, terms, amendments |
| Microsoft Business and Services Agreement (MBSA) | The master terms governing the entire commercial relationship. Incorporates by reference all other documents. | Limited — standard terms with some enterprise exceptions available |
| Price Sheet | Lists effective prices for every product in the enrolment. Generated at contract execution. | Yes — discounts negotiated here |
| Microsoft Product Terms | Defines use rights for every Microsoft product — what you can and cannot do with each licence. Updated monthly by Microsoft. | No — standard for all customers |
| Online Services Terms (OST) / Data Protection Addendum (DPA) | Governs cloud service terms, data processing obligations, GDPR commitments, and Microsoft's data use rights. | Limited — some DPA provisions negotiable for regulated industries |
| Amendment / Order Form | Documents any changes agreed after initial signing — price adjustments, product additions, co-terming events. | Yes — the primary vehicle for mid-term and renewal changes |
The practical implication of this architecture: the document you sign (the Enrolment) incorporates terms from documents you may never have read (Product Terms, MBSA). A change in the Product Terms — which Microsoft updates monthly — can affect your use rights without any amendment to your signed agreement. This is the principal mechanism through which Microsoft adjusts licensing rules during a three-year EA term.
The Microsoft Business and Services Agreement: What It Actually Says
The MBSA is the master governing document. Most enterprise procurement teams read the Enrolment carefully and the MBSA cursorily, which is the wrong allocation of attention. The MBSA contains the commercially significant clauses — and the ones that most enterprise customers would want to modify if they read them carefully.
Audit Rights — The Clause That Matters Most
The MBSA grants Microsoft audit rights that are, if read literally, extraordinarily broad. Microsoft can request a self-assessment (which you prepare) or, in Section 6, conduct its own audit using a third party of Microsoft's choosing. The key provisions to understand:
- Scope: Audit rights extend to all Microsoft software and services — not just what is in your EA, but any Microsoft product deployed by you or your affiliates.
- Methodology: The MBSA does not specify audit methodology. Microsoft and its designated auditors can propose their own counting methodology, which enterprise customers are expected to accept unless they challenge it.
- Frequency: No explicit limitation on audit frequency in the standard MBSA. Enterprise amendments can introduce cooling-off periods (typically 12–24 months between audits).
- Cost: You bear significant internal cost for responding to an audit regardless of outcome. The MBSA does not require Microsoft to pay your response costs even if findings are zero.
What can be modified: audit scope limitation (excluding specific product categories or subsidiary entities), methodology approval rights (requiring agreement before audit commences), cooling-off provisions, and data disclosure limits. For our full audit defence guide including how to respond to an audit notice, see the dedicated article.
True-Up Mechanics: The Contractual Obligation
The MBSA and Enrolment together establish the true-up obligation. The core mechanic: annually on the anniversary of your enrolment date, you must report all qualified desktops and users across your organisation, and pay for any count increases above your initial commitment. Key provisions:
- True-up pricing: Unless you have a price protection amendment, your true-up additions are priced at the then-current price sheet prices — not the prices at which you originally signed. If Microsoft has increased prices during your term (as it did in 2022 with a 15–25% increase), your true-up additions are priced at the higher rate.
- True-up scope: The obligation extends to affiliates covered by your EA. If you acquire a company mid-term, their headcount enters your true-up obligation from the acquisition date.
- Annual vs anniversary: Most EAs use an anniversary true-up, but some use a calendar year true-up. The distinction affects when you report and when you pay. Confirm which model applies before your first true-up cycle.
The commercially critical amendment is true-up pricing lock — a provision specifying that additional licences purchased during the term are priced at the original enrolment price plus any negotiated price escalation cap. Without this protection, you are exposed to full price increases on all growth. For detail on the true-up mechanics and how to negotiate them, see our dedicated guide.
Payment Terms
The standard MBSA payment terms are annual in advance — one third of the three-year total commitment payable in each year. Microsoft's standard position is non-negotiable on this for most customers, but exceptions exist:
- Monthly billing: Available for some cloud-only EAs (MCA-Enterprise model) — not typically for on-premises-inclusive EAs.
- Upfront payment discount: For organisations that can pay the full three-year commitment in advance, Microsoft occasionally offers a further discount, typically 2–4% of the total. This is not widely advertised.
- Payment date flexibility: The anniversary date can sometimes be aligned to your financial year for budgeting purposes, though this requires agreement before the enrolment is executed.
Auto-Renewal Provisions
The MBSA and standard Enrolment terms contain auto-renewal provisions. If you do not provide written notice of non-renewal within a specified period before expiry (typically 60–90 days depending on your Enrolment version), the agreement may auto-renew on potentially unfavourable terms. Enterprise customers have been caught by this provision — discovering that their agreement has renewed at list price without negotiation because the non-renewal notice window was missed.
The correct countermeasure: enter your non-renewal notice date (expiry minus 90 days) into your procurement calendar at EA execution, and ensure responsibility for sending the notice is clearly assigned. Sending the non-renewal notice does not end the relationship — it simply preserves your negotiating position and ensures Microsoft does not unilaterally renew at non-negotiated prices. For the full EA renewal preparation timeline, see our dedicated guide.
Need Independent EA Contract Review?
We review Microsoft EA Programme Agreements for enterprise customers ahead of signing or renewal — identifying commercial risks, negotiable terms, and the amendments that protect your organisation for the full three-year term.
Request a Contract Review → Download EA PlaybookThe Enrolment Agreement: What You Actually Sign
The Enrolment is the operative document — it specifies who is covered, what products are included, at what counts and prices, for what term. Despite being the document that most attention is paid to during execution, many enterprise customers sign Enrolments that have not been reviewed for the following commercially critical items:
Affiliate Coverage Schedule
The Enrolment specifies which legal entities are covered. Coverage can be defined either by a named-entity schedule (specific companies listed) or by a definition-based approach (any entity where the customer holds >50% ownership, directly or indirectly). The choice has significant commercial implications:
- Named-entity schedule: Provides clarity on scope. New acquisitions require amendment. Divestitures can remove entities cleanly.
- Definition-based (standard): Automatically includes new acquisitions from the date ownership threshold is met. Creates Day 1 compliance obligation on acquisitions. Can create unintended over-coverage for minority investments that approach the 50% threshold.
For organisations with active M&A programmes, the affiliate coverage definition in the Enrolment is a material commercial clause. See our EA affiliate licensing guide for detailed analysis.
Product and Count Tables
The Enrolment specifies the product categories (Enterprise, Enterprise Plus, Additional Products) and the minimum licence counts for the initial period. This is the baseline against which your true-up obligations are measured. Common errors in Enrolment product tables:
- Overcounting the qualified desktop base: Microsoft often uses the organisation's total headcount as the qualified desktop count. The actual qualified desktop count (devices running qualifying Windows OS or users of qualifying products) is frequently 10–20% lower.
- Including products not deployed: Enterprise-wide products included "for completeness" that are not actually deployed represent pure cost without value.
- Incorrect platform assignment: Cloud-only users sometimes included in on-premises platform counts, and vice versa — affecting price sheet allocation.
Term and Co-Terming Events
The standard Enrolment term is three years. Co-terming — aligning the term of added products to the main enrolment anniversary — has commercial implications that are frequently underestimated. When you add a product mid-term and co-term it to your existing enrolment, you are purchasing a partial-year licence at full annual pricing. Microsoft treats this as a three-year commitment for pricing purposes (volume tier calculation), but only charges for the remaining months. The practical effect: you get the full three-year discount but pay only for the remaining months of the term. This can be commercially advantageous for large mid-term additions — and Microsoft's account team will often resist it for exactly that reason.
The Product Terms: The Document That Changes Without Your Signature
Microsoft's Product Terms (formerly the Product Use Rights or PUR, formerly the Online Services Terms) are a monthly-updated document that defines what you can do with every Microsoft product. Your EA incorporates the Product Terms by reference, which means that changes Microsoft makes to the Product Terms automatically become part of your agreement — without any amendment or your signature.
Since 2022, Microsoft has used Product Terms updates to introduce: Teams EU unbundling requirements, SQL Server licensing changes for virtualisation environments, and Defender for Endpoint feature realignments. All of these affected enterprise EA customers mid-term without any renegotiation opportunity. Monitoring Product Terms changes is not optional for enterprise customers with complex environments — it is essential compliance risk management.
What the Product Terms govern in practice:
- Use rights: What you can install, how many devices, which configurations are permitted.
- Licence mobility: Under what conditions you can run Microsoft software on third-party hosted infrastructure.
- Dual-use rights: Whether previous product versions remain available.
- AHUB conditions: The terms under which Azure Hybrid Benefit can be claimed — conditions that have been modified mid-term in the past.
- True-up scope definitions: How qualifying users and devices are counted — definitions that affect your true-up obligation.
The best defence against adverse Product Terms changes is a well-constructed amendment that locks in the use rights and counting methodology in effect at the time of signing. This is one of the highest-value provisions you can negotiate and one that Microsoft account teams resist strongly — which itself signals its commercial value. For a clause-by-clause analysis of your EA, see our guide on how to read your Microsoft Enterprise Agreement.
The Amendment: Your Primary Post-Signing Protection Vehicle
After the EA is executed, the Amendment (sometimes called an Order or Amendment Order) is the vehicle through which all commercial changes are documented. Understanding the amendment framework matters for two reasons: first, it determines what protections you can add during the term; second, the amendment process is where many of the highest-value commercial provisions are obtained.
Amendment Provisions Worth Pursuing
| Amendment Provision | Commercial Value | Microsoft Resistance |
|---|---|---|
| True-up pricing lock — additional licences priced at initial enrolment price | High — eliminates price increase exposure on growth | High — directly protects revenue |
| Audit scope limitation — excludes specific product categories or entities | High — reduces audit exposure surface | Medium-High |
| MACC underspend protection — converts unspent MACC to credits | High — protects against Azure consumption shortfalls | Medium |
| EA-to-CSP transition rights — ability to migrate workloads without penalty | Medium-High — preserves flexibility | Medium |
| Renewal pricing commitment — next renewal not to exceed X% above current | High — the most forward-looking protection | Very High |
| Product Terms freeze — use rights locked to document version at signing | Very High — prevents adverse mid-term changes | Very High |
| Count reduction provisions — agreed process for reducing mid-term counts | Medium — protects against over-commitment | High |
Not all of these are achievable in every engagement, and the achievability depends on your leverage position, relationship quality, deal size, and timing. The key principle: amendment provisions should be negotiated at the point of maximum leverage — at renewal or at the time of a significant expansion event — not mid-term when you have no commercial leverage to offer.
Common Enrolment Errors and How to Avoid Them
Error 1: Signing Without Legal Review of the MBSA
The MBSA is a standard form agreement, but "standard" does not mean unimportant. Enterprise legal teams that routinely review supplier contracts often treat the Microsoft MBSA as a formality. The audit rights provisions, liability limitation clauses, and data processing terms in the MBSA warrant the same scrutiny as any major supplier agreement. If your legal team has not reviewed the MBSA in the past three years, the version you are working from may have changed.
Error 2: Not Retaining Executed Copies of All Documents
Every document in the EA architecture — Enrolment, MBSA, Price Sheet, all Amendments — should be retained in your procurement records with version dates. Microsoft's VLSC (Volume Licensing Service Centre) provides access to some documents, but not all historical versions. Your own records are the authoritative source. We have seen audit disputes where customers could not produce the price sheet version in effect at the time of true-up because their internal records were incomplete.
Error 3: Not Tracking Product Terms Changes
Microsoft publishes Product Terms updates on a monthly cycle. Subscribe to Microsoft's licensing notifications and assign responsibility for reviewing Product Terms changes to a named individual in your IT procurement or licensing team. Any change that affects your deployed product stack should trigger an immediate compliance assessment.
Error 4: Treating the Enrolment as a Procurement Document, Not a Commercial Contract
The Enrolment is executed by the purchasing entity's authorised signatory, typically in procurement. Because it resembles a standard order form in structure, it is frequently processed as one — with insufficient attention to the commercial terms embedded in it. The qualified desktop count, the affiliate coverage definition, the true-up anniversary date, and the co-terming provisions are all commercially significant decisions that should involve your CFO or General Counsel, not just your procurement team.
Planning Agreement: The Pre-EA Vehicle
Before an EA is executed, Microsoft often proposes a Planning Agreement — a lightweight document that records agreed commercial terms (product mix, counts, pricing parameters) for a future EA enrolment. Planning Agreements serve Microsoft's needs more than the customer's: they create commercial commitment before the formal agreement is executed, they lock in product scope that Microsoft wants included, and they establish a pricing anchor.
Planning Agreements are not binding in the same way as an Enrolment — but they create significant commercial momentum. Once your organisation has signed a Planning Agreement at a specific product mix and pricing, departing materially from those terms at Enrolment execution requires a much more difficult negotiation than if you had not signed a Planning Agreement at all. The guidance: if Microsoft proposes a Planning Agreement, treat it as a near-final commercial commitment and evaluate it with that weight. Do not sign a Planning Agreement with the intent to renegotiate materially at Enrolment. For the full EA negotiation guide, see our comprehensive article.
Frequently Asked Questions
Can I negotiate the MBSA terms?
Some MBSA provisions can be modified for large enterprise customers, typically via a separate Supplemental Agreement or addendum. The most commonly negotiated provisions are audit scope, liability caps (for certain regulated industries), and data processing terms. Standard MBSA terms apply to the majority of customers regardless of size.
What happens if Microsoft changes the Product Terms in a way that creates a compliance breach?
Microsoft typically provides a transition period for Product Terms changes that create new compliance obligations — usually 180 days. However, there is no contractual guarantee of any transition period. The best protection is the Product Terms freeze amendment provision, which locks use rights to the version in effect at signing for the EA term. Without this protection, you are subject to whatever Microsoft publishes monthly.
How do I get copies of all EA documents?
The VLSC (Volume Licensing Service Centre, now largely migrated to Microsoft 365 Admin Center) provides access to your Enrolment and some Amendment documents. For the MBSA, Product Terms, and older Price Sheets, request copies directly from your Microsoft account team and retain them in your own records. Do not rely on Microsoft's portals as your sole document archive.
What is the difference between an Enrolment and a Subscription under EA?
An Enrolment (also called Enterprise Enrolment) covers on-premises software and may include cloud services. A Subscription Enrolment is a cloud-first variant that covers primarily online services. Most large enterprises use the standard Enterprise Enrolment that covers both on-premises and cloud products.