Choosing the Right Microsoft Unified Support Level: Core vs Advanced vs Performance

How Microsoft Unified Support Pricing Works

Microsoft Unified Support is priced as a percentage of your total annual Microsoft spend — a base that includes all M365 licences (across all SKUs from E1 through E7), Azure consumption, Dynamics 365 subscriptions, GitHub enterprise licences, Power Platform, and any other Microsoft commercial products covered under the EA or equivalent agreement. This percentage-of-spend pricing model is fundamental to understanding the cost dynamics of each tier.

As your Microsoft estate grows — through SKU upgrades, headcount additions, Azure consumption growth, or new workload deployments — your Unified Support cost automatically increases in proportion, without any renegotiation. This means organisations that have added M365 Copilot ($30 per user per month as a standalone or included in E7 at $99 per user per month) or increased Azure consumption since their last support renewal have likely experienced significant support cost growth that they did not explicitly approve. In our experience, Unified Support costs frequently grow 10 percent in Year 2 and 20 to 30 percent by Year 3 of an EA cycle, purely through Microsoft estate expansion rather than any change in the support contract itself.

Published rates for the three tiers are approximately 6 to 8 percent for Core, 8 to 10 percent for Advanced, and 10 to 15 percent for Performance. These are opening positions, not fixed rates. Microsoft's published rates have no contractual basis — they are the starting point for negotiation. Organisations that accept published rates without benchmarking consistently overpay by 20 to 40 percent against the rates achievable through structured negotiation.

Tier-by-Tier Analysis

Core Support: What You Actually Get

Core is the entry-level Unified Support tier, providing unlimited reactive break-fix support across all Microsoft commercial products covered under the agreement. Support is available 24 hours per day, 7 days per week for Severity A (critical, production-down) incidents. For Severity B (significant impact but workaround exists) and Severity C (non-urgent, minimal business impact) issues, Core support operates during standard business hours only — a material constraint for organisations with extended or global operational coverage requirements.

Core's Severity A response target is initial contact within one hour. Severity B response target is four business hours. Severity C is acknowledged within eight business hours. These are response targets — not financially backed SLAs. Microsoft does not face contractual penalties for missing response targets at any Unified Support tier. The distinction matters: at Core level, there is no TAM to escalate to, no dedicated support delivery manager, and no proactive programme to ensure Microsoft is engaged appropriately on your account.

Core does not include proactive services, deployment health checks, workshops, or technical account management. The absence of proactive services is the defining characteristic of Core versus Advanced — and it is the primary factor that should drive the tier decision. If your organisation can fully manage its Microsoft technology without external Microsoft guidance, Core provides the reactive safety net at the lowest cost.

Best suited for: Organisations with mature internal Microsoft technical capability, predominantly standardised M365 deployments without complex hybrid or multi-cloud configurations, and low incident volumes (fewer than 15 to 20 support cases annually). Also appropriate as a temporary tier for organisations that have recently right-sized a support renewal and are planning to rebuild internal capability before moving back to Advanced.

Advanced Support: The TAM and Proactive Question

Advanced is the most common tier for mid-market and lower-end enterprise organisations. It adds a Technical Account Manager (TAM), faster critical incident response (30-minute Severity A target, 2-hour Severity B), and a proactive services programme — typically 20 to 40 proactive service days per year including technology briefings, health assessments, deployment reviews, and access to Microsoft engineering advisory for specific product areas.

The TAM is the most frequently cited reason for choosing Advanced over Core, and the most frequently underutilised benefit in practice. A TAM's value is entirely dependent on how actively the organisation engages them. In a significant proportion of Advanced support contracts, organisations use fewer than half of their included proactive service days — meaning they are paying for a TAM-delivered programme that they are not consuming. Before committing to Advanced primarily for TAM access, the organisation must honestly assess whether it has the internal capacity and discipline to maintain a regular engagement cadence with the TAM and consume the included proactive services.

Advanced pricing is typically 8 to 10 percent of Microsoft spend at published rates. For an organisation with $4 million in annual Microsoft spend, that translates to $320,000 to $400,000 annually for support alone. Negotiated Advanced rates for organisations that benchmark and present competitive alternatives typically land at 6.5 to 8.5 percent — a saving of $60,000 to $140,000 annually on a $4 million estate.

