Microsoft Unified Support levels: Core vs Advanced vs Performance. Priced on what you buy, not what you use.

Unified Support is priced as a percentage of your Microsoft spend, so the fee grows with every purchase even when cases fall. Core is the right default for most buyers, and an upgrade should follow your incident history.

What are the Microsoft Unified Support levels?

Microsoft Unified Support has been sold in three levels: Core, Advanced and Performance. They rise in response speed, proactive services and price, and all three are priced as a percentage of your Microsoft product and online services spend. None of them is priced on the support you actually use.

Core is the reactive baseline. Advanced adds faster response on critical cases and more proactive hours. Performance adds the fastest response and the most extensive engagement, including the deepest involvement from Microsoft engineers.

How does Microsoft sell Unified Support today?

As of 2026, Microsoft's public site presents the base plan as Unified Enterprise, with optional services layered on top instead of named tiers. The plan details page lists Unified Assured, Mission Critical Services and Value Acceleration Services, which come as Designated Engineering or Enhanced Designated Engineering.

Many contracts and renewal quotes still use the Core, Advanced and Performance names, so the tier question is the same one under different labels. Microsoft publishes these initial response targets for Unified Enterprise:

• Critical (Sev 1). 15 minutes for Azure and 1 hour for all other products, 24x7.
• Sev A. 1 hour, 24x7.
• Sev B. 2 hours, with 24x7 handling available on request.
• Sev C. 4 hours, business hours only.

Read those targets before any upgrade conversation. If the base plan already commits to a 1 hour response on a Sev A case around the clock, the case for paying more has to rest on something the base plan does not give you.

How is Microsoft Unified Support priced, and why does the bill keep rising?

Unified Support is priced as a percentage of your annual Microsoft spend. It is not a flat fee and it is not based on usage. Unified replaced Premier, where you bought a block of support hours, with an all you can use model tied to what you own.

That change removed the hour caps and linked cost to the size of your Microsoft footprint, which raised the bill for most large customers. Premier charged for support consumed. Unified charges for software owned, so every EA true up, every Azure commitment and every Copilot attach raises the support line without a single extra ticket.

What spend does Microsoft count, and at what rate?

Microsoft's published plan details base the fee on your previous 12 months of purchases: cloud services, Azure consumption after discounts and before credits, license only purchases and Software Assurance. The minimum contract price is $50,000. Rates are graduated, so each band of spend carries its own percentage.

The published definition of the base covers almost everything you buy from Microsoft. Treat it as a negotiation item anyway. Confirm line by line what Microsoft counted, and push back on lines that carry no support load, such as a one time true up spike or licenses bought for a system you are retiring.

Worked example: how the support line grows with no new tickets

Say a company spends $6M a year on Azure and $4M on Microsoft 365, and raises roughly the same number of cases every year. In year two, Azure grows to $7M under a larger commitment and a Copilot rollout lifts user product spend to $4.4M.

Spend rose 14 percent and the support fee rose $72,000, or 9.7 percent, with the same case volume. The accounts we review show the same pattern, which we cover below. The full band by band cost of each level is worked in our Unified Support pricing analysis.

Why the support renewal belongs with the EA renewal

Because the license spend feeds the fee, the two negotiations cannot be separated. Microsoft's sales teams have the most room to trade during the EA renewal, so time the support negotiation to run alongside it. Our note on aligning the support renewal with EA timing covers the calendar in detail.

When is Advanced or Performance worth paying for over Core?

Only where two years of incident history and a map of workload criticality both say so. For most buyers, Core is the right default and any upgrade has to be argued from evidence. In our reviews, the level bought was almost always higher than the incident history justified.

The reason is how the decision gets made. The account team frames Advanced or Performance as safety, and the tier is chosen in that conversation instead of from the ticket data. Proactive hours that go unused are still paid for, and that premium is margin for Microsoft.

Why we disagree with buying a higher tier as insurance

The usual advice is to buy one tier above what you think you need, because an outage costs more than the premium. We disagree. The premium is paid every year on a growing spend base, while faster response only matters on the few critical cases you raise. Find those cases in your history and price the upgrade against them.

The level decision is an evidence decision, and the evidence sits in your own ticket data.

How do you build the workload criticality map?

List the systems that would actually call on faster response, then test each one against its incident record. An upgrade from Core is justified only where the map and the history agree.

1. List candidate workloads. Start with systems that carry revenue or regulated operations, such as ERP on Azure, customer facing apps, identity and email.
2. Price an hour of downtime for each. Use the business owner's figure, and write down how it was reached.
3. Pull the Sev 1 and Sev A cases per workload for the last two years, with time to first response and time to resolution.
4. Compare the actual response with the base plan targets. If Core or the base plan met the need, faster response would not have changed the outcome.
5. Upgrade only the gaps. If one workload needs more, ask whether Mission Critical Services or Designated Engineering scoped to that workload covers it more cheaply than a full tier.

