Microsoft Unified Support is priced as a percentage of your annual Microsoft licensing and online-services spend, not per incident. That single design choice means your support bill rises every time your Azure or M365 spend rises — even if your ticket volume never moves. Most enterprises pay 6–10% of total Microsoft spend on Unified Support, and most of them can cut it 30–50% through scope redesign and credible third-party leverage. Here is the model and the playbook.
Unified Support is Microsoft's enterprise support programme, the successor to Premier Support. It prices support as a percentage of your total Microsoft spend rather than per incident: roughly 8–10% of on-premises licensing, 9–12% of Microsoft 365 and Dynamics online subscriptions, and 6–8% of Azure consumption. Because the fee tracks spend rather than usage, the model rewards Microsoft when your estate grows and penalises you for buying more Microsoft — the more you commit, the more you pay for support you may not use proportionally.
The core problem: support cost is decoupled from support consumption. A firm that doubles Azure spend can double its Unified Support bill while opening the same number of tickets. The fee is a tax on growth, not a price for service.
This is a sub-guide in our Microsoft cost optimization pillar. It pairs with the Azure MACC commitment and Azure FinOps guides, and sits under our Microsoft vendor practice.
The list calculation is mechanical, but the negotiated outcome is not. Below are the benchmark fees we see at list versus the targets we hold in negotiation, by total Microsoft spend band. The effective percentage falls as spend rises — but only if you push it; left alone, large accounts pay disproportionately because nobody re-tests the scope.
| Annual Microsoft spend | Unified Support at list | Effective % at list | Benchmarked target | Reduction |
|---|---|---|---|---|
| $10M | $0.90M | 9.0% | $0.55M | 39% |
| $30M | $2.40M | 8.0% | $1.40M | 42% |
| $60M | $4.20M | 7.0% | $2.50M | 40% |
| $120M | $7.80M | 6.5% | $4.40M | 44% |
Premier Support is gone for new agreements, but the comparison still frames the conversation, because third-party support providers now price the way Premier used to — against a service envelope, not your spend. The table below is the structural comparison we walk clients through.
| Dimension | Unified Support | Legacy Premier | Third-party support |
|---|---|---|---|
| Pricing basis | % of Microsoft spend | Per incident / hours | Fixed service envelope |
| Grows with Azure spend | Yes | No | No |
| Typical cost vs Unified | Baseline | — | 30–60% lower |
| Product-source escalation | Microsoft direct | Microsoft direct | Via provider |
| Best for | High-touch, deep Azure | — | Stable, mature estates |
We benchmark your fee against your spend band and your actual ticket history, then run the re-scope. Most clients see 30–50%.
Three, in order of impact. First, scope: Unified is sold as all-product, all-environment coverage, but you can carve coverage to the products that genuinely need vendor-direct escalation and self-serve the rest. Second, tier right-sizing: the Core / Advanced / Performance tiers carry materially different multipliers, and most accounts are over-tiered relative to their incident profile. Third, and the one that actually moves Microsoft's number, a credible third-party support alternative on the table during the negotiation window.
"Microsoft's deal desk does not discount Unified Support because you ask nicely. It discounts when a costed third-party quote is sitting in the room."
Third-party support fits a mature, stable estate where most incidents are operational rather than deep-product, and where the version cadence is steady. It is a weaker fit for organisations mid-migration into new Azure services or running bleeding-edge Microsoft AI features that need vendor-direct escalation. The decision is rarely all-or-nothing: the strongest position is hybrid — third-party for the stable on-prem and commodity estate, Unified for the deep-Azure and emerging-product surface — which also keeps a credible alternative live for the next renewal.
| Estate profile | Best-fit model | Indicative saving |
|---|---|---|
| Mature on-prem + steady M365 | Third-party | 40–60% |
| Mixed, some deep Azure | Hybrid | 25–40% |
| Heavy Azure + emerging AI | Unified, re-scoped | 20–35% |
The full benchmark percentages by spend band, the third-party comparison model, and the renewal-timing calendar.
Unified Support usually co-terms with the Enterprise Agreement, which is both a risk and an opportunity. The risk is that support gets bundled into the EA conversation and waved through at list while attention is on the licensing lines. The opportunity is leverage: the EA is the moment Microsoft most wants your signature, so it is the moment a support re-scope has the most weight. Sequence it deliberately — settle the licensing and Azure commitment first, then bring support in as a separate negotiation with the alternative quote in hand. The full renewal sequencing is in our complete Microsoft EA guide, and the reservations layer it interacts with is in Azure Reservations & Savings Plans.
For estates above $30M annual Microsoft spend, a Unified Support re-scope handled as a focused software contract negotiation typically returns 20–40 times its advisory cost in the first year alone — and because it is structural, it compounds across the agreement term.
$1.8B+ in documented client savings across 340+ engagements. Buyer-side only since 2016. Gartner recognised.
Weekly compliance intelligence for IT leaders.
