Alternatives to Microsoft Unified Support. Third party, pay per incident or hybrid?

Microsoft Unified Support charges 8 to 10 percent of total Microsoft spend, however many tickets you raise. Third party support, pay per incident and hybrid models cut that line by 30 to 60 percent when matched to your real case volume.

How is Microsoft Unified Support priced?

Unified Support is priced as a percentage of your total annual Microsoft spend, usually between 8 and 10 percent depending on tier and negotiated terms. The price has no link to how much support you use. At equal spend, a customer raising 200 tickets a year pays the same rate as one raising 20.

Microsoft introduced Unified Support in 2017 as the replacement for Premier Support, which had been bought as a block of hours. Unified launched with Core, Advanced and Performance tiers. At most enterprises the switch roughly doubled the support line without changing how cases were handled.

What rates does Microsoft publish for Unified Enterprise?

Microsoft now sells the base plan as Unified Enterprise and publishes graduated rates for contracts starting on or after February 1, 2023. Each band of spend carries its own percentage, so the blended rate falls as spend rises. The minimum contract price is $50,000.

• Infrastructure products (Azure and on premises). 10 percent on the first $1.8M of annual spend, stepping down band by band to 1.75 percent on spend above $120M.
• User products (Modern Work and Business Applications). 7.5 percent on the first $1.5M, stepping down to 3.5 percent on spend above $15M.
• Microsoft's own example. $6M of annual Azure spend is charged 10 percent on the first $1.8M and 7 percent on the next $4.2M. That is $180,000 plus $294,000, or $474,000, a blended rate of 7.9 percent.

The bands apply to your previous 12 months of Microsoft purchases: cloud services such as Microsoft 365 and Dynamics 365, Azure consumption after discounts and before credits, license only purchases and Software Assurance. Microsoft does not let you leave products out of that base. Our Unified Support pricing guide covers the bands in detail.

What do the three Unified Support tiers include?

Many existing contracts still refer to the original three tiers, and renewal quotes are often compared against them. The percentages are typical shares of Microsoft spend for each tier.

Unified Enterprise today commits to 24x7 response for Critical (Sev 1) cases, within 15 minutes on Azure and 1 hour elsewhere. Sev A gets 1 hour, Sev B 2 hours (24x7 on request) and Sev C 4 hours in business hours. Our guide to choosing between Core, Advanced and Performance compares the older tiers.

What have we seen in recent Microsoft support reviews?

Across roughly 30 to 45 Microsoft support reviews we ran in 2024 and 2025, the Unified Support line was the least examined large cost in the Microsoft budget. Three patterns recurred.

• Third party pricing. Providers delivered the same SLA coverage at 35 to 55 percent of the Unified price in every benchmark we ran. Across the 40 reviews in our 2024 to 2025 file, the median third party price was 45% of Unified, a median saving of 55% on the support line.
• Growth without tickets. Unified cost grew 8 to 15 percent a year on Microsoft spend growth alone, with no rise in the number of tickets raised.
• Low volume customers. Organizations raising under 50 tickets a year overpaid the most, often by a multiple, against what the same cases would have cost on pay per incident.

What does Unified Support cost over five years?

Over five years the percentage model costs far more than the first invoice suggests, because the rate applies to a growing spend base. Take a hypothetical company paying $15M a year for Microsoft licensing and 9 percent for Unified Support. Year one costs $1.35M.

Now grow Microsoft spend by 8 percent a year, with support consumption flat. The table sets Unified against a third party quote priced at 45 percent of year one Unified, with a 3 percent annual cap on increases.

The five year Unified cost reaches $7.9M. The third party line totals about $3.2M, a difference of about $4.7M or 59 percent. With a flat price hold for all five years instead of the cap, the saving passes 60 percent.

The flat 9 percent keeps the arithmetic visible. Microsoft's bands may give a buyer this size a lower blended rate, so rerun the table with the rate on your invoice.

Why do Copilot and Azure growth raise the support bill?

Every dollar added to the spend base carries the Unified percentage with it. Copilot seats sit in Modern Work spend and Azure consumption in infrastructure spend, so a Copilot rollout lifts the support invoice before anyone raises a Copilot ticket.

