The Contractual Landscape Before and After the Acquisition

Before Broadcom's acquisition closed, VMware's contractual framework had remained broadly stable for a decade. Enterprises held perpetual licences, paid annual support and subscription (SnS) fees, and operated under straightforward end-user licence agreements (EULAs) and enterprise purchase agreements (EPAs) that were well-understood by procurement and legal teams. Product entitlements were granular, support tiers were clearly defined, and reseller relationships provided a degree of commercial flexibility.

All of that has been replaced. Understanding what the new contractual terms actually say, and where the commercial risk now sits, is essential for every enterprise that continues to operate VMware infrastructure.

The End of Perpetual Licences: What It Means for Your Legal Position

The most consequential change is the elimination of perpetual licences. All VMware perpetual licences were discontinued in 2024. Organisations that hold existing perpetual licences — purchased before the acquisition or during the transition period — retain the right to use that software indefinitely. However, the critical distinction is that those perpetual licences now exist without a support pathway. Broadcom will not renew SnS contracts for perpetual licenced products. This means your perpetual licences represent a fixed asset whose effective useful life is determined by how long you can operate unpatched software in your environment.

From a practical standpoint, this is a significant legal and operational risk. Security vulnerabilities discovered in VMware software after your SnS expires will not receive patches under your existing entitlement. Your legal and risk management teams should understand that "we own perpetual licences" no longer provides the protection it once did.

Subscription Contract Terms: The Key Clauses

The new VMware subscription agreements introduce several contract terms that are materially different from pre-acquisition VMware agreements and require specific attention during legal review.

Auto-renewal provisions. Broadcom's standard subscription terms include automatic renewal clauses that activate if the customer does not provide written cancellation notice within a specified period before the agreement end date. The cancellation window is typically 30 to 60 days before expiry. Miss the window, and you are automatically committed to another subscription term. This provision is not unusual in SaaS contracting but represents a change from the more customer-controlled renewal process that characterised legacy VMware SnS agreements.

Core-based licensing with minimum requirements. The subscription agreement is structured around per-core licensing with a 72-core minimum per physical host. This minimum is contractually enforced regardless of how many cores are actually active or in use. Organisations that previously licenced on a per-CPU or per-socket basis and have modern multi-core processors are frequently discovering that their actual deployed footprint, mapped to the new core-based metric, requires significantly more licences than their historical entitlement. The contractual minimum is non-negotiable without special enterprise agreement terms.

Bundle mandates and product entitlements. The subscription agreement entitles you to a specific bundle tier, not to individual products. If you have purchased VMware Cloud Foundation (VCF), your contract entitles you to all products within VCF — vSphere, vSAN, NSX, Tanzu, and Aria — whether you use them or not. You cannot purchase only the components you use. This matters contractually because it means you are accepting licence terms for products you have not deployed, and Broadcom retains the right to audit your use of all components within your entitled bundle.

"The contractual minimum of 72 cores per host is enforced regardless of actual usage. Many enterprises only discover this during their first subscription renewal when the numbers are reconciled."

Need a contract review before your VMware renewal?

Our advisors have reviewed 80+ Broadcom subscription agreements. We identify the clauses that matter.
Request a Review →

Support Terms: What You Are and Are Not Entitled To

Support entitlement under the new Broadcom model is fundamentally different from the support structure that most enterprise VMware customers are accustomed to. Understanding what your subscription fee actually buys is critical, because the gap between customer expectation and contractual entitlement is one of the most common sources of dissatisfaction in post-acquisition renewals.

Tiered Support Structure

Broadcom has rationalised VMware support into a tiered structure with Standard and Enterprise support tiers. Enterprise support, which most large organisations previously had access to through their VMware account team, is now a distinct paid tier with its own pricing. Organisations that previously received enterprise-grade support as part of a standard SnS contract may find themselves looking at a meaningful additional cost to maintain equivalent support responsiveness.

Response time SLAs have also been restructured. Business-hours response for non-critical issues, 24/7 coverage for critical incidents, and access to technical account management are now explicitly tiered. Review your subscription agreement carefully against your operational requirements to confirm the support tier you have purchased covers the response times your infrastructure depends upon.

Product Lifecycle and Version Rights

Your subscription agreement entitles you to use the current version of your licenced product and to receive updates during the subscription term. This is standard SaaS practice, but it differs from the perpetual licence model in one important respect: when your subscription expires, you lose the right to use the software. There is no "run-out" period. This creates a hard dependency on subscription continuity that perpetual licences did not have.

Product lifecycle terms are also important. Broadcom has communicated general lifecycle commitments for the current VCF and VVF bundle tiers, but the specific end-of-support dates for individual components within those bundles are Broadcom's discretion. Organisations should request explicit written commitments on lifecycle timelines for their critical components as part of any multi-year agreement negotiation.

Renewal Rights and the 90-Day Window

One of the most commercially significant changes in post-acquisition VMware contracts is the narrowing of the renewal window. Broadcom's standard subscription agreements permit renewal activity only within the 90 days preceding contract expiry. Outside of this window, Broadcom's standard position is that pricing discussions are not available and terms are not negotiable.

This is a structural pressure mechanism. Ninety days is insufficient time for most enterprise organisations to conduct a meaningful evaluation of alternatives, complete internal approval processes, negotiate contract terms, and execute a procurement decision. The window is designed to be narrow. Organisations that wait until the renewal notice arrives before engaging with the process are effectively accepting Broadcom's offered terms.

The late-renewal penalty compounds this dynamic. If your subscription lapses — even briefly — Broadcom applies a 20% penalty on the first year of the new subscription when you renew. The combination of the narrow renewal window and the lapse penalty is designed to ensure that most organisations sign renewal agreements quickly and with limited negotiation. Responding to this requires deliberate early engagement, which we address in our VMware renewal response strategy guide.

Partner and Channel Contract Changes

Organisations that historically managed VMware purchasing through a reseller or partner channel should be aware that the partner landscape has changed materially. Broadcom reduced the number of authorised VMware Cloud Service Providers (VCSPs) from over 4,500 globally to approximately 300 Premiere partners and 12 Pinnacle partners in 2025. Many resellers that previously held VMware partner status have had their agreements terminated.

This reduction in channel breadth has two practical consequences. First, the resellers with whom you have established relationships may no longer hold authorised partner status, which affects their ability to quote, renew, or support your VMware agreement. Second, the reduced partner competition means that reseller pricing competition — which historically provided a degree of commercial flexibility — has largely been eliminated. Direct Broadcom engagement is now the primary channel for substantive commercial discussions.

Audit Rights and Compliance Exposure

Broadcom's standard subscription agreements include audit rights that are broadly consistent with industry practice. Broadcom may, with reasonable notice, audit your deployment to verify compliance with the terms of your subscription. Under the new bundle model, this audit exposure is broader than it was under the legacy VMware entitlement model.

Because you are licenced for an entire bundle tier rather than individual products, an audit will examine your deployment against all components within your bundle. If you have deployed components that were not part of your pre-acquisition entitlement — for example, if your transition to the new bundle tier included Tanzu or NSX to which you were not previously entitled — you may face compliance exposure for the period between bundle transition and audit. Organisations should conduct an internal entitlement review as part of any subscription renewal or transition to ensure their actual deployment maps cleanly to their contractual entitlement.

Planning Your Contract Position: Key Actions

Given the changes described, there are several specific actions that enterprise legal and procurement teams should take to manage VMware contract risk effectively.

Obtain and review your current subscription agreement in full. Many organisations renewed into subscription terms via reseller channels without fully reviewing the Broadcom standard terms that now govern their agreement. Obtain the full agreement document and have your legal team review it with specific attention to auto-renewal provisions, audit rights, bundle entitlements, and support tier definitions.

Map your deployed footprint against your contractual entitlement. Confirm that your actual VMware deployment — including all components within your licenced bundle tier — is accurately reflected in your entitlement documentation. Any discrepancy between what you have deployed and what you are entitled to deploy represents audit risk that should be resolved before your next renewal conversation.

Engage Broadcom or your authorised reseller at least six months before your renewal date. Do not wait for the 90-day window. Use the additional time to explore terms, understand your options, and if appropriate, obtain competitive pricing from Nutanix or Microsoft Azure VMware Solution that can be used to support a commercial negotiation.

Consider whether multi-year terms serve your interests. Broadcom offers better pricing on multi-year agreements of three to five years. Whether this trade-off makes sense depends on your confidence in your VMware dependency over that period. Organisations with active cloud migration programmes or serious evaluation of Nutanix as an alternative should weigh the lock-in implications of multi-year terms carefully before committing.

The Broader Context: Why These Changes Were Made

Understanding the commercial logic behind Broadcom's contract changes helps you anticipate how they will evolve. Broadcom acquired VMware primarily as an enterprise software business — not as a hardware or infrastructure business. Hock Tan, Broadcom's CEO, has a well-documented history of acquiring infrastructure software companies and transforming them into high-margin subscription businesses with a focused customer base of large enterprises.

The transition from perpetual to subscription, the reduction of the product catalogue, the narrowing of the partner channel, and the 3x to 5x support cost increases are all consistent with this playbook. Broadcom is not trying to grow the VMware customer base; it is trying to maximise revenue from the existing installed base of enterprises that have significant VMware infrastructure dependencies. This context matters for contract negotiations because Broadcom's account teams are measured on retention and spend under management, not on new customer acquisition. That creates some, albeit limited, commercial flexibility for customers who demonstrate a credible alternative option. The alternatives that provide the most credible negotiating leverage are Nutanix Cloud Infrastructure and Microsoft Azure VMware Solution — both of which have matured significantly since the acquisition and are worth understanding in detail before any renewal discussion.