This article is part of our Microsoft Knowledge Hub. For Unified Support negotiation help, see Microsoft Contract Negotiation Service. For cost reduction strategies, see Microsoft Advisory Services. For EA transition guidance, see our Microsoft EA Optimization Service.

Why Choosing the Right Unified Support Tier Is a Strategic Decision

Microsoft Unified Support replaced Premier Support in 2018, fundamentally changing how enterprise support is priced. Under Premier, you purchased a defined number of support hours and incidents. Under Unified, you pay a percentage of your total annual Microsoft spend — licences, subscriptions, and Azure consumption combined. As your Microsoft spend grows, your support cost grows automatically, regardless of whether your support needs have changed.

This pricing model creates a structural incentive problem. Microsoft benefits when you are on a higher tier (higher percentage means more revenue) and when your Microsoft spend grows (same percentage on a larger base means more revenue). Microsoft’s sales teams are compensated accordingly. The recommendation you receive from your Microsoft account team is not objective — it is influenced by Microsoft’s revenue targets.

The organisations that manage Unified Support costs effectively share three disciplines: they understand exactly what each tier provides (and does not provide), they match the tier to their actual operational needs (not Microsoft’s characterisation of their needs), and they negotiate the percentage rate regardless of which tier they choose. This guide provides the analytical framework for all three.

“The single most common mistake we see in Unified Support is enterprises on the Performance tier who use it like an Advanced tier. They pay for a dedicated TAM, comprehensive proactive services, and the fastest SLAs — then open the same reactive break-fix tickets they would open on Advanced. The difference in cost between the two tiers often exceeds $500K annually. If you are not actively consuming the proactive services, you are not on the right tier.”

The Three Tiers Compared — Feature by Feature

Understanding what each tier actually includes — beyond the marketing descriptions — is the foundation of an informed decision. The following comparison covers every dimension that affects both cost and operational value.

DimensionCoreAdvancedPerformance
Critical Issue Response (Sev A)1 hour (24x7)1 hour (24x7) with priority routing30 minutes or less (24x7) with dedicated escalation
Standard Issue Response (Sev B)8 business hours4 business hours4 business hours with higher queue priority
Low-Priority Response (Sev C)Next business day8 business hours8 business hours
Reactive Support CasesUnlimitedUnlimitedUnlimited
Proactive ServicesVery limited — mostly paid add-onsModerate — planning workshops, health checks, advisory hoursComprehensive — architecture reviews, performance tuning, on-site visits
Account ManagementNone — general support poolService Delivery Manager (SDM) assignedDedicated Technical Account Manager (TAM) plus designated support engineers
Escalation SupportStandard processSDM-assisted with priority handlingTAM-driven with direct access to product engineering teams
On-Site SupportNot includedLimited (add-on or included days vary)Included — regular on-site visits from TAM and engineers
Typical Cost (% of Spend)6 to 8%~10%15%+ (often 18 to 20% before negotiation)
Minimum Annual Fee~$25K~$50K~$100K+

Core Support — When It Is Enough and When It Is Not

Core is the right tier for organisations where Microsoft products are important but not mission-critical in a way that demands sub-hour response times or dedicated technical account management. The typical Core customer runs M365 for productivity, uses Azure for non-production or secondary workloads, and has internal IT teams capable of first-line troubleshooting.

Core Is Right When: Your internal IT team handles most issues without Microsoft escalation. You open fewer than 50 support cases per year. Your critical systems have alternative support paths (third-party, partner, or internal). You are cost-sensitive and willing to accept slower response times for non-critical issues.

Core Is Not Enough When: You run production workloads on Azure with uptime requirements above 99.9%. Your organisation lacks deep Microsoft technical expertise internally. You experience complex, multi-product issues that require coordinated escalation. You need proactive guidance for cloud migration, security hardening, or architecture optimisation.

