You are registered. The full playbook follows on this page. For the chapter overview and a summary of what the guide covers, see the Microsoft EA Negotiation Playbook overview.
Prepared by Atonement Licensing · buyer-side advisory · last reviewed June 2026. Prices quoted are Microsoft list figures or clearly labelled indicative ranges; the 10,000-seat estate used below is a representative benchmark scenario for illustration, not a quote.
Executive summary
You can cap a Microsoft EA renewal uplift, and the buyers who do it start twelve months early with their own license count in hand. Microsoft frames the renewal as a fixed step up from your current spend, then adds E5, Copilot for Microsoft 365, and an Azure commitment on top. The quote moves when you bring an independent inventory, sequence the commercial levers correctly, and refuse to negotiate price before structure.
On a representative 10,000-seat estate, an opening proposal that standardizes the base on E5, deploys Copilot to the whole workforce, and sizes an Azure commitment to Microsoft's growth model can run near $10.4M per year on the productivity stack alone. The same headcount, right-sized across E5, E3, and F3 with Copilot held to the credible population, models near $5.2M per year — a Year 1 difference of roughly $5M (indicative) on the same people, before the headline discount is even discussed. The decision in front of procurement is which roles sit on which suite, how far to commit on Copilot and Azure, and which protections to place before signature.
The playbook on this page covers the full renewal cycle. It explains how Microsoft constructs an Enterprise Agreement quote from your trued-up quantities and price level, the twelve levers that change the number, and the 12-month preparation timeline that creates bargaining room. It then works through the three places most money is lost: the E3 to E5 step-up, the Microsoft Azure Consumption Commitment, and the audit or SAM engagement that lands mid-negotiation. Across our advisory engagements, structured preparation of this kind has produced an average saving of 38 percent against the initial proposal, and the durable value usually comes from a capped uplift, a right-sized mix, and a commitment sized to real demand rather than the headline discount alone.
How Microsoft prices an Enterprise Agreement renewal
A Microsoft Enterprise Agreement is a three-year commitment, normally for organizations with 500 or more users or devices, priced on enrolled quantities at a price level set by your size. Your renewal quote starts from the quantities you trued up to over the term, not from what your people actually use today. That distinction is where overspend begins, and it is the first number to challenge.
Price levels matter more than most buyers realize. The EA program bands customers into levels A through D by enrolled seat count, and each band carries a deeper programmatic discount against the published price list. A buyer near a band threshold has a structural argument before the negotiation even starts.
| Price level | Enrolled users or devices | What it means for the buyer |
|---|---|---|
| Level A | 500 to 2,399 | Entry EA band, smallest programmatic discount |
| Level B | 2,400 to 5,999 | Deeper band, check eligibility at every true-up |
| Level C | 6,000 to 14,999 | Material step in list discount, often missed at renewal |
| Level D | 15,000 and above | Deepest band, plus the strongest case for custom terms |
Two contract documents govern what you can change. The Microsoft Product Terms define use rights, license requirements, and what each SKU includes. The Enterprise Enrollment, increasingly paired with the Microsoft Customer Agreement, defines the commercial mechanics: the term, the true-up obligation, price protection on existing products, and the rules for adding or reducing at renewal. Read both before the first meeting, because the account team will quote from them selectively. The Microsoft Licensing Briefs are also worth pulling for the products where use rights are contested, such as virtualization and outsourcing scenarios.
The proposal usually arrives as a per-user step up. Microsoft proposes moving your base from Microsoft 365 E3 to E5, adding Copilot for Microsoft 365 at a per-user price, and committing Azure spend through a Microsoft Azure Consumption Commitment. Each addition is presented as a discount opportunity. Each one also raises your committed floor for the next three years. Microsoft runs on a June 30 fiscal year, the account team carries a quota weighted toward E5, Copilot, and Azure growth, and the first proposal is built to protect that growth, which means it is built with room to move.
EA, MCA-E, or CSP: confirm the vehicle before the price
Microsoft is steering mid-sized customers from the classic EA toward the Microsoft Customer Agreement for enterprise, the MCA-E, and toward Cloud Solution Provider purchasing through partners. Each vehicle changes the commercial rules. The EA gives three-year price protection on enrolled products and a defined true-up regime. The MCA-E moves pricing closer to a published rate card with fewer programmatic discounts but more flexibility on quantities. CSP prices monthly or annually through a partner whose own margin is negotiable.
Before any renewal conversation, decide which vehicle, or which combination, fits your size and volatility. A stable 20,000-seat estate usually belongs on an EA or MCA-E with negotiated terms. A volatile subsidiary or a divested unit often runs cheaper on CSP, where seats flex monthly. Microsoft will frame the vehicle question as administrative. It is not. It decides which protections you are even allowed to negotiate, so settle it first and put the answer in writing.
Action. Pull the Enterprise Enrollment and current Product Terms, confirm the purchasing vehicle in writing, and check your price level band before any number is exchanged.
2The renewal levers, sequenced
Price is one lever among twelve, and discount alone is the weakest place to spend your effort. A Microsoft EA gives buyers structural levers that protect spend across the full three-year term. Use them in order, starting with the ones that cost Microsoft the least to grant and protect you the most.
| Lever | What it does | When it works best |
|---|---|---|
| 1. Renewal price cap | Cap the uplift on renewed quantities for the term | Always; uncapped uplift is the quiet cost |
| 2. Term and timing | Align signature to Microsoft fiscal year end | When you can hold to a June close |
| 3. Product mix | Right-size E3, E5, F3, and F1 by user role | When licensing is one size fits all today |
| 4. True-down at renewal | Reset enrolled quantities to real headcount | When headcount fell or shelfware grew |
| 5. E5 component pricing | Buy the E5 Security or E5 Compliance step-up alone | When you need part of E5, not all of it |
| 6. Copilot pricing and term | Negotiate Copilot price, ramp, and exit | When Copilot is bundled into the base |
| 7. Azure commitment sizing | Set the MACC to consumption you can forecast | When the Azure commit is pushed past demand |
| 8. Azure discount and credits | Take consumption discounts and migration credits | When you have real near-term Azure growth |
| 9. Unified Support scope | Decouple support from license spend, scope to need | When support is priced as a percentage of spend |
| 10. Audit standstill | Agree no audit during an active renewal | When a SAM review and renewal overlap |
| 11. Payment terms | Annual rather than upfront, where cash matters | When the term is long and rates are high |
| 12. Discount | The headline percentage, last | After every structural term is set |
The order matters. If you spend your bargaining room on discount first, you have nothing left to trade for the renewal price cap, the true-down right, or a sensible Azure commit, all of which are worth more across three years than a few points off list.
A 10 percent discount on a base that is 20 percent too large is not a saving. It is a smaller overpayment.
Action. Build your lever list before the first meeting and rank it: structural protections first, discount last. Trade down the list, never up it.
Facing a Microsoft EA renewal in the next year? Our advisors run this playbook with you.
Microsoft EA Renewal AdvisoryThe 12-month EA renewal timeline
Room to bargain is built, not found. By the time Microsoft sends a renewal proposal, the buyers who do well have already finished the preparation. The timeline below is the one we run with clients, and each stage exists to take a decision out of Microsoft's hands and put it back in yours.
Baseline and inventory
Build an independent license and usage baseline, identify shelfware, and decide the right E3, E5, and F3 mix before Microsoft tables a number.
Benchmark and model
Set a benchmarked target price and walk-away, then model Copilot and the Azure commitment against real, bottom-up demand rather than the growth case.
Open and close
Open the commercial conversation structure-first, escalate exceptions to the deal desk, and time the close to the Microsoft fiscal year end.
| Months before renewal | What to do | Why |
|---|---|---|
| 12 to 9 | Build an independent license and usage baseline | You cannot negotiate what you cannot measure |
| 9 to 7 | Identify shelfware and the right E3, E5, and F3 mix | Decide what to true down and what to step up |
| 7 to 5 | Benchmark target pricing and set your walk-away | Set the number before Microsoft sets it for you |
| 5 to 3 | Model Copilot and the Azure commit against real demand | Avoid committing to consumption you cannot use |
| 3 to 1 | Open the commercial conversation, structure first | Anchor on your terms, not the proposal |
| 1 to 0 | Close near Microsoft fiscal year end | Quarter and year-end timing favors the buyer |
The baseline work in the first quarter of the timeline is the part most organizations skip, and it is the part that pays for everything else. An independent count of assigned licenses, active users, and dormant accounts gives you the evidence to true down, the data to size Copilot and Azure, and the confidence to hold a walk-away number when the proposal lands.
What the baseline has to contain
A usable baseline is more than an export from the Microsoft 365 admin center. It reconciles three numbers per SKU: what you are enrolled for under the Enterprise Enrollment, what is assigned in the tenant, and what is actively used over a trailing 90 days. The gaps between those three numbers are your negotiation agenda. Enrolled above assigned is shelfware to true down. Assigned above active is reharvesting to do before you count. Active users mapped by role is the input for the E3, E5, and F3 mix and for any Copilot ramp.
Do the same exercise for Azure: trailing twelve months of consumption by subscription, with Azure Hybrid Benefit, reservations, and savings plans modeled in, becomes the only defensible input to a MACC number. Benchmark pricing belongs in the same pack. Without a reference point for what comparable enterprises pay at your seat count and price level, the first proposal becomes the anchor by default.
Action. Stand up the baseline at month 12 and refresh it quarterly. The renewal then inherits evidence instead of three years of drift.
4True-up and true-down: E3, E5, and Visual Studio counting
A Microsoft EA obliges you to true up. When you add users or deploy more of an enrolled product during the year, you report and pay for the increase at the annual enrollment anniversary. What most buyers miss is that the true-up count carries forward into the renewal as your new baseline. Overstating it once raises your floor for three more years.
At renewal you also have a true-down opportunity that does not exist mid-term. You can reset enrolled quantities to your real position before signing the next agreement. If headcount fell, if a business unit was divested, or if shelfware accumulated, this is the moment to remove it. After signature, the new quantities become the floor again, so the reset has to happen before the ink dries, not after.
The products where the count matters most are the per-user suites and the developer subscriptions. Set the E3, E5, F1, and F3 mix by role: frontline workers on F1 or F3, information workers on E3, and only the users who need advanced security or compliance on E5. Developer tooling deserves the same scrutiny. Visual Studio subscriptions are often enrolled in bulk at the Enterprise tier and outlast the projects that justified them, and Project Plan 3 and Visio Plan 2 seats accumulate in pockets nobody owns.
| SKU family | Common overspend | The true-down move |
|---|---|---|
| Microsoft 365 E5 | Whole organization on E5 for a feature few use | Step up only the users who need it |
| Microsoft 365 E3 | Licensed for leavers and dormant accounts | Reset to active, assigned users |
| Microsoft 365 F3 and F1 | Frontline staff on E3 by default | Move eligible roles to frontline SKUs |
| Visual Studio subscriptions | Enterprise tier held after project end | True down to Professional or remove |
| Project Plan 3 and Visio Plan 2 | Seats assigned once, never reclaimed | Reharvest and license active users only |
Run your own count of active versus assigned users in the 60 days before the true-up order is due, not after. Once a true-up order is submitted at the enrollment anniversary, those quantities become contractually enrolled, and Microsoft treats them as the renewal starting point. Deal desks rarely volunteer that a renewal true-down can also cross a price level boundary in Table 1, in either direction. Check the band math before you submit any number.
Action. Reconcile enrolled, assigned, and active counts per SKU before every true-up, and reset at renewal. The count is the negotiation.
5The E5 step-up and Copilot for Microsoft 365
The largest single lever in most EA renewals is the move from E3 to E5, and Microsoft sells it as a security and compliance upgrade. E5 adds advanced security through Microsoft Defender for Office 365 and Defender for Endpoint, compliance and information governance through Microsoft Purview, analytics through Power BI Pro, and telephony through Microsoft Teams Phone. The list is real, but most organizations need only part of it, and only for part of their users.
Two facts give buyers room. First, Microsoft sells E5 component step-ups: the Microsoft 365 E5 Security add-on and the E5 Compliance add-on can be bought on top of E3 without taking the full suite. Second, you do not have to put the whole organization on E5. Map who genuinely needs advanced threat protection or eDiscovery, license those users on E5 or the relevant step-up, and leave the rest on E3 or a frontline SKU.
Indicative published list prices per user per month before EA programmatic and negotiated discounts. Confirm current figures against the Microsoft price list for your agreement and currency.
The arithmetic is the argument. If a quarter of your users need advanced security and nobody outside the SOC and legal needs the rest of E5, the blended cost of E3 plus targeted step-ups is far below a full-suite migration, even after Microsoft discounts the E5 price to make the bundle look inevitable. Price the roles, not the organization.
Indicative monthly list gap between Microsoft 365 E3 and full E5 before EA discounts. The bundle is priced to make this delta look inevitable; role-based mapping defeats it.
Indicative reduction on the M365 component when the suite mix is set by role rather than standardized organization-wide, before any negotiated discount.
Pricing Copilot on your terms
Copilot for Microsoft 365 is the newest addition to the renewal conversation, priced as a per-user add-on on top of an eligible Microsoft 365 base. Microsoft has an incentive to bundle Copilot into the renewal at scale. Buyers should treat it as a separate decision. Run a measured pilot, license the roles where the productivity case is proven, negotiate the per-user price and a ramp schedule that matches adoption, and secure the right to reduce seats if usage does not materialize.
Do not accept an all-user Copilot commitment as a condition of the renewal discount. A discount that depends on a commitment you cannot consume is not a discount. It is a higher floor with a friendlier label.
Run the Copilot decision like a procurement exercise
The Copilot conversation goes better when it has the discipline of any other major purchase. Define the pilot population by role, agree the success metrics before the pilot starts, and measure actual usage from the tenant rather than from survey enthusiasm. Sustained weekly usage by a defined role is a purchase signal. A spike in the first month that decays by the third is a renewal trap.
When the pilot supports a purchase, negotiate three things beyond price: a ramp schedule that adds seats as adoption is demonstrated rather than all at once, a mid-term checkpoint with a contractual right to reduce seats against measured usage, and protection from Copilot being used as the justification for an unrelated uplift elsewhere in the proposal. Microsoft wants Copilot reference customers, and that want is bargaining room. The full pricing and governance detail is in our Microsoft Copilot Licensing Guide 2026.
When Microsoft proposes E5 at a discount conditioned on an all-user commitment, ask the account team to quote the same population as E3 plus the E5 Security add-on at the same discount percentage. The comparison forces the deal desk to defend the delta on the components you would never deploy, and it frequently surfaces a component-level price that was not on the table before.
Action. Quote E3-plus-step-up against full E5 at the same discount, and keep the Copilot volume decision tied to measured adoption, not the renewal incentive.
6Azure MACC commitments and the overcommit trap
Azure commitments belong in the same negotiation as your licensing, and they carry the same risk: committing to consumption you cannot use. A Microsoft Azure Consumption Commitment, the MACC, is a dollar amount you agree to consume over the term in exchange for discounts and access to private pricing. Used well, it lowers your effective Azure rate. Sized wrong, it becomes a shortfall you pay for whether or not you consume it.
The discipline is to forecast real Azure demand from the bottom up, commit to the floor you are confident you will consume, and treat headroom as upside rather than obligation. Marketplace purchases that count toward the MACC, Azure Hybrid Benefit for Windows Server and SQL Server, and reservations or savings plans all change the math. Model them together before you agree a commitment number.
| Azure lever | What it does | Watch for |
|---|---|---|
| MACC sizing | Sets your committed consumption floor | Commit to the floor, not the forecast ceiling |
| Azure Hybrid Benefit | Reuses Windows Server and SQL Server licenses | Confirm Software Assurance coverage first |
| Reservations and savings plans | Discount steady-state compute | Match term length to workload stability |
| Marketplace eligibility | Lets qualifying third-party spend count to the MACC | Confirm which offers qualify before relying on them |
| Shortfall treatment | Defines what happens to unconsumed commitment | Negotiate carryover or term extension in writing |
Understand the MACC decrement mechanics before you size the number. Only eligible Azure consumption and qualifying Marketplace transactions decrement the commitment, and Azure Hybrid Benefit, reservations, and savings plans all reduce the rate at which you burn it down. Buyers who size the MACC off a raw consumption forecast, then apply those optimizations afterward, build in a shortfall by design. At term end an unconsumed balance is typically invoiced, so negotiate carryover or an extension window before signature, not after.
Beyond the MACC: rate, credits, and the funding programs
The commitment number is only half of the Azure conversation. The other half is the rate you pay against it. Negotiated Azure discounts on specific service families, migration funding through Microsoft's partner and incentive programs, and credits tied to named migration projects all sit outside the MACC arithmetic and are easiest to win while the EA renewal is open. Ask for them as line items, tied to workloads you can name, with expiry dates you can actually meet.
Treat credits the way you treat any vendor currency: they have value only if you would have spent the money anyway. A credit pool tied to a migration you have not scheduled is decoration on the proposal. A rate reduction on the storage and compute families you already consume is money.
Action. Model Hybrid Benefit, reservations, and savings plans first, size the MACC to that optimized floor, and put carryover and shortfall terms in the paper.
7Audit and SAM defense, and Unified Support cost control
A Microsoft audit, or the softer Software Asset Management engagement that often precedes one, is a commercial event. Microsoft uses the formal audit clause in the Enterprise Enrollment and the SAM program to surface license gaps, and the findings usually arrive as a proposed purchase. The response that protects a buyer controls scope, controls data, and settles on forward-looking terms rather than a back-dated penalty. Across our audit defense engagements, structured responses of this kind have reduced initial claims by an average of 72 percent.
- Days 1 to 15. Acknowledge in writing, confirm the contractual audit clause and its limits, and route all contact through a single owner. Do not run vendor scripts or share data before scope is agreed.
- Days 15 to 45. Build your own measurement first. Establish entitlements and actual deployment independently so you can test every finding against the Product Terms.
- Days 45 to 75. Compare the claim to your baseline, isolate the technicalities, and prepare the commercial response, often a forward-looking purchase rather than a back-dated penalty.
- Days 75 to 90. Settle into the renewal where that produces the lowest total cost, with the engagement closed in writing.
Unified Support is the quiet line item in the same conversation. Microsoft prices it as a percentage of your eligible product and cloud spend, which means every license you add raises your support bill automatically, including the E5 step-up and the Azure commitment you just negotiated. Scope support to what you actually need, challenge the percentage basis, and compare the quote against the prior Premier model and against third-party support alternatives before you renew. Support should be a costed service, not a tax on growth.
Unified Support: challenge the basis, not just the bill
Three moves contain Unified Support cost. First, isolate the calculation basis: ask Microsoft to show exactly which license and cloud spend lines feed the percentage, because renegotiated Azure rates and removed shelfware should flow through to a lower support number. Second, scope the service: most enterprises consume a small set of reactive support and advisory hours, and a costed comparison against third-party providers for that same scope is the strongest pricing argument available. Third, time the conversation with the EA renewal, because support is most movable when license growth is on the table.
If an audit or SAM engagement overlaps your renewal window, merge the tracks deliberately. A finding that would cost list price as a settlement is frequently worth a fraction of that as part of a renewal Microsoft wants to close by June 30. Keep the standstill in writing and make closure of the engagement a condition of the renewal order.
Action. Route any SAM or audit contact through one owner, measure independently before sharing data, and fold the settlement into the renewal on forward-looking terms.
8Put every concession in the paper
The final discipline is documentation. Microsoft concessions agreed verbally or by email have a way of not surviving contact with the order paperwork. Price caps, true-down rights, Copilot seat reduction rights, MACC carryover, audit standstills, and support scope all belong in the Enterprise Enrollment amendment or the Customer Price Sheet, in clause language your counsel has read. If a term is not in the signed documents, you do not have it.
Keep a concession log through the negotiation, and reconcile it line by line against the final paperwork before signature. The two hours that reconciliation takes is the cheapest insurance in the entire renewal cycle, and it is the step that converts a well-negotiated deal into an enforceable one.
Action. Reconcile a written concession log against the final Enterprise Enrollment amendment before signature. Anything not in the paper does not exist.
Start twelve months out with an independent baseline, anchor on your own license count, sequence the twelve levers with discount last, right-size the E3, E5, and F3 mix, keep Copilot a separate measured decision, size the MACC to optimized consumption, and write every concession — price caps, true-down rights, seat reductions, MACC carryover, audit standstills, support scope — into the Enterprise Enrollment before signature. The durable saving on a Microsoft EA renewal lives in the mix, the structure, and the clause set, not in the headline percentage, and that is where a prepared buyer recovers the multi-year gap.
Key takeaways
- The first EA proposal is built to move. Start preparing 12 months out.
- Anchor on your own license count, not Microsoft's carried-forward quantities.
- Check your price level band before you accept any quote.
- Sequence the twelve levers and negotiate discount last.
- Treat every true-up as a renewal decision, because it sets your floor.
- Price E5 by role, use the E5 Security and Compliance add-ons, and keep Copilot a separate, measured choice.
- Size the Azure MACC to optimized consumption and fix shortfall treatment in writing.
- Merge any audit or SAM engagement into the renewal negotiation.
Frequently asked questions
How much can we save on a Microsoft EA renewal?
Savings depend on your starting mix, the share of shelfware, and the credibility of your alternatives. Across our engagements buyers have averaged 38 percent savings, though the durable value usually comes from a capped uplift and a right-sized E3, E5, and F3 mix rather than the headline discount alone.
Can we reduce Microsoft licenses at renewal?
Yes. A renewal is the one moment you can true down enrolled quantities to your real position. Reset for leavers, divested units, and shelfware before signing, because the new quantities become your floor for the next three years.
Do we have to move from E3 to E5 to get a discount?
No. You can buy the Microsoft 365 E5 Security or E5 Compliance add-on on top of E3, and you can license full E5 only for the users who need it. Do not accept a full-suite or all-user commitment as a condition of the renewal price.
How should we handle Copilot for Microsoft 365 in the renewal?
Treat Copilot as a separate decision. Run a measured pilot, license the roles where the case is proven, negotiate the per-user price and a ramp, and secure the right to reduce seats. Avoid an all-user Copilot commitment tied to the renewal discount.
What should we do first when Microsoft opens a SAM engagement or audit?
Acknowledge in writing, confirm the audit clause and its limits, route communication through one owner, and build your own measurement before sharing data. Aim to settle any gap into the renewal on forward-looking terms.
Get this playbook applied to your EA before the proposal lands. Confidential assessment within one business day.
Book a 30 minute callMicrosoft EA Renewal AdvisoryRelated research: the Microsoft Enterprise Agreement Guide 2026, the Microsoft Audit Defense Playbook 2026, and the Azure MACC Negotiation Guide 2026.