When does Performance pay for itself?

It rarely does. Performance suits mission critical systems where downtime is measured in large sums per hour, and where you have a record of critical incidents in which faster engagement shortened the outage. For most buyers the extra cost outruns the benefit. The decision that matters is the gap between Core and Advanced.

How do you check what support you actually use?

Build a two year usage file before the renewal: incidents by severity, time to response, and proactive hours bought versus consumed. Microsoft holds this data, and it is rarely brought to the table by the account team, so collect it yourself.

• Services Hub. Unified customers manage support requests and proactive services there. Export the case list with severity and dates.
• Azure portal. Help and support lists every Azure case raised, with severity.
• Microsoft 365 admin center. The support section shows service requests raised for Microsoft 365.
• Your CSAM. Ask the Customer Success Account Manager for the consumption report on proactive services and hours, by quarter.
• Your own ITSM tool. Match internal tickets escalated to Microsoft against the Microsoft case list, so nothing is counted twice.
• The last three invoices. Check which spend lines Microsoft included in the base and at which rate.

How does a third party support quote change the Unified renewal?

It changes the price Microsoft offers, whether or not you switch. In our reviews, a credible third party quote improved renewal terms by 10 to 20 percent. The percentage rate, the spend base it applies to and the proactive hours are all open to negotiation, and Microsoft gives most when it believes you would sign elsewhere.

Independent providers support Microsoft environments at materially lower cost where systems are stable. Pay per incident fits organizations whose ticket volume never justified an all you can use fee. The comparison is worked in our alternatives analysis.

Making the alternative credible

A quote only works if the account team prices the risk that you will act on it. Get a written proposal with named coverage, response targets and a start date aligned to your Unified expiry, and let Microsoft see that procurement and the technical owners have reviewed it.

The order of the conversation itself, rate, base and hours, is set out in our Unified Support negotiation guide.

What have we seen in recent Unified Support reviews?

Across roughly 30 to 40 Microsoft Unified Support reviews in 2024 and 2025, the level chosen was usually higher than actual usage justified. The spend based model worked as designed: the fee grew with the license footprint, the tier grew with concern about outages, and neither followed the ticket queue.

• Overbought tiers. In 24 of the 38 accounts we reviewed, Advanced or Performance proactive hours went 30 to 60 percent unused while the fee climbed.
• Spend growth with flat case volume. The support line rose 8 to 15 percent a year from license growth alone, before any change in how much support was used.
• One shared record. The accounts that corrected the level had a two year usage file, incidents by severity and proactive hours consumed, which turned the renewal from a safety conversation into an evidence conversation.

Microsoft can measure every case and every proactive hour you consume. At renewal, that record only helps you if you have built your own copy of it.

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

Expect the same few lines at most Unified renewals. Each has a reply you can support with your own data.

• "Moving to Core puts your critical systems at risk." Show the Sev 1 and Sev A cases from the last two years, and the published base plan response targets they would have received.
• "The percentage is standard and cannot change." Ask for the rate applied to each band of your spend, and for a cap on annual growth in the fee.
• "Your spend base is set by policy." Ask for the line by line base, and name each line that carries no support load.
• "Third party providers cannot reach Microsoft engineering." Ask the provider how it escalates product defects, then count how many of your own past cases actually needed a Microsoft code fix.
• "Unused proactive hours show you need more engagement, not less." Reply that unused hours show the allocation is too large, and ask to cut it or convert it to services you will use.

Which Unified Support terms should you ask for at renewal?

Ask for terms that stop the fee growing faster than your support needs. Each one below addresses a way the spend based model raises cost.

• A cap on annual fee growth. Limits the effect of EA true ups and Azure growth on the support line.
• A written base statement. A line by line list of the spend counted, so the next renewal starts from an agreed figure.
• Proactive hours sized to consumption. Set the allocation from your usage file, with the right to convert unused hours.
• A mid term review of the level. The right to step down a tier if the incident record does not support the one you bought.
• Coterminous dates with the EA. One renewal date keeps both negotiations in the same room.

Timeline before your Unified renewal

Buyers who want outside help can use our Unified Support review service, which builds the usage file and the comparison.

What to do next

1. Pull two years of history. Export incidents by severity and proactive hours consumed, because the level decision rests on that data.
2. Map each critical workload to the response it needs. Let the map, not the account team, argue any upgrade from Core.
3. Confirm and challenge the spend base line by line, since every new Microsoft purchase raises the fee.
4. Get a third party quote before the renewal. It improves terms whether or not you switch.
5. Ask for a growth cap and a written base statement in the renewal paperwork.
6. Review the level at every renewal against usage, timed with the EA. Our Microsoft practice runs the comparison with you.

Frequently asked questions