The publisher's flagship volume contract: a three-year construct combining the Microsoft Business and Services Agreement, an Enterprise Enrolment, a Server and Cloud Enrolment and an annual True-Up. The Admodum read on the components, the cycle and the transition to MCA-E.
The Microsoft Enterprise Agreement is the publisher's flagship volume-licensing contract for organisations above the 500-seat threshold (the historical commercial floor; the publisher has retained the EA construct for upper mid-market and enterprise buyers while migrating the lower segments to the MCA-E and partner-led constructs).
The EA construct is a three-year contract by design. The base framework (the Microsoft Business and Services Agreement) is signed once; the enrolments under it carry the actual commercial commitments (the products subscribed, the user and device counts, the Azure commitment, the price level locked for the term).
The wider editorial sits in the Microsoft pillar; the Microsoft practice sits at the Microsoft practice; the aggregated reading list sits in the Microsoft knowledge hub.
An EA carries one or more enrolments under the MBSA framework. The principal enrolments today are: the Enterprise Enrolment (productivity: M365 E3 / E5 / F3, Microsoft 365 Apps, the per-user productivity suite), the Server and Cloud Enrolment (SCE) (the server-side products, Windows Server, SQL Server, Visual Studio, and the Azure monetary commitment), and the legacy Subscription EA (the original subscription-only variant).
Older or legacy enrolments may also appear in long-running cumulative contracts: the Enrollment for Education Solutions (EES, the academic variant), the Microsoft Products and Services Agreement (MPSA, the no-commitment cousin), the Open Value programme (the small-business cousin). Each carries its own commercial mechanics; the buyer-side discipline reads the cumulative contract record for every enrolment in force.
The renewal-time question is which enrolments persist on the EA and which transition to the MCA-E. The wider transition context is the publisher's strategic migration of the volume contracts onto the Customer Agreement family; the practical answer is enrolment-by-enrolment.
The True-Up is the EA's annual reconciliation of growth. The contract is sized at the start of the term against an initial user and device count; the True-Up reconciles, once per year on the anniversary, the actual growth in users and devices against that initial size.
The True-Up has three principal properties. First, it is retroactive: the growth is billed for the year that just elapsed, not for the year ahead. Second, it is priced at the term-locked price level: a user added in year three is billed at the price level locked at term start, not the publisher's current price-list. Third, the True-Up does not reduce: a contraction during the term is not refunded; only at renewal can the contract size be decreased.
The buyer-side discipline against the True-Up is the same disciplined discipline that runs against any once-per-year reconciliation: the actual user and device counts are tracked monthly; the headcount-fluctuation pattern is modelled; the True-Up window is scheduled and rehearsed before the publisher requests the reconciliation; the over-counting risk (users counted twice, devices counted as users, departed users not removed from the active register) is read against the licensing-count of record.
The Server and Cloud Enrolment carries the Azure monetary commitment, historically through the Server and Cloud Enrolment-Azure (SCE-Azure) component, more recently through the Microsoft Azure Consumption Commitment (MACC). The commitment is a multi-year (typically three-year) ramp of Azure spend; the buyer commits to a minimum quantum per year, the publisher delivers a discount on the consumption rate.
The commitment design is the principal commercial decision inside the SCE. Quantum, tenor, ramp shape (flat, front-loaded, back-loaded), eligible-service catalogue (which services count against the commitment), Marketplace pull-through (third-party Marketplace consumption counts against the commitment), unspent-commitment treatment (the commitment is consumed against actual spend; unspent commitment lapses).
The wider Azure MACC read sits at the Azure MACC design spoke (forthcoming in this cluster); the wider Azure context sits in the Microsoft practice; the white-paper read sits at the Azure MACC white paper.
The EA's price-level mechanic is a step-table priced against the user / device count at term start. Level A, B, C, D map to bands of user count; the price level applied to the products inside the EA is the level that matches the buyer's qualifying count at term start. The level locks for the duration of the term: growth via True-Up during the term is billed at the locked level, even when the cumulative count crosses into a higher level.
The mechanic creates a renewal-time arithmetic: a buyer crossing a level boundary during the term retains the higher-level pricing only until renewal; at renewal, the level resets to the actual count. Buyers approaching a level boundary at renewal have an arithmetic-driven decision (commit more at renewal to retain or move to a better level; commit less to consolidate at the current level; restructure the entities under the agreement to shift the count).
The wider account-team dynamic that frames the price-level conversation sits at the Microsoft account team spoke (forthcoming); the renewal-cycle context sits at the Microsoft EA renewal cycle.
The publisher is migrating the EA construct to the Microsoft Customer Agreement for Enterprise (MCA-E). The MCA-E is a perpetual-framework contract (no fixed term on the framework itself; the commitments are added as subscriptions under it) with a different commercial cadence and a different account-team posture.
The transition has practical implications. The three-year term protection ends. The price-level lock loosens. The annual True-Up gives way to monthly subscription mechanics. The negotiating posture shifts: the buyer is no longer renewing a single contract every three years but managing a portfolio of subscriptions under one framework.
The MCA-E-versus-EA decision read sits at the MCA-E versus EA spoke (forthcoming); the wider engagement sits in the Microsoft practice; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The publisher fiscal calendar and the eighteen-month renewal cadence.
A senior Admodum Microsoft advisor will read your cumulative EA, enrolment map and renewal proposal on a private call. Active renewal moments route to the Renewal Programme.