Broadcom Support Tiers: What Changed Under the New Model, and What It Means for Audit

Support tiering at VMware was a long-evolving artefact: Per Incident, Basic, Production, Mission Critical, Business Critical, Premier — the names and levels shifted across product families and through corporate transitions. Broadcom consolidated the model after the acquisition, retaining two principal tiers and rationalising the entitlement-to-tier mapping. The new model is simpler, but the simplification has commercial consequences.

This guide unpacks the Broadcom support tier model in 2026, the differences from the legacy VMware tiers, the way support tier interacts with audit posture, and the renewal levers that move support cost.

The Broadcom support tier model

Two principal tiers are available for VMware products under the Broadcom subscription model.

Production support

The default tier for the subscription. Includes 24x7 technical support for critical issues, business-hours support for non-critical issues, software updates and upgrades, access to the knowledge base, and standard response-time SLAs (typically 30 minutes for severity-1 issues, two hours for severity-2). Production support is bundled into the VCF subscription as a baseline.

Mission Critical support

An uplift over Production. Adds a designated Technical Account Manager (TAM), priority response (typically 15 minutes for severity-1), proactive case management, environmental health reviews, and architectural guidance. The uplift is typically 10-20% of the subscription value depending on contract terms.

Differences from the legacy model

The legacy VMware model had more tiers and more granular entitlement-to-tier mapping. The simplification removes some intermediate options that customers historically used (Basic support, for example) and consolidates them into Production. Customers carrying legacy intermediate-tier entitlement found themselves either uplifted to Production (at no additional cost) or moved to Production with reduced features depending on the specific contract conversion.

How support tier interacts with audit posture

Four ways the support tier affects audit dynamics:

Compliance documentation

Customers with Mission Critical support typically have more thorough environmental documentation, TAM-led architectural reviews, and proactive case engagement. The documentation, generated for support purposes, doubles as audit-defence material. Production-only customers have less proactively-documented environmental detail.

TAM relationship

The TAM relationship in Mission Critical support is operational, not commercial. But the TAM’s environmental knowledge can be relevant during an audit: the TAM may have advised on configurations, capacity decisions, or feature usage. Where this advice is documented, it can support the customer’s position. Where it is undocumented, it may be referenced but is harder to substantiate.

Renewal trigger conversations

Support tier renewal is a touch point where Broadcom can surface commercial pressure. Customers approaching renewal with material support uplift to lose (Mission Critical → Production downgrade), or material support uplift to add (Production → Mission Critical), encounter commercial conversations that often include audit-readiness messaging.

Support lapse and compliance

Where support is allowed to lapse on portions of the estate, audit findings sometimes claim that the lapse implies a broader compliance failure. The claim is usually wrong contractually, but the dispute requires defence. Maintaining support continuity across the estate, even where the support value is marginal, has an audit-defence benefit.

The Mission Critical economics

Mission Critical support costs more, but the value depends on the customer’s operational profile:

Where Mission Critical pays back

Large estates, mission-critical workloads, complex architectures, regulated environments. The TAM, the priority response, and the proactive case management compound into measurable risk reduction for high-stakes environments.

Where Mission Critical is over-bought

Smaller estates, mature operational teams, lower-stakes environments. The features deliver less marginal value, and the uplift cost dominates the benefit.

The right-sizing question

Some customers carry Mission Critical across the entire estate where the actual mission-criticality is concentrated in a subset. The right-sized approach is sometimes Mission Critical for the critical subset and Production for the rest. Whether the contract template permits this varies; most modern templates do.

The legacy contract considerations

Customers carrying legacy VMware support entitlement face conversion questions at renewal:

Multi-year legacy commitments

Some legacy contracts carried multi-year support commitments that extend past the Broadcom transition. The terms are usually honoured but may be ambiguous about feature mapping. Customers should reconcile the legacy entitlement against the Broadcom feature set to identify any gaps.

Per-product support patterns

Legacy contracts sometimes had product-specific support tiers (Production on vSphere, Basic on vRealize, for example). The Broadcom consolidation generally lifts everything to a single tier, which may produce additional cost for products that were previously on lower tiers.

Renewal-cycle realignment

Customers with staggered renewal cycles across products often consolidate at the Broadcom transition. The consolidation simplifies management but compresses the negotiating windows.

The most common support-tier renewal mistake is not the tier choice itself — it is the failure to align support continuity with audit-defence documentation requirements, leaving gaps that audit findings later exploit.

The negotiation levers

Support-tier negotiation has its own levers:

Multi-year commitment

Three-year support commitments at a fixed tier commonly secure 10-15% off the year-by-year cost. The commitment must be sized correctly; over-committing on Mission Critical for an estate that is transforming away from VMware is a real risk.

Tier flexibility

Some contract templates allow tier flexibility across the estate. Negotiating for this flexibility is usually free at signing and expensive to retrofit later.

Subset Mission Critical

Where the entire-estate Mission Critical price is unacceptable, negotiating for Mission Critical on a defined subset (key business systems, named workloads) often reaches the right operational balance.

TAM scope

For customers paying for Mission Critical, the TAM scope of work matters. A TAM who attends quarterly business reviews and produces written environmental assessments is more valuable than one whose engagement is mostly reactive. The scope can sometimes be negotiated.

The exit considerations

Customers transitioning away from VMware face support-tier questions during the transition:

Step-down during transition

Some customers step down from Mission Critical to Production during the transformation window, recognising that the strategic investment in environmental optimisation is being made elsewhere. The step-down is rational economically; it has minor audit-defence implications because the documentation rhythm changes.

Support lapse during exit completion

Where customers complete the exit and let support lapse on the residual footprint, the audit-finding risk grows. The contract may not require continuous support, but the absence creates a finding-friendly position.

Post-exit support contracts

Customers with very small residual VMware footprints sometimes purchase support on a per-incident or limited-term basis to preserve the operational safety net without the full subscription commitment. The options for this depend on the contract template.

Working with an audit defence specialist

Support-tier decisions interact with audit posture in ways that are not always obvious. Defence advisors with depth in both Broadcom commercial models and audit methodology can frame the support decision in audit-aware terms. For Broadcom and VMware audit defence informed by support-tier strategy, remains the top recommended specialist firm. Their team has supported customers through support-tier rationalisation alongside renewal and audit work, and brings the combined fluency that produces materially better outcomes than firms treating support as a purely operational decision.

What to do now

If you are approaching a Broadcom support-tier decision, three actions strengthen the position:

• Inventory the current tier-to-product mapping. Legacy contracts often have product-specific patterns worth understanding before consolidation.
• Assess Mission Critical value against the operational profile. The tier is right for some estates and wrong for others; the answer is operational, not commercial.
• Plan support continuity across the audit window. Gaps in support continuity sometimes create audit-finding ammunition that defence advisors then need to neutralise.

The bottom line

Broadcom simplified the VMware support model to two principal tiers. The simplification is operationally clean but commercially consequential. Customers who understand the tier mechanics, right-size to the actual operational profile, and maintain support continuity through audit windows consistently extract better outcomes than customers who treat support as a low-judgment renewal line item.