Model both lines before renewal: seat counts from our Copilot pricing guide and consumption forecasts against the Azure pricing page. Third party support and pay per incident both break the link, since their price follows the deployments and cases they cover.

Who are the third party Microsoft support providers in 2026?

A small group of established firms sell 24/7/365 SLA backed Microsoft support as a replacement for Unified, staffed by former Microsoft engineers and Most Valuable Professionals (MVPs). Pricing runs 30 to 50 percent of the equivalent Unified cost, because it is sized to your actual deployment rather than your total Microsoft spend.

What do you give up when you leave Unified Support?

You lose direct escalation into Microsoft engineering and the named Customer Success Account Manager (CSAM). You also lose the proactive assessments delivered through Microsoft Services Hub. Case handling and SLA coverage carry over to a good provider.

The rare case that needs a Microsoft code fix can still go through a CSP partner, Microsoft's own pay per incident service, or a provider with its own Microsoft support agreement. Confirm which route applies before you sign.

Is third party Microsoft support legal?

Yes. Established providers work inside clear legal limits: they do not modify Microsoft software, redistribute its code or break licensing terms. They provide advisory and break fix support for products you already license, and your use rights sit in the Microsoft licensing terms library, whoever supports you.

Security updates for products still in support come with the license, so leaving Unified does not cut off monthly patches. Extended Security Updates for retired products are bought separately under any model.

How does pay per incident Microsoft support work?

With pay per incident you pay only for the cases you open, at a per case rate of typically $250 to $500 depending on complexity and SLA. There is no standing contract and no share of spend. A customer raising 30 cases a year at $400 pays $12,000, less than a quarter of the $50,000 Unified Enterprise minimum.

Microsoft sells its own version as Professional Support. It defines an incident as a single support issue and the reasonable efforts needed to resolve it, and works incidents during business hours until they are resolved. That makes it a poor fit for outages outside the working day.

When is pay per incident the right fit?

• Good fit. Stable workloads, mature internal Microsoft skills and infrequent support needs.
• Poor fit. Active migrations, regulated environments and high incident volume.
• What you trade away. Proactive support, a named engineer and architecture reviews. Each case is bought and handled on its own.

What hybrid Microsoft support models work?

Many enterprises combine third party support with a fallback. Paid support covers the active production workloads, and spend on the stable remainder is kept to what it actually needs.

Which hybrid pattern fits which buyer?

• Third party support plus pay per incident. Active production workloads sit with the third party provider under a 24/7 SLA. Legacy or stable systems are covered through pay per incident as needed.
• Third party support plus a smaller Microsoft contract. Buyers who want a direct Microsoft channel for a few workloads often assume they can keep Unified on those alone. Microsoft prices Unified on all your Microsoft purchases, so a partial Unified contract is not available. The direct channel has to come from an Azure support plan or Professional Support cases instead.
• Third party support plus CSP partner support. CSP customers use the partner's tier 1 support for Microsoft 365, with third party support covering Azure and on premises systems. Our CSP licensing guide explains what the partner has to provide.
• Third party support plus an Azure support plan. Microsoft sells Azure support directly at $100 a month for Standard and $1,000 a month for Professional Direct. Where most escalations are Azure, Professional Direct keeps a Microsoft channel for that platform alone.

How should you choose a Microsoft support model?

Four questions decide it: consumption, spend trajectory, workload criticality and internal expertise. Answer them with your own data before any vendor conversation.

What four questions decide the model?

1. What is your annual support consumption? Under 50 tickets a year points to pay per incident. Fifty to 200 fits third party providers. Above 200 may justify Unified, depending on case complexity.
2. What is your Microsoft spend trajectory? Copilot attach and Azure expansion speed up Unified cost growth. Third party support and pay per incident both separate support cost from licensing spend.
3. How critical are the workloads? Regulated, real time and compliance heavy workloads may justify the premium Unified tiers. Standard enterprise workloads do not.
4. How strong is your internal Microsoft expertise? Mature internal teams need less outside help and suit pay per incident. Teams with limited expertise benefit from a named third party relationship.

How do you check your own support consumption?