Core and Third-Party Strategy: Many organisations pair Core Unified Support with third-party Microsoft support providers (such as US Cloud or Ensono) that offer faster SLAs at a fraction of the Performance tier cost. This hybrid approach provides Core-level pricing with Advanced-level responsiveness.

Core Cost Example: An organisation with $8M annual Microsoft spend on Core at 7% pays $560K per year for support. The same organisation on Performance at 17% pays $1.36M — a difference of $800K annually for faster SLAs and proactive services that may or may not be fully utilised.

Advanced Support — The Middle Ground Most Enterprises Should Evaluate First

Advanced is the most frequently under-considered tier. Microsoft’s sales teams tend to push organisations from Core directly to Performance, skipping Advanced because Performance generates more revenue. Yet for the majority of mid-to-large enterprises, Advanced provides the optimal balance of responsiveness, proactive guidance, and cost efficiency.

The Service Delivery Manager (SDM) assigned under Advanced acts as your single point of accountability within Microsoft’s support organisation. While not as deeply embedded as a Performance-tier TAM, the SDM ensures your critical cases are prioritised, escalations are managed, and your support experience is coordinated rather than fragmented across the general support pool.

The proactive services included with Advanced — typically 15 to 25 days annually of planning workshops, health checks, and advisory sessions — address the most impactful needs for the majority of enterprises. Architecture reviews before major cloud migrations, security posture assessments, and M365 adoption workshops are the proactive activities that deliver measurable ROI. Performance includes more proactive days, but analysis consistently shows that enterprises consume only 40 to 60% of their Performance-tier proactive allocation. Advanced-tier allocations, being smaller, are utilised at 70 to 85% — meaning the return per proactive day is significantly higher.

Advanced also includes the same unlimited reactive support as Performance. The primary SLA difference is at the Severity A level: Performance may offer 15 to 30 minute response, while Advanced offers 1 hour. For most organisations, the practical difference in incident resolution time between a 30-minute response and a 1-hour response is negligible — because resolution time is dominated by diagnostic and remediation work, not the initial response.

Mini Case Study: Insurance Company Saves $480K by Downgrading from Performance to Advanced

Situation: A mid-tier insurance company with $12M annual Microsoft spend had been on Performance-tier at 16% — costing $1.92M annually. An internal review revealed: the dedicated TAM spent 60% of their time on routine ticket management, only 12 of 48 included proactive service days were used in the prior year, and 85% of support cases were standard break-fix issues.

What happened: We helped the client analyse two years of support ticket data, quantify value of proactive services consumed, and negotiate a transition to Advanced tier at 10% with an enhanced SDM allocation and 15 preserved proactive service days.

Result: Annual support cost dropped from $1.92M to $1.2M (Advanced at 10%) — a saving of $720K. After investing $240K in a third-party provider for enhanced Azure SLAs, the net annual saving was $480K. No degradation in support quality after 12 months.

Takeaway: Performance-to-Advanced downgrades are the highest-ROI Unified Support optimisation. If you are not consuming the majority of your proactive allocation and your critical case volume is low, Advanced delivers 90% of the value at 60% of the cost.

Performance Support — When the Premium Is Justified

Performance is the right tier for a specific type of organisation: one where Microsoft Azure is the primary production platform, where downtime is measured in revenue loss per minute, and where the organisation actively consumes proactive services to prevent issues rather than just reacting to them.

The dedicated TAM in the Performance tier provides value that cannot be replicated by lower tiers — but only if the organisation engages the TAM proactively. A TAM who understands your architecture, your business cycles, and your technical debt can prevent incidents that would otherwise require reactive support. They can coordinate across Microsoft product teams in a way that general support cannot. They can secure early access to patches, private fixes, and engineering escalations not available at other tiers. But all of this value requires active engagement. A Performance TAM who is treated as a ticket coordinator — rather than a strategic technical adviser — is an expensive misallocation of resources.

