Under an enterprise agreement, Microsoft sets a price level for the organization, A through D, based on the qualified seat count, and that level governs the published pricing on every product line before a single concession is discussed. The level is locked at enrollment and rarely revisited, which means a buyer who accepts the wrong level pays the penalty for the full term. The price level is the quietest and most durable number in the entire agreement, and the buyers who win establish the right one before the negotiation over discount even starts.
The enterprise agreement assigns a price level from the organization's qualified user or device count. The bands are published, the level applies across the enrollment, and it determines the list pricing the discount is then applied against.
The enterprise agreement defines four levels keyed to qualified seat count. Level A covers the smallest qualifying enterprises, and the level rises through B and C to D for the largest. Each step up to a higher level carries a better base price on the enterprise products, before any negotiated discount is layered on.
The bands are set by Microsoft and applied at enrollment. The difference between adjacent levels is not trivial. On a large estate it can move the base cost of the core suite by a meaningful margin across the term.
The level is driven by the qualified count, which is not the same as the raw headcount. Affiliates, subsidiaries, and the way the enrolling entity is defined all shape the number Microsoft uses to set the band. How the organization scopes the enrollment directly determines the level it lands in.
This is where many buyers lose money silently. An enrollment scoped too narrowly can land a level below where the true consolidated estate belongs, and the buyer pays a higher base price for the whole term.
The most important property of the price level is that it is set at enrollment and holds for the agreement. It does not float up as the organization grows during the term, which makes the enrollment moment decisive.
The price level is established when the agreement is signed and governs the published pricing for the full term. Organic growth during the term does not automatically lift the buyer into a better level, so a buyer who enrolls just below a band threshold can spend three years paying the higher price even after crossing the line.
Because the level is sticky, the negotiation to establish it belongs before signature. Once the agreement is in place the level is effectively fixed until the next renewal, and the cost of getting it wrong compounds across every order.
Renewal is the moment the level is reassessed, which makes it the moment to correct a level that no longer reflects the true estate. A buyer whose consolidated count has grown past a threshold should arrive at renewal insisting the new level be recognized in the base pricing, not buried under a discount conversation.
Conversely, a buyer whose estate has shrunk should understand that the level rarely moves down, and plan the negotiation around discount and structure rather than expecting a lower band to rescue the price.
Buyers routinely confuse the price level with the discount and negotiate one while ignoring the other. They are distinct mechanics, and a strong discount on a wrong level still leaves money on the table.
The price level determines the published price the buyer starts from. It is the base. A buyer enrolled at the correct, higher level is negotiating a discount against a lower starting number on every product line, which compounds across the entire estate and the full term.
The negotiated discount is applied on top of the level based price. It responds to leverage and effort. But a generous discount on an inflated base, because the buyer accepted too low a level, can still cost more than a modest discount on the correct one.
The correct sequence is to establish the right level, then negotiate the discount against it. Buyers who let the discount conversation dominate while the level goes unexamined optimize the visible number and ignore the base that drives it.
Where the qualified count sits near a threshold, the level is genuinely arguable. The buyer who builds the count carefully and presents it before enrollment can land the better band and lock it for the term.
The strongest argument for a higher level is an accurate consolidated count that captures every affiliate and subsidiary the enrollment can legitimately include. Organizations frequently undercount because the estate is fragmented across business units that never reconcile their numbers.
Assembling the full qualified count before enrollment, and structuring the enrolling entity to include it, can lift the organization into a higher band and a lower base price that holds for the entire term.
Where the current count sits just below a band, a credible commitment to reach the threshold across the term can support enrolling at the higher level now. Microsoft will weigh the forward count against the risk, and a documented growth or consolidation plan gives the account team the cover to grant it.
This is the same logic as a volume tier jump, applied to the price level. The buyer trades a believable forward commitment for a better base price from day one.
The price level governs the enterprise products, but the rest of the estate is priced on its own logic. A buyer who assumes one level rules everything misreads where the savings actually sit.
The enterprise online services and the core suite are leveled across the whole organization, so the single qualified count sets the band for every seat. This is where the level matters most, because a better band reprices the largest, most uniform part of the estate.
It is also why consolidating the count is so powerful here. One reconciled number drives the price of the product line that dominates most agreements.
Azure is priced on consumption and commitment, not on the seat based price level. A buyer who wins a strong level on the suite still negotiates Azure on its own terms, through the commit, the discounts on consumption, and the funding that surrounds a migration.
Treating Azure as governed by the suite level is a common error that leaves the consumption negotiation underworked while the buyer celebrates a level that never touched it.
Server products and per device licensing follow their own quantity and pricing rules, sometimes tracking the level and sometimes priced independently. The buyer has to know which products move with the level and which are negotiated separately.
Mapping each product line to its pricing basis before the renewal ensures the level argument is applied where it pays and the separate negotiations are not neglected.
We treat the level as the first number to settle, built from a consolidated count and locked at the right band before the discount conversation begins.
We reconcile the qualified count across every affiliate the enrollment can include, identify which band the consolidated estate belongs in, and make the case for it before the agreement is signed. The objective is to lock the correct level, because it governs base pricing for the full term.
Where the count sits near a threshold, we build the forward case so the buyer can claim the higher band on a credible commitment rather than leaving the level to default to the lower one.
With the level settled, we negotiate the discount against the correct base, so the concession compounds on a lower starting number across every product line and the full term rather than on an inflated one.
At renewal we reassess the level against the current estate and insist any growth past a threshold is recognized in the base pricing, not quietly buried under a discount that looks generous and leaves the band untouched.
Our brief on the level bands, what counts toward the qualified total, and how to build the case for a higher band before enrollment. Sent on request.
The price level governs base pricing for the whole term and locks at enrollment. We build the consolidated count, claim the right band, and negotiate the discount against it.