Best suited for: Organisations deploying complex or evolving Microsoft workloads (Azure platform services, Microsoft Fabric, Copilot pilot programmes, Dynamics 365), those undertaking significant migrations or transformations, or those that lack deep internal Microsoft technical expertise and rely on Microsoft's proactive advisory to guide deployment decisions. The value case for Advanced depends on actually using the proactive services.

Performance Support: When Premium Is Justified

Performance is the highest Unified Support tier, providing 30-minute Severity A response, 24/7 coverage across all severity levels, a senior TAM with typically 40-plus proactive service days per year, dedicated support engineers for specific Microsoft product areas, and access to Microsoft's Designated Engineering escalation path for complex architectural or platform issues. Performance also typically includes customised support plans aligned to the organisation's specific technology strategy and renewal roadmap.

Published Performance rates are 10 to 15 percent of Microsoft spend. At the enterprise level — $20 million or more in annual Microsoft spend — this produces annual support costs of $2 million to $3 million. These figures are routinely negotiated down to 8 to 12 percent for organisations that present competitive alternatives and engage Microsoft's global accounts team rather than the standard account team.

The question for Performance is not whether the premium services are valuable in isolation — they are. The question is whether the incremental value of Performance over Advanced justifies the incremental cost for your specific organisation. For most organisations, the marginal benefit — 30-minute versus 2-hour Severity A response, additional proactive days, dedicated engineers — does not justify the 3 to 5 percentage point premium over Advanced rates. The exceptions are highly regulated enterprises (financial services, healthcare, critical infrastructure) where production outages carry regulatory or reputational consequences that make 30-minute response a genuine business requirement, and organisations running complex Microsoft platform services (Azure OpenAI with PTU reservations, Microsoft Fabric at scale, large Dynamics 365 implementations) where dedicated engineering access has demonstrable value.

Best suited for: Large enterprises with mission-critical Microsoft dependency, regulated sectors where response time has regulatory implications, complex multi-product Microsoft estates requiring sustained engineering engagement, and organisations managing rapid Microsoft adoption programmes where TAM and dedicated engineering guidance is consumed consistently throughout the year.

The Tier Comparison at a Glance

The SLA Problem: What No Tier Actually Guarantees

One of the most important facts about Microsoft Unified Support — at any tier — is that response time targets are not financially backed service level agreements. Microsoft does not face contractual penalties, credits, or financial consequences for missing Severity A response targets, even at Performance tier. The response times in the table above are best-effort targets, not guaranteed commitments backed by compensation mechanisms.

This is materially different from how cloud infrastructure SLAs work — Azure, for example, offers financially backed uptime SLAs with credit mechanisms for downtime. Unified Support's response targets operate on a fundamentally different basis. For organisations that require genuinely guaranteed response times with financial consequences for failure, third-party support alternatives — which do offer financially backed SLAs — should be evaluated alongside Microsoft's Unified Support tiers.

Third-party Microsoft support providers — including US Cloud and others — offer support for many Microsoft products at 50 to 70 percent of Unified Support rates, with financially backed SLAs. The trade-off is that third-party providers cannot access Microsoft's internal engineering teams or product groups for escalation, which limits their effectiveness on complex platform issues. For organisations that rarely escalate beyond standard break-fix support, the third-party alternative is worth modelling.

Negotiation Strategy for Each Tier

Microsoft's Unified Support rate is negotiated as a component of the broader EA or equivalent agreement renewal. The most important structural principle is to negotiate support bundled with the EA, not as a separate and subsequent discussion. Organisations that negotiate EA pricing and then address support separately lose the bundling leverage that comes from treating the total commercial relationship as one negotiation.

Establishing Your Benchmark

Independent benchmark pricing is the foundation of any Unified Support negotiation. Microsoft's published rates are starting positions. The benchmark you need is the actual negotiated rate achievable for an organisation of your size, complexity, and Microsoft spend level — not the published rate. Organisations that present Microsoft with a third-party support proposal alongside the Unified Support negotiation achieve measurably better outcomes: independent data suggests that 91 percent of enterprises who present a competitive alternative to Microsoft Unified Support receive immediate discounts in response.

Core-Specific Negotiation Points