Justified: Mission-Critical Azure Workloads. Organisations running tier-1 production applications on Azure — financial trading platforms, healthcare systems, e-commerce engines — where a 30-minute response advantage over a 1-hour response can prevent six-figure revenue loss.

Justified: Complex Multi-Product Environments. Enterprises using a deep Microsoft stack — Azure, M365, Dynamics 365, Power Platform, SQL Server — where issues frequently span multiple products and require coordinated resolution. A dedicated TAM who understands the entire environment resolves cross-product issues 40 to 60% faster than general support.

Not Justified: Primarily M365 and Productivity Use. Organisations whose Microsoft footprint is predominantly M365 for email and collaboration. M365 issues are typically not complex enough to require a dedicated TAM or the fastest SLAs. Advanced — or even Core with good internal IT — is sufficient and saves $500K to $1M+ annually.

The Pricing Model — Understanding How Microsoft Calculates Your Support Cost

Unified Support pricing is based on a percentage of your total annual Microsoft spend — a number Microsoft calls your “eligible product and online services revenue.” This includes M365 and Office 365 subscription fees, Azure consumption (including Reserved Instances), Dynamics 365 subscriptions, Power Platform licences, and on-premises licence purchases with Software Assurance.

The critical implication: as your Microsoft spend grows, your support cost grows automatically — even if your support needs remain constant. An organisation that grew Azure consumption by $2M in a year at a 15% Performance rate sees an automatic $300K increase in its Unified Support bill without receiving any additional support services.

Annual Microsoft SpendCore (7%)Advanced (10%)Performance (16%)Performance (Negotiated 12%)
$5M$350K$500K$800K$600K
$10M$700K$1.0M$1.6M$1.2M
$20M$1.4M$2.0M$3.2M$2.4M
$50M$3.5M$5.0M$8.0M$6.0M

Every percentage point of negotiated reduction on a $20M Microsoft estate saves $200K annually. On a $50M estate, $500K. The rate is always negotiable.

Negotiation Strategies — Reducing Your Rate at Any Tier

Regardless of which tier you select, the percentage rate is negotiable. Microsoft’s published rates (6 to 8% for Core, approximately 10% for Advanced, 15%+ for Performance) are starting positions, not final prices. Organisations with strong negotiation strategies consistently achieve 20 to 40% reductions from the initial rate.

1. Benchmark Your Rate Against Peers. Request anonymised benchmarking data from your independent negotiation adviser or industry peers. If your peer group is paying 11% for Performance and Microsoft is quoting you 17%, you have a factual basis for negotiation.

2. Quantify Your Actual Support Consumption. Pull 24 months of support ticket data: total cases opened, severity distribution, average resolution time, and proactive services consumed. If you opened 30 critical cases in two years and used 15 of 48 proactive days, you have objective evidence that your consumption does not justify the highest tier or rate.

3. Introduce Competitive Alternatives. Third-party Microsoft support providers (US Cloud, Ensono, and others) offer enterprise-grade support with comparable or better SLAs at 30 to 50% lower cost than Unified Support. Presenting a credible third-party proposal creates genuine competitive pressure that Microsoft’s retention team responds to with rate reductions.

4. Negotiate a Spend Growth Cap. Request a clause that caps the support fee calculation base — for example, limiting the eligible spend growth to 10% per year regardless of actual spend increases. This prevents your support cost from ballooning when Azure consumption spikes due to cloud migration or new workload adoption.

5. Co-Term with Your EA or MCA Renewal. Negotiating Unified Support alongside your EA or MCA renewal creates combined leverage. Microsoft’s account team is more willing to offer support concessions when simultaneously securing a large licence commitment. Never negotiate support in isolation — bundle it with your largest Microsoft commercial event.

For further reading, explore our Microsoft Knowledge Hub, Microsoft Contract Negotiation Service, Microsoft Advisory Services, Microsoft EA Optimization Service, and our Microsoft white papers. You can also assess your current Microsoft licensing position with our Microsoft assessment tools.