Microsoft EA negotiation in 2026. Nine deals Microsoft prices as one.

A Microsoft EA renewal is nine linked negotiations that Microsoft prices as one volume deal. Each workload added grows the committed base far more than it improves the discount, so price every part separately before you sign.

How does a Microsoft EA negotiation work?

A Microsoft Enterprise Agreement renewal is nine separate negotiations that Microsoft prices as one volume deal. Each is handled by a different Microsoft team at a different moment, and every one adds to the same committed base. Microsoft 365, Azure, Dynamics 365, Power Platform, Sentinel and Unified support all end up tied to one clock.

The agreement sets discount tiers by volume from Level A through Level D, locks pricing for the three year term and reconciles added licenses at an annual True Up. Commercial customers need at least 500 users or devices to sign one, and can spread the cost over three annual payments.

Which nine negotiations sit inside one agreement?

Why do the separate deals all push the base the same way?

Microsoft presents the EA as a discount structure. In practice it works as an aggregation engine that turns nine purchasing decisions into one volume story, where each decision makes the story bigger.

The counter is to split the deal back into its parts: price each workload standalone, commit Azure spend at your own consumption, audit the True Up yourself, and settle Unified in the same round. Our Microsoft EA pillar covers the tiers and the shift away from the EA itself, and the Microsoft knowledge hub holds the wider library.

What is an EA volume tier worth after the November 2025 price change?

One tier step has been worth 3 to 5 percent off Microsoft list price, with Level D the deepest tier. Since November 1, 2025, that discount reaches fewer products, because Microsoft now prices online services the same at Levels A through D, in line with the prices published on Microsoft.com.

The change applies at your first renewal after that date, or when you buy new online services. On premises software pricing did not change, and the Education and U.S. Government price lists were excluded. Our impact analysis of the discount removal covers the effect by product.

• Still tiered. On premises products bought through the EA, such as Windows Server and SQL Server.
• No longer tiered. Microsoft 365, Dynamics 365 and other online services, where the renewal discount is now whatever the account team agrees to grant.

The account plan pitch survived the change. Pulling Dynamics 365, Power Platform and Sentinel onto the agreement is still presented as the route toward Level D, or toward a larger negotiated discount.

Worked example: what three new workloads add to the bill

Say your EA runs at $5,000,000 a year. The account team proposes adding Dynamics 365, Power Platform and Sentinel at $1,200,000 a year and offers 4 percent off the enlarged agreement. Your Unified contract runs at 8 percent of EA spend, and a standalone quote for the scope you would deploy comes to $700,000.

The EA route costs more even after the discount, because the $1,200,000 commitment reflects Microsoft's adoption plan while the standalone quote covers what you would deploy. If your Unified contract also counts spend outside the EA, add 8 percent to the standalone line as well.

The EA route then still costs $292,000 more a year. Collect the standalone quote before the workload conversation starts, so the EA has to beat a real number.

Why we advise against consolidating everything to reach the next tier

Resellers and many procurement teams advise putting as much Microsoft spend as possible on the EA to earn the deepest volume discount. We disagree. A discount only has value against a price you could otherwise pay, and without a standalone quote you cannot tell whether the tier step saved money or simply enlarged the commitment.

The November 2025 change weakens the tier argument further for cloud services, where the level no longer sets the price. Treat each workload as its own purchase that joins the EA only when the EA beats its standalone quote.

How should you size an Azure MACC?

Size the Microsoft Azure Consumption Commitment to your trailing twelve months of Azure consumption, plus only the growth that funded projects will deliver. In the renewals we advised, MACC commitments sized on Microsoft's forward forecast over ran trailing twelve month consumption by 22 to 38 percent.

Microsoft's forecast reflects its own growth plan for your account. Once you sign it, that plan becomes your liability, and an unconsumed commitment is spend no discount can recover. Our MACC sizing guide builds the model line by line.

What happens when you miss the commitment?