For Core negotiations, the primary lever is minimum spend floor management. Microsoft's minimum annual fee for Core is approximately $25,000. For smaller organisations, this floor may represent a higher percentage of spend than the nominal 6 to 8 percent rate — meaning the effective rate is higher than published for low-spend organisations. Negotiating the minimum fee down or securing a tiered rate that reflects actual organisational size is the primary Core negotiation objective.

Advanced-Specific Negotiation Points

For Advanced, the key negotiation items beyond rate reduction are proactive service day allocation, TAM engagement model, and the scope of included health assessments. Advanced customers frequently leave significant value on the table by not explicitly negotiating the proactive services scope — accepting whatever is offered rather than specifying the health assessments, workshops, and advisory sessions that align to the organisation's actual Microsoft roadmap. Microsoft's TAM programme is worth considerably more when the proactive services are consumed against a documented engagement plan rather than ad hoc.

Performance-Specific Negotiation Points

Performance negotiations should address dedicated engineer scope — which product areas have assigned engineers, what response protocol applies when dedicated engineers are unavailable, and how escalation to Microsoft's product engineering teams is structured. Performance customers who do not explicitly define dedicated engineer scope often find that the designation is nominal rather than operational. Additionally, Performance customers should negotiate a formal service review mechanism — quarterly business reviews with Microsoft account leadership — as a contractual commitment, not an informal courtesy.

The Bundle Negotiation Advantage

The most powerful Unified Support negotiation lever is treating support as an integrated element of the EA commercial relationship. Organisations that renew EA and Unified Support simultaneously — presenting Microsoft with a single total commercial position — consistently achieve better outcomes than those that handle each component separately. Microsoft's account team is measured on total contract value, not component-level pricing. Creating a single negotiation covering EA discount, Unified Support rate, Azure Reserved Instance pricing, and any add-on subscriptions gives Microsoft's account team maximum flexibility to structure concessions across components — which typically produces a better total outcome than extracting concessions on each item individually.

For independent Unified Support negotiation support, including benchmark pricing and bundle strategy, our Microsoft EA advisory specialists work exclusively on the buyer side. You can also visit the Microsoft knowledge hub for our complete library of Microsoft licensing resources.

The 2026 Context: Why Unified Support Costs More Than You Think

Two structural changes in 2026 make Microsoft Unified Support more expensive in real terms than it has ever been. The first is Microsoft's July 1, 2026 price increases: M365 E3 rises from $36 to $39 per user per month, and E5 from $57 to $60 per user per month. Since Unified Support is calculated as a percentage of your total Microsoft spend, these list price increases automatically drive up your Unified Support bill — even if you negotiate a better percentage rate. An organisation paying 8% of total Microsoft spend on Core support will pay 8% of a larger number from July 2026. There is no notification. There is no renegotiation trigger. The cost just goes up.

The second structural change is the elimination of EA Level B–D volume discounts from November 1, 2025. Previously, a 15,000-user enterprise received an automatic 12% discount on online services (Level D), reducing the Microsoft spend baseline against which Unified Support was calculated. That 12% discount floor is gone. All customers, regardless of size, now start at Level A list pricing. The practical effect is that your Microsoft spend baseline — the denominator in the Unified Support percentage calculation — is higher by 6–12% for mid to large enterprises. Unified Support costs follow that increase automatically.

The M365 SKU stack now runs from F1 through F3, E3, E5, to the new E7 top tier launching May 1, 2026 at $99 per user per month. Organisations that upgrade any portion of their estate to E7 will see their Microsoft spend baseline increase significantly. A move of 2,000 users from E5 ($60) to E7 ($99) adds $936,000 annually to the Microsoft spend baseline — and therefore adds $56,160–$140,400 to an annual Unified Support cost at 6–15% of spend. That incremental Unified Support cost is rarely factored into E7 business cases. It should be.

The implication is clear: before negotiating Unified Support tier or rate in isolation, model the total Microsoft spend trajectory over the next three years. Both the July 2026 price increases and any planned SKU upgrades will drive your Unified Support cost upward independently of any rate negotiation. Capping the support fee at an absolute dollar maximum — irrespective of spend growth — is the most important Unified Support negotiation lever available to enterprise customers in 2026.