Unified Support is priced as a percentage of what you buy rather than what you use, and quoted fees ran 30 to 60 percent above the value of tickets actually raised
Every licence you buy raises your support bill, whether or not it generates a single ticket. That link is the product, and it is the thing to negotiate.
Prepared by Redress Compliance · August 17, 2026 · Microsoft advisory. 25 to 35 Microsoft Unified Support renewals benchmarked, 2024 to 2025.
Executive summary
Quoted fees ran 30 to 60 percent above the value of tickets actually raised. Across the renewals benchmarked, the quoted price rarely matched the support a client actually used.
The fee is a percentage of total Microsoft licence and cloud spend. So the bill climbs automatically as the estate grows, entirely independently of support demand.
Every licence you buy raises your support bill. Which means a successful Microsoft expansion is also an unbudgeted support increase, arriving without anyone deciding on it.
The percent link is the thing to break. Not the percentage. Arguing the rate accepts the mechanism; the mechanism is what produces the 30 to 60 percent gap.
What the fee is actually attached to
Support pricing normally tracks support. Here it tracks purchasing, and the two move independently.
| Input | Does it move the fee? | Consequence |
|---|---|---|
| Annual licence and cloud spend | Yes, directly | Every purchase raises the support bill |
| Tickets raised | No | Fees ran 30 to 60 percent above their value |
| Severity or response consumed | No | Not reflected in what you pay |
| Estate growth | Yes, automatically | An unbudgeted increase nobody approved |
Read the second and fourth rows together, because that is the whole commercial problem. The one variable that should drive a support fee, how much support you consume, does not affect it. The one that should not, how much software you bought, drives it entirely. A buyer who successfully expands their Microsoft estate has, in the same act and without a separate decision, increased their support bill by a proportion of that expansion.
Break the percent link, not the percentage
Microsoft Unified Support charges a percentage of your annual Microsoft licence and cloud spend. That single design choice produces every finding on this page. Across roughly 25 to 35 Unified Support renewals benchmarked in 2024 and 2025, the quoted price rarely matched the support a client actually used, and quoted fees ran 30 to 60 percent above the value of tickets actually raised.
The gap is not evidence of overcharging in any narrow sense. The product is priced exactly as described. It is evidence that the pricing mechanism has no connection to the thing being sold, and that the disconnection runs in one direction only. An estate that grows pays more without consuming more. An estate that consumes heavily but buys little pays less than its usage would justify. Since most enterprise Microsoft estates grow, most buyers sit on the expensive side of that.
What follows is a negotiating instruction that is easy to state and rarely followed. The lever is the percent link, not the percentage. A buyer who argues the rate down has accepted the mechanism that produces the problem and won a discount on it, which means the same gap reopens with the next licence purchase and keeps reopening for the life of the agreement. A buyer who attacks the linkage, by capping it, by carving spend categories out of the calculation base, or by moving to a structure priced on consumed support, changes what the fee responds to.
The evidence needed is unusually easy to produce, which is the encouraging part. Ticket volume, severity mix, and resolution history are all recorded, and setting the value of that consumption beside the quoted fee produces the 30 to 60 percent gap directly. It is a comparison the buyer can make and the vendor cannot easily dispute, and it reframes the conversation from what the rate should be to what the fee should be attached to. The Software Assurance premium sits in the SA playbook, the renewal sequence in the proposal playbook, and the library in the Microsoft practice.
- Usage exports analysed: inactive accounts, plan right sizing, per user reassignment
- Your renewal quote benchmarked against real closed Microsoft deals
- Every risky clause flagged with the exact quote, the page, and the replacement language
The Microsoft EA renewal playbook
The renewal moves, the EA framework, the SKU framework, and the buyer side moves across the full Microsoft estate.
Get the brief →How to attack it
- Value the support you actually consumed, using ticket volume, severity mix, and resolution history, which is what exposes the 30 to 60 percent gap.
- Negotiate the linkage rather than the rate, because a discount on the percentage leaves the mechanism intact and the gap reopens with the next purchase.
- Cap the calculation base, so estate growth stops translating automatically into support increases nobody approved.
- Carve categories out of the base, particularly spend that generates no meaningful support demand.
- Price alternatives priced on consumed support, which changes what the fee responds to rather than how large it is.
- Model the fee against your Microsoft roadmap, since a planned expansion is also a planned support increase and should be budgeted as one.
What the Unified Support renewals showed, 2024 to 2025
Across roughly 25 to 35 Microsoft Unified Support renewals benchmarked:
How far quoted fees ran above the value of tickets actually raised. The quoted price rarely matched the support a client actually used.
The fee is a percentage of annual Microsoft licence and cloud spend, so it tracks purchasing rather than support demand.
Every licence you buy raises your support bill, whether or not it generates a single ticket, which means a successful Microsoft expansion carries an unbudgeted support increase that nobody separately approved.
The evidence needed to challenge it already exists: ticket volume, severity mix, and resolution history are recorded, and comparing their value to the quoted fee produces the gap directly.
Watch the briefing · 4:06Where the Leverage Sits in a Microsoft EAWhich lines respond to a rate argument, and which need the mechanism changed.
Your first five moves
- Pull ticket volume, severity mix, and resolution history for the trailing year.
- Value that consumption and set it beside the quoted fee, which is the comparison that produces the 30 to 60 percent gap.
- Target the linkage, not the percentage, so the fix survives your next licence purchase.
- Ask for a cap on the calculation base and carve out spend that generates no support demand.
- Price a consumption based alternative. The Microsoft practice builds the comparison with you.
Frequently asked questions
How is Unified Support priced?
As a percentage of your annual Microsoft licence and cloud spend. The fee tracks what you buy rather than what support you consume, and those two move independently.
How far above consumed value do quotes run?
30 to 60 percent above the value of tickets actually raised, across the 25 to 35 renewals benchmarked. The quoted price rarely matched the support a client actually used.
Is that overcharging?
Not in a narrow sense, since the product is priced exactly as described. It is evidence that the pricing mechanism has no connection to the thing being sold, and the disconnection runs one way for most estates.
Why does most of the gap fall on growing estates?
Because an estate that grows pays more without consuming more, while one that consumes heavily but buys little pays less than its usage justifies. Most enterprise Microsoft estates grow.
Should we negotiate the percentage down?
It is the weaker move. A discount on the rate accepts the mechanism, so the same gap reopens with the next licence purchase and keeps reopening across the agreement.
What should we negotiate instead?
The linkage. Cap the calculation base, carve out spend categories that generate no support demand, or move to a structure priced on consumed support.
What evidence do we need?
Ticket volume, severity mix, and resolution history. All are already recorded, and setting their value beside the quoted fee produces the gap directly.
Can the vendor dispute that comparison?
Not easily, which is what makes it useful. It rests on the vendor own support records rather than on a benchmark the vendor can argue is not comparable.
Does a licence purchase really raise support cost?
Yes, automatically and without a separate decision. That is worth naming explicitly in the business case for any Microsoft expansion, because the support increase is a real cost of that expansion.
When should this be modelled?
Against the Microsoft roadmap, not just at renewal. A planned expansion is also a planned support increase, and budgeting it as one removes the surprise rather than the cost.