You pay the difference. Microsoft's billing documentation states that if you do not reach the MACC total by the end date, the remaining balance is charged as a shortfall in the form of an Azure prepayment credit, and consumption paid from that credit does not count toward any MACC.

Here the forecast sits 32 percent above actual use, inside the range we recorded. Microsoft sends email alerts 90, 60 and 30 days before a commitment ends, far too late to close a gap that size by consuming more.

Where do you find your real Azure consumption?

• Cost Management + Billing. In the Azure portal, open your EA billing account, select Credits + Commitments, then the MACC tile for commitment, consumption to date and remaining balance.
• Cost analysis exports. Export twelve months of actual cost by subscription and service, so the file shows run rate by workload.
• Marketplace spend. Separate MACC eligible Marketplace purchases from the rest. The portal shows which offers decrement the commitment.
• Project pipeline. List migrations with an approved budget and a start date. Anything without both stays out of the commitment.

How do the True Up and the Microsoft 365 mix grow your base?

The True Up is the annual reconciliation that adds licenses deployed during the year to the agreement, and it only goes upward. Microsoft must receive the order between 60 and 30 days before your anniversary, and Microsoft's guidance puts the account team discussion at 120 days. Settle your count before then, using the steps in our True Up guide.

Reductions are a separate right. The Enterprise Subscription Enrollment allows you to raise or lower subscription counts each year, while the standard Enterprise Enrollment, built on perpetual licenses, limits removals. Confirm which one you hold before you plan any reduction.

How does the Microsoft 365 mix set the price of every seat?

The Microsoft 365 mix is the SKU ladder across your seat base, and each seat carries the full three year term once priced. Right size it first: F3 for frontline staff, E3 for most knowledge workers, and E5 only where its security and compliance features are switched on and used.

List price changes make this more pressing for renewals in late 2026 and 2027. Existing agreements keep current pricing only until the next renewal after July 1, 2026, when these per user monthly prices apply.

On 10,000 Microsoft 365 E3 seats, the $3 increase adds $360,000 a year before any discount. Moving 1,500 frontline staff from E3 to F3 at the new prices removes $522,000 a year, which is why the mix review comes before price talks.

How do you check the count before Microsoft states it?

• Licenses page. In the Microsoft 365 admin center, Billing then Licenses shows purchased against assigned for each product. Unassigned seats can be dropped at renewal.
• Usage reports. Reports then Usage shows active users by workload, which separates E5 seats that use E5 features from seats that only use mail and Teams.
• Sign in activity. Microsoft Entra ID sign in logs show licensed accounts with no recent activity, often leavers and service accounts.
• Volume licensing records. The volume licensing pages in the Microsoft 365 admin center, which replaced VLSC, hold your entitlements and past True Up orders.
• Server deployments. For Windows Server and SQL Server, take counts from your inventory tool, because the True Up counts deployments.

How is Unified support priced against the EA?

Microsoft Unified support is priced as a share of your Microsoft spend, typically 6 to 10 percent of EA spend, in Core, Advanced and Performance levels. Because it is a percentage, every dollar added to the agreement raises the support bill, and the tier discount never mentions it.

That makes Unified the negotiation that has to close inside the EA deal. Renewed afterward as an administrative item, it is recalculated on a base the other decisions have just enlarged. See our guides to Unified support negotiation and choosing between Core, Advanced and Performance.

What does the percentage cost as the EA grows?

At 6 to 10 percent, a $5,000,000 EA carries $300,000 to $500,000 a year in Unified fees. Adding $1,200,000 of new workloads raises that by $72,000 to $120,000 a year, before anyone has asked whether you need more support hours.

• Ask for the calculation base. Get Microsoft to state in writing which agreements and products count toward the spend the percentage applies to.
• Price the level against use. Compare last year's support cases and consumed hours with what Core, Advanced and Performance include, and step down if you used the lower level's scope.
• Fix the fee in dollars. Settle a stated amount for each year of the term, so later EA growth does not reopen it.
• Test the alternative. Get a quote from a Microsoft partner for support on the workloads you run, so Unified has a price to beat.

How should you handle ECI funding and co terminus dates?

Tie any ECI funding request to your own migration or deployment program, with named projects and dates, rather than to the Microsoft priorities in the account plan. Microsoft calls these End Customer Investment Funds (ECIF). They usually pay for services delivered by a partner or by Microsoft and do not reduce your invoice.

Check how any Azure credits in the offer are treated. Microsoft's billing rules state that consumption covered by Azure credits from Microsoft does not count toward your MACC, so credits bundled into the deal can make the commitment harder to reach.

Which anniversaries should you align?

Microsoft sets the EA against several anniversaries: Microsoft 365, the Azure MACC, Dynamics, Sentinel and Unified support. Aligned, they form one renewal too large to walk away from, negotiated on a clock set by Microsoft's fiscal year, which closes on June 30.

Co term deliberately where it simplifies your calendar. Leave at least one material workload off cycle where it keeps a live alternative in your hand, because that alternative prices every other conversation.

How do MCA-E and CSP change the negotiation?

The Microsoft Customer Agreement for Enterprise (MCA-E) and the Cloud Solution Provider program (CSP) are the alternative contract shapes. Microsoft has been moving some customers off the EA at renewal, so for 2027 renewals the first question may be which agreement you are offered.

Price the same scope under the EA and MCA-E and under CSP before the EA offer arrives.

What will the account team say, and how should you reply?

• "Adding Dynamics 365 and Power Platform takes you up a tier." Reply: here is our standalone price for the same scope and the net EA figure after Unified. Show us which of our products the new level actually reprices.
• "Our forecast shows your Azure growth supports a larger commitment." Reply: we will commit to our trailing run rate plus funded projects, with a written shortfall remedy.
• "Unified is renewed by a separate team after the EA closes." Reply: then the EA is still open. We sign both together, with the Unified fee fixed against today's base.
• "Aligning every date makes administration easier for you." Reply: we will align the dates that suit our calendar, and the rest keep their own end dates.
• "This pricing is only available if you sign before June 30." Reply: put the offer in writing with its expiry date. We sign when the scope is right.

Which contract terms should you ask for?

1. Price hold on additions. Fix the unit price of products added in years two and three, since new pricing otherwise reaches you mid term through additions.
2. MACC shortfall remedy. The right to extend the commitment period or carry a shortfall into the renewal instead of paying it as a prepayment credit.
3. MACC eligibility in writing. A list of the services and Marketplace offers that decrement the commitment, so a later change cannot shrink what counts.
4. Unified fee cap. A stated dollar baseline for the term, so growth in the EA does not raise it.
5. Subscription reductions. The right to lower Microsoft 365 and Dynamics 365 counts at each anniversary, whatever the enrollment type.
6. ECIF commitment letter. Amount, project, delivery partner and dates, signed before the EA is.
7. Separate end dates. Written confirmation that a named workload keeps its own term.

What have we seen in EA renewals from 2024 to 2026?

Across the EA renewals we advised from 2024 to 2026, the discounts were visible and the base growth was not. The same three patterns kept coming back.

The percentage you see is the smallest number in the transaction, and it is doing the work of a lure.

The common thread was sequence. Each item closed at a different moment with a different Microsoft team, so the combined effect on the base only showed once everything was signed. Make Microsoft win each negotiation separately, on its own numbers.

What to do next

1. 12 months out. Build the trailing twelve month Azure consumption file and map every anniversary, deciding which stay off cycle.
2. 9 months out. Take standalone prices for Dynamics 365, Power Platform and Sentinel, and price the same scope under MCA-E and CSP.
3. 6 months out. Audit the True Up count and the Microsoft 365 mix, so the base Microsoft states is one you already verified.
4. At 120 days. Table the full package, with Unified support priced against the base you are about to change and any ECIF request tied to named projects.
5. 60 to 30 days out. Submit the True Up order and close the EA, MACC and Unified terms together.
6. Before a 2027 renewal. Work through our EA 2027 checklist, or have the Microsoft advisory practice run the sequence with you.

Frequently asked questions