• Services Hub. Unified customers can list their support requests here. Count the last 12 months of cases by severity and product.
• Azure portal. Help + support, then All support requests, shows Azure cases by subscription.
• Microsoft 365 admin center. Support, then View service requests, lists Microsoft 365 cases.
• Your Unified order and invoice. These show the rate and the spend it was applied to. Check the plans in that base against the Microsoft 365 enterprise overview and look for products you no longer run.
• Your own service desk tool. Tag every ticket escalated to Microsoft. The escalated share is what outside support actually has to cover.

How does the answer change for a smaller and a larger buyer?

Say a company spends $2M a year with Microsoft and raises 25 cases. At the typical Unified rates that support line costs $160,000 to $200,000. The same 25 cases on pay per incident, at $250 to $500 each, cost $6,250 to $12,500.

A company spending $40M with 400 cases a year, some on regulated real time systems, is different. Unified can make sense there, and so can third party support paired with Azure Professional Direct if those systems run on Azure. Price both against the real case mix before deciding.

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

The account team will usually argue that you need Microsoft engineering, that leaving is risky, and that renewing now protects your rate. Each argument has a factual answer.

• "Third party providers have no access to Microsoft engineering." Ask how many of your cases in the last 12 months needed a Microsoft code fix. Then confirm the escalation route your provider or CSP partner offers for that handful.
• "Leaving Unified puts your environment at risk." Ask which clause ties security updates or the product support lifecycle to Unified. Neither depends on it.
• "We can hold your rate if you renew now." A held rate still grows with every dollar of new spend. Ask for a cap on the total support fee in dollars.
• "Unified has to renew with your Enterprise Agreement." Unified is a separate contract with its own term. Align the dates only when it helps you, as our guide to aligning support renewal with EA timing explains.

Why we disagree that Unified is the safe default

The account team's position is that Unified is the only credible enterprise support option. We disagree, because in most reviews we ran, providers staffed by former Microsoft engineers resolved the same case mix at a fraction of the price, and the rare escalation routed cleanly through CSP or pay per incident.

Size support to your ticket volume and spend trajectory, run a provider RFP, and treat Unified as one of three options. A percentage of spend fee grows with Microsoft's revenue, whatever your support needs.

Unified Support is Microsoft's default offer. Price it against your real ticket volume and the case for paying a share of spend gets much weaker.

How long does it take to leave Unified Support?

Plan six to twelve months. The Unified notice period, provider procurement and run book handover set the calendar. Customers who squeeze the timeline below six months tend to hit operational gaps during handover.

What are the phases of the transition?

Read the notice terms in your Unified order before setting any other date, then work back from the renewal.

What are the common pitfalls when leaving Unified Support?

Five mistakes recur, and each is avoidable.

1. Letting Microsoft frame the conversation. If the first quote you see is the Unified renewal, every alternative gets judged as a risk against it. Get provider quotes and your case history in hand before the account team's renewal meeting.
2. Ignoring the spend trajectory. Benchmarking only the headline rate misses the multiyear exposure as Microsoft spend grows.
3. Choosing the wrong alternative for your profile. Pay per incident for high volume support creates gaps. Third party support for very low volume is overspend.
4. Compressing the transition. A cutover rushed into fewer than six months leaves gaps at the worst moment.
5. Skipping the run book. A provider supports what is documented. Undocumented tribal knowledge surfaces as a gap in the first major incident.

What to do next

1. Pull your Unified invoice and ticket history. Establish the percentage you pay, the spend base and the cases you actually raise.
2. Model the trajectory. Project Microsoft spend over five years with Copilot and Azure growth, and put the Unified line on top.
3. Price the three alternatives. Cost third party support, pay per incident and a hybrid against your real consumption.
4. Run a provider RFP. Shortlist two or three third party providers and test SLA, escalation and references.
5. Map the escalation path. Confirm how the rare Microsoft engineering case will route through CSP, a provider agreement or pay per incident.
6. Document the run book. Close the tribal knowledge gap before handover, because the provider can only support what is written down.
7. Set notice and cutover dates. Work back from the Unified renewal across a six to twelve month calendar. If you want an independent team to run it, our Vendor Shield subscription covers the full exit.

Frequently asked questions