Broadcom withdrew standalone Support and Subscription renewals, bundled support into the term subscription, and moved all but its largest customers to partner-delivered support. The Admodum read on what changed and what it means at renewal.
Broadcom withdrew the ability to renew VMware Support and Subscription as a standalone line. Support is now delivered only as part of a term subscription, so an organisation that wants continued patches, updates and vendor support must move from perpetual entitlement to a subscription. Admodum is an independent, buyer-side software licensing advisory, and this page sets out the practical consequences of that change for buyers planning a renewal.
Support and Subscription (SnS) was the annual maintenance fee attached to a perpetual VMware licence. A buyer who had purchased the licence once paid SnS each year — commonly around twenty per cent of licence value — to keep access to updates and technical support. The licence itself was owned outright; SnS bought only the ongoing service layer on top of it. That standalone arrangement is what Broadcom has withdrawn. The wider model sits in the pillar at Broadcom VMware licensing: VCF, VVF and per-core subscription, and the licence-side change at the end of VMware perpetual licences.
The change matters because, under the old arrangement, SnS was a lever the buyer could pull independently. An organisation could let support lapse on a stable workload while keeping it current on a critical one, or renew support without re-buying licences it already owned. Removing the standalone SnS line removes that flexibility: support and the right to run are now coupled inside a single subscription, so the buyer can no longer treat maintenance as a separate, smaller decision. Understanding that coupling is the first step to reading what the renewal quote is really asking the organisation to commit to.
Under the Broadcom model, production support is bundled into the per-core subscription fee rather than priced as a separate item. There is no longer a support line to renew because the subscription already contains it.
This bundling is part of why the recurring cost rises so sharply. A perpetual buyer at renewal paid only SnS on an owned licence; a subscription buyer pays for the licence and the support together, in full, every term. The support component is no longer a discrete, negotiable line item that can be trimmed in isolation — it is folded into the subscription quantum that is driven by the billed core count. The per-core arithmetic that sets that quantum is examined at the 16-core-per-CPU subscription minimum, and how it surfaces on the renewal paper at how to read a Broadcom VMware renewal quote.
Alongside the licensing changes, Broadcom restructured how it manages customers. It manages a defined list of large, strategic customers directly, with dedicated account teams, and serves everyone outside that list through its partner network rather than directly.
For a buyer below the direct-managed threshold, this changes who they actually deal with. The renewal quote, the commercial negotiation and the first line of support all run through a Broadcom partner rather than through Broadcom itself. For some organisations that is a downgrade in attention; for others a capable partner provides more responsive service than a distant vendor account team did. The point for procurement is that the support and commercial relationship has moved, and the identity, incentives and escalation path of the partner now matter directly to both price and service.
This makes verifying the support path a defined step in any renewal review: confirm whether the organisation is direct-managed or partner-served, identify the partner, and establish the escalation route to Broadcom for severity-one incidents. Where support quality is business-critical, that route should be tested and documented rather than assumed. The negotiation choreography that surrounds this sits at the VMware renewal negotiation playbook.
The partner relationship also has a commercial dimension that buyers should weigh. A partner earns margin on the transaction, which can mean it has an incentive to favour the larger bundle or the longer term, but it can equally mean a motivated intermediary willing to compete for the renewal where more than one partner is able to quote. Some organisations find they can ask more than one Broadcom partner to bid for the same renewal, introducing competitive tension that a single direct relationship would not. Establishing whether that option exists, and on what terms, is part of mapping the support and commercial path before the renewal is negotiated.
An organisation that declines to subscribe keeps the permanent right to run its existing perpetual licences, but once its current SnS contract lapses it cannot be renewed. The estate continues to operate; it simply stops receiving patches, security updates and vendor support.
There is also a contractual nuance worth recording: letting SnS lapse and later wishing to return to support is not a clean reinstatement. Because standalone support no longer exists, the only route back to a supported state is a subscription, and re-entering may carry back-support or reinstatement charges rather than a simple resumption. An organisation choosing an unsupported bridge should therefore treat it as a one-way decision for the duration, planned against a definite end point — either a migration or a negotiated subscription — rather than as a pause it can casually reverse. For an isolated, stable workload with a planned decommission date, running unsupported for a defined window can be a deliberate and defensible choice. For an internet-facing or compliance-bound estate, the absence of security patches becomes an accumulating exposure that most organisations will not tolerate for long, and may breach regulatory or contractual obligations on patching. The real deadline in a Broadcom renewal is therefore the SnS expiry date, not the loss of the right to run — and reading that timeline correctly is what converts a renewal under pressure into a planned decision. The broader decision framework sits at VMware exit and renegotiation strategy.
The support changes turn three facts into prerequisites for any sound decision: when support lapses, who delivers it, and what it now costs inside the subscription.
Record the SnS expiry date for every perpetual entitlement, because that date governs the timeline. Confirm whether the organisation is direct-managed by Broadcom or served through a partner, and if the latter, identify the partner and document the escalation route. Then model the subscription cost with support bundled in against the cost and risk of running unsupported, so the renewal decision rests on evidence rather than urgency. The wider engagement sits at the Broadcom / VMware practice, the aggregated reading at the Broadcom knowledge hub and the cluster index at the Broadcom and VMware hub; a renewal moment routes to the Renewal Programme and engagement opens at contact.
No. Broadcom no longer sells standalone Support and Subscription renewals for perpetual VMware licences. Support is now delivered only as part of a term subscription, so an organisation that wants continued patches and vendor support must move to a subscription rather than renew SnS on its existing perpetual estate.
The named-account model is Broadcom's decision to manage only a defined list of large strategic customers directly, with dedicated account teams. Customers outside that list are served through Broadcom partners rather than directly, which changes who a smaller buyer negotiates and raises support tickets with.
The perpetual licence keeps conferring the right to run the software, but once the existing Support and Subscription contract lapses it cannot be renewed. The estate continues to operate, but it stops receiving security patches, updates and vendor support, which becomes an accumulating risk for any internet-facing or compliance-bound workload.
Yes. Under the Broadcom subscription model, production support is bundled into the per-core subscription fee rather than purchased as a separate line. This is one reason the recurring figure rises sharply, because the buyer now pays for the licence and support together every term rather than paying only an annual support fee on an owned licence.
It can. Buyers below the direct-managed threshold transact through a partner, so pricing, renewal terms and first-line support come through that partner rather than Broadcom directly. The practical effect depends on the partner, which makes verifying the support path and escalation route a necessary part of any renewal review.
The full post-acquisition model: VCF, VVF and per-core subscription.
The Admodum white paper on the Broadcom VMware transition sets out the SnS withdrawal, bundled support and the named-account model in full. A senior advisor will read your SnS expiry dates, support path and renewal quote against it on a private call.
Renewal approaching? Join the newsletter or route the moment to the Renewal Programme.