How to Renew VMware License

VMware’s licensing structure changed in late 2024, and these changes shape how teams handle renewal conversations today. The shift away from perpetual keys and SnS agreements means organizations migrate directly into subscription bundles instead of extending older terms. This matters because the subscription format ties licensing to newer capacity rules, and every renewal request eventually leads back to those subscription paths.

VCF and VVF form the center of the updated model. Both are subscription-based, which is why renewal discussions often feel more like license transitions. Another way to view this is that a renewal now validates whether the environment fits into one of these bundles. The announcement that Workstation and Fusion became free in 2024 might confuse some readers, but this change only applies to desktop products and doesn’t affect server or datacenter licensing.

The new model also introduces two important capacity floors: a 16-core minimum per CPU and a 72-core minimum per product instance, the latter of which took effect early in 2025. Those numbers influence how customers calculate usage before they renew VMware license subscriptions and make it easier to avoid gaps during audits. When customers talk about “renewals,” they’re often being quoted these updated subscription bundles rather than the older SnS renewals that no longer apply.

Because the legacy Customer Connect portal was retired, every part of the renewal workflow now runs through the Broadcom Support Portal. This consolidation simplifies some tasks, but it also means organizations must know exactly where to look before making choices about subscriptions or license usage.

Accessing the Broadcom Support Portal

The migration happened on May 6, 2024, so teams searching for old login paths won’t find them. Inside the Support Portal, license management sits under My Entitlements, where each entitlement contains its own license badge. That’s where upgrading, downgrading, merging, and splitting keys happen.
Some teams use this page to clean up older structures; others treat it as a checkpoint before requesting quotes. Anyone handling renewals should get comfortable navigating this part of the portal because it’s required to renew VMware license access in the new framework.

Steps to Complete Renewal or Subscription Transition

1. Log in to the Broadcom Support Portal.
2. Open My Entitlements and look for expiration dates and contract details.
3. Confirm whether the environment aligns with VCF or VVF and check all core entitlements.
4. Accept the subscription terms shown for the product edition you’re renewing.
5. Download and apply new keys in vCenter → Administration → Licensing.
6. Validate that the applied license matches the entitlement and appears correctly in the product.

That short sequence replaces the old SnS workflow. It gives organizations a consistent way to roll forward their usage without relying on multiple systems or outdated contract rules.

The updated model introduces timing issues that weren’t as strict before. SnS renewals cannot be reinstated once they expire, so organizations that wait too long must migrate to subscriptions. A pattern appearing in 2025 reports shows late renewals leading to extra costs and service interruptions, which explains why some customers feel rushed during renewal cycles.

Confusion also comes from capacity rules. The 16-core and 72-core minimums affect compliance directly, and teams that overlook them risk falling out of alignment. Another way to think about this is that every renewal includes a built-in compliance check: If the organization exceeds core entitlements or miscalculates vSAN capacity, the subscription may not map cleanly.

Broadcom guidance phrases it simply: “Expired SnS agreements can’t be renewed; subscription migration is the only valid path forward.” IT teams sometimes underestimate the importance of documentation, but ISO/IEC 19770-1 and 19770-3 help establish evidence for entitlements and usage. Those standards offer structure during audits, especially when environments shift from perpetual licenses to subscription-based rules.

Every environment approaches renewal a little differently, but several steps show up in nearly every scenario. These tasks help teams prepare before initiating a subscription conversation or updating any keys.

Start with a detailed inventory. Count cores per socket, host, and cluster, then compare them against the 16-core and 72-core requirements. This avoids surprises during subscription quotes. Storage checks also matter. If a team uses vSAN as part of a VCF stack, they must confirm any TiB-based add-ons or cluster exceptions noted in Broadcom documentation.

Once the environment is mapped, review entitlements inside the Support Portal. Export all license information so you have evidence before making changes. Another way to frame this step is to treat it like a snapshot; once renewal begins, those details help confirm whether the subscription aligns with the environment.

Teams with structured IT asset management practices usually align the process with ISO/IEC 19770-1 to keep approvals consistent. They also compare the costs of VCF versus VVF to see which subscription better matches real usage. That modeling becomes critical because the choice determines how you renew VMware license access year over year.

Some mistakes appear repeatedly in renewal scenarios, and avoiding them makes the process smoother. Buying from unauthorized resellers may seem cheaper at first, but it cancels support rights and complicates license tracking. Underestimating core counts is another common issue. If the environment runs heavier workloads than expected, it can drift out of compliance and trigger contract adjustments.

Another mistake involves ignoring renewal notifications. Because expired SnS terms don’t roll over, missing these alerts forces organizations into subscription re-quotes. That usually increases the total cost. Some teams also forget about vSAN TiB requirements, which affects VCF subscriptions directly. It’s easy to overlook this when focusing only on compute cores.

Another issue comes from assuming perpetual keys still renew. Once the perpetual model ended in 2024, those keys stopped receiving contract extensions. Without updated entitlements, renewals stall. Documentation matters here. Tracking changes with ISO/IEC 19770-1 practices keeps evidence clear and reduces stress during audits or migrations.

OTAVA is still a Broadcom Pinnacle Partner and we help organizations navigate these shifts by reviewing entitlements, mapping core usage, and walking through subscription options that fit current environments. Our team understands the subscription bundles tied to Broadcom’s new model, and we support customers who want a clearer path during renewal cycles. We also evaluate vSAN requirements and examine how the 16-core and 72-core rules affect capacity planning.

If you’re preparing to renew VMware license subscriptions under this updated framework, we can guide you through the details and help prevent missed steps or unnecessary costs. Reach out to us to schedule a VMware licensing assessment and move into your next term with confidence.