We are currently revamping our website to improve user experience. During this time, some pages or links may not function as expected. We regret any inconvenience and appreciate your patience and continued support.

VMware Licensing Changes: What They Mean for Your Workloads

VMware licensing changes, for the IT head, infrastructure manager or finance lead in India or the GCC who runs VMware on their own hosts and has a renewal ahead. Five changes matter: subscription terms, cores counted per CPU with a 16-core minimum, bundles with vSAN storage per core, a new support portal for keys, and bring-your-own subscriptions for VMware hosted on a hyperscaler.

The VMware licensing changes replace one-time purchases with term subscriptions and change how a renewal is sized. Five changes matter for an estate: the move to subscription terms, cores counted per CPU with a 16-core minimum, bundles that include vSAN storage per core, a support portal that holds only keys under active support, and a bring-your-own subscription for VMware hosted on a hyperscaler. A subscription license lets you use the software for a set term, after which you renew it or stop.


Last reviewed 2026-11-14 by Manish Sharma.

This explainer is written for IT heads, infrastructure managers and finance leads in India and the GCC. Their firms host VMware on their own servers, with a renewal date coming up. The facts below are as of November 2026. They come from VMware’s own notices and knowledge base and from Microsoft and AWS documentation. Each section explains one change and what to check on your own hosts, bundle and dates. However, this article does not plan a move, score your readiness or compare other options. Those are separate decisions.

VMware Licensing Changes at a Glance

The VMware licensing changes touch five things a renewal depends on: how you buy, what you count, what the bundle holds, where your keys live and where VMware runs. The table sets out each change, what it means for your estate and what to check first.

Change What it means for your estate What to check first
Subscription terms You renew the software for a set term instead of owning it, and each renewal becomes a budget event. First, check the end date and term length on your current contract.
Cores counted per CPU, with a 16-core minimum You license every physical core on the hosts you choose. A CPU with fewer than 16 cores still counts as 16. Count the CPUs and cores on each host you intend to license.
Bundles with vSAN storage per core Products now come in bundles, and each core you license brings some vSAN storage entitlement. Compare the bundle’s parts with what your team runs today.
Support portal move Only keys under an active support contract moved to the new portal. Confirm who holds the portal login and which keys appear there.
Hosted VMware on a hyperscaler From 1 November 2025, you bring your own portable subscription to VMware hosted on a hyperscaler. Check how your hosted nodes are licensed today and when that arrangement ends.

The sections below take each change in turn, starting with the move to subscription terms.

From Perpetual Licenses to Subscription Terms

A perpetual license is a one-time purchase that lets you run a software version for as long as you like. You buy support and updates separately each year. By contrast, a subscription license lets you use the software only for the term in the contract. VMware’s notice on ending perpetual licensing, from January 2024, describes its transition from perpetual licensing to a subscription model. In that notice, VMware describes VMware Cloud Foundation and VMware vSphere Foundation as subscription software only.

For a finance lead, this changes the shape of the budget. With perpetual licenses, the large spend came once, and later years carried only the support renewal. With a subscription, the renewal date becomes the budget event instead. The whole license is renewed on that date. The amount depends on the core count and the bundle at that time.

For an IT head, the change also moves the planning horizon. A host that ran for years on a perpetual license now needs a live subscription for each term. Any change in host count, CPU model or bundle shows up at the next renewal. In practice, that makes the renewal date the point where the estate’s shape and its license meet.

Key Takeaway A renewal date belongs in the budget plan in the same way as a lease end or a hardware refresh.

The next section starts with the count itself, which sets the size of each renewal.

VMware Licensing Changes and Your Core Count

The size of a renewal starts with a count of physical cores on the hosts you license. The two sections below explain the rule VMware uses and then how to run that count on your own hosts.

How VMware Counts Cores Per CPU

A physical core is a processing unit built into the CPU chip itself. A virtual machine sees a virtual CPU instead. VMware knowledge base article 313548 sets the rule. VCF and VVF core licensing covers the total number of physical CPU cores across all ESXi hosts you intend to license. VCF is VMware Cloud Foundation and VVF is VMware vSphere Foundation, the two bundles this article refers to.

The same article also sets a floor. You must license at least 16 physical cores for each CPU in your ESXi hosts. A CPU with 8 cores therefore counts as 16, while a CPU with 24 cores counts as 24.

The knowledge base gives a worked example. Host A has 2 CPUs with 8 cores each, and Host B has 2 CPUs with 24 cores each. First, each of Host A’s CPUs is raised to 16 cores, which gives 32 cores. Then Host B adds its 48 cores. Together, the two hosts come to 80 cores to license, although they hold 64 physical cores between them.

Under vmware per core licensing, the count follows the hardware CPU by CPU, however many virtual machines run on it. For example, a lightly used host with two low-core CPUs can outcount a busier host with denser CPUs.

Third-party timelines also describe a minimum at the contract level, on top of the per-CPU rule. They disagree on whether it still applies. However, article 313548 states no contract-level minimum. We recommend asking your reseller to confirm in writing whether one applies to your renewal.

Running the Count on Your Own Hosts

A hypervisor is the software layer that runs virtual machines on a physical server. In a VMware estate, that layer is ESXi. The count covers the ESXi hosts you plan to license, so first decide which hosts those are.

Steps for running the core count behind the VMware licensing changes: list hosts, note CPUs, note cores, raise to 16, add up, in white, light gray and orange
Follow the numbers to reach one core count to take to the reseller.

Start with a list of the hosts you intend to license at the next renewal. For each host, note how many CPUs it has, then how many physical cores each CPU holds. Next, raise any CPU below 16 cores to 16. Finally, add up the cores across the hosts. That total is the core count your renewal starts from. For hosts under vCenter, VMware’s knowledge base offers a PowerCLI tool that collects core and TiB counts per host.

Two things can push the count above what the hardware suggests. First, older or smaller CPUs with fewer than 16 cores each count as 16. A cluster of low-core hosts then carries more licensed cores than it holds. Second, a host that stays on the list but runs few workloads still counts in full. For example, a standby host kept for spare room adds its cores like any other. A test host left switched on does too.

Under the VMware licensing changes, each of these hosts is renewed every term. A host list that grew over the years deserves a fresh look before the renewal. A move off VMware starts from a checklist of readiness marks for a VMware estate.

We recommend keeping the count in a sheet with each host’s serial number, CPU model and core count. That record gives the IT and finance leads one set of numbers for the renewal talk with the reseller. It also shows which hosts could leave the count if their workloads moved to other hosts.

Bundle Fit: Paying for Parts You Do Not Use

VMware now sells its products in bundles, with VCF as the larger bundle and VVF as the smaller one. Each bundle includes vSAN, VMware’s storage software. It pools the disks inside each host into storage that a group of hosts can share.

VMware article 313548 counts vSAN on the total raw physical storage, in TiB, that all ESXi hosts contribute to vSAN clusters. Each VCF core includes 1 TiB of vSAN entitlement. Each VVF core includes 0.25 TiB, rounded up to the next TiB.

That entitlement fits some estates better than others. Hyperconverged infrastructure (HCI) is a design where compute and storage sit in the same hosts. vSAN is how VMware builds it. An estate that keeps its data on an external storage array may not use the vSAN entitlement at all. The bundle includes it anyway. On the other hand, a storage-heavy HCI estate may need more TiB than its cores bring. That extra capacity sits on top of the bundle.

The same question applies to the rest of the bundle. Under the VMware licensing changes, parts once bought one by one now arrive together, used or not. For example, a firm that ran only the hypervisor and its management tools may now hold a bundle with unused parts.

Before the renewal, take three questions to your reseller. Which parts of the bundle does your team run today, and which would it start using within the term? How much raw storage do your hosts contribute to vSAN, compared with the entitlement your cores bring? Also, if you keep an external array, does the smaller bundle cover the hosts you need?

VMware Licensing Changes and Renewal Timing

A subscription renews on a fixed date for a fixed term. That date and term set the window for any change to hosts, bundle or count. The two sections below line them up with your hardware and budget.

Renewal Date Against Hardware Dates

Put the dates side by side before the renewal talk. The ones that matter are the subscription renewal date and the term length on offer. Add the support end dates for your hosts and storage, plus any data center contract end date. A single line with these dates on it shows where they cluster and where they pull apart.

Checklist of dates to line up before a VMware renewal: renewal date, term length, hardware support ends, data center contract end, financial year end
Dates that fall close together are the first ones to compare.

For example, take a host whose hardware support ends a year after the renewal. A long term on its cores means licensing hardware you may replace partway through. If the replacement hosts carry CPUs with more cores, the count changes as well. For the hardware side, see a dated plan for replacing servers.

The budget year matters too. Under the Companies Act 2013, firms in India generally close their financial year on 31 March. The budget then runs April to March. A renewal date in February then lands at the end of one budget, with the next still in planning. GCC readers can check their own company’s financial year in the same way.

The renewal is also a moment for IT and finance to review the estate together. We recommend checking which workloads each host runs, and whether backup and recovery for those workloads have been tested recently. In practice, a host that nobody can link to a workload is a candidate to leave the count.

What Raises the Renewal Total

When people search for a vmware price increase, the reasons behind a higher renewal total trace to the rules above. This article gives no figures, because each quote depends on the estate’s own count and bundle. Four drivers can raise the total.

First, CPUs with fewer than 16 cores count as 16. A low-core estate then licenses more cores than it holds. Second, a bundle can include parts your team does not use, and those parts are still part of the renewal. Third, term length and renewal timing change the total, for example when a long term covers hosts due for replacement. Fourth, the late-renewal terms in your contract matter. Check what applies to a renewal after the end date, and ask your reseller before the date slips.

Ask for the lines behind a quote

We recommend asking for the core and TiB lines behind any quote. With those lines, your team can check the core count against its own host sheet. It can check the vSAN figure against the storage the hosts contribute. A gap between the two is a question for the reseller before anyone signs.

Support Portal and License Key Changes

VMware moved its customer portals in 2024. VMware knowledge base article 282163 states that from Sunday, 5 May 2024, all customer portals redirect to the new support portal. The same article states that only license keys with an active support contract were brought over. Keys associated with expired support contracts are not accessible there.

For an estate with mixed contracts, this matters at renewal and at any rebuild. For example, a key on an expired contract may be missing from the portal when a host needs reinstalling. Under the VMware licensing changes, the portal record also becomes the reference for what your firm holds.

Before the renewal talk, start with access. Check who in your firm holds the portal login, and whether that person is still in the role. Then confirm the site ID your contracts sit under. After that, export the key list and match each key to its contract dates and to the hosts it covers.

A key with no live contract, or a host with no matching key, is a question for the reseller before the renewal.

Key Takeaway Keep the key list beside the host sheet: one record of hosts, cores, keys and dates for IT and finance.

VMware Licensing Changes When VMware Runs on AWS or Azure

VMware also changed how it is licensed on a hyperscaler. A hyperscaler is one of the large public clouds that host VMware for customers. Microsoft’s Tech Community post for Azure VMware Solution customers was updated on 28 August 2026. It states that the new model for hyperscalers began on 1 November 2025. Under it, the customer brings a portable VCF subscription that it holds itself.

For Azure VMware Solution, the same post sets out three dates. Microsoft stopped selling Azure VMware Solution with VCF subscriptions included after 15 October 2025. Pay-as-you-go nodes with the license included could keep running unchanged through 31 October 2026, which has now passed. Reserved instances bought on or before 15 October 2025 can continue until 30 August 2027.

Microsoft Learn’s page on VCF license portability for Azure VMware Solution adds a rule for the count. On each private cloud, the registered cores you bring must exactly match the cores you deploy. In other words, the hosted estate has its own core count. Every deployed core needs a portable subscription behind it.

On AWS, the Amazon Elastic VMware Service setup guide states that you bring your own VCF licenses to run VCF there, however you deploy it.

A firm that runs a hybrid cloud, with VMware both on site and in a hyperscaler, may hold two counts. One covers its own hosts, and one covers the hosted nodes. For firms in India and the GCC, region choice matters as well. Data residency rules can decide which cloud region a hosted VMware estate may use.

Three Paths After the VMware Licensing Changes

After the VMware licensing changes, an estate has three broad paths. Each one changes the licensing picture in its own way.

Three paths after the VMware licensing changes: stay and right-size, run VMware on a hyperscaler, replatform, in white, light gray and orange
Two of the three paths keep VMware running; replatforming moves workloads off it.

Staying and right-sizing means keeping VMware on your own hosts and reducing what the count covers. That can mean fewer hosts, fewer low-core CPUs raised to 16, or workloads moved off standby hosts. A private cloud on your own hardware stays in place, with a smaller count at each renewal.

Running VMware on a hyperscaler means moving the workloads to a hosted VMware service. The hardware leaves your data center, while the portable subscription is still counted per deployed core.

Replatforming means moving workloads to a different platform, and VMware licensing ends as each one moves. However, the move itself has its own cost, effort and risk, which belong in the decision.

Choosing between these paths is a separate decision, set out in the ways to stay, run in the cloud or replatform. The order in which workloads move is set out in an order of work for moving virtual machines to AWS or Azure. Where the question covers the building as well as the hosts, read about when the whole facility needs a rethink.

To be clear about our interest: Signisys provides cloud migration and cloud services, including work on VMware estates. A Signisys consultant goes through your core count, bundle fit and renewal date with you. No charge, with a fixed scope.

Book a consultation
Talk through your VMware renewal with Signisys

What This Explainer Leaves Out and When to Get Help

This explainer covers VMware’s server and cloud products, and VMware’s desktop products sit outside it.

Not contract or legal advice

This explainer gives no contract or legal advice; your reseller and legal team have the final word on your terms.

Get help when a renewal is a few months away or your count and the reseller’s do not match. The use case page on moving VMware workloads to AWS or Azure sets out the move itself. Our solution for planned moves and rebuilds on AWS and Azure covers delivery. If the count is in dispute, our cloud team can run it with you against your host list.

VMware Licensing Changes FAQ: Common Questions

Why are companies leaving VMware?

Some firms weigh a move when the renewal terms, bundle or low-core host count no longer fit their estate. Others stay and right-size, because a move to another platform carries its own cost, effort and risk. This article gives no figures on how many firms do either.

How does VMware licensing work now?

VMware has moved from perpetual licenses to subscriptions for a set term. You license every physical core across the ESXi hosts you choose, with at least 16 cores per CPU. The VCF and VVF bundles also include vSAN storage per core. At the end of the term, you renew or stop.

Do the VMware licensing changes hit hosts with few cores per CPU harder?

Yes, in the count. A CPU with fewer than 16 cores still counts as 16. For example, a host with two 8-core CPUs counts as 32 cores while holding 16. An estate of such hosts licenses more cores than it holds.

What happens to license keys tied to an expired support contract?

VMware knowledge base article 282163 states that only keys with an active support contract moved to the new portal. Keys tied to expired contracts are not accessible there. Check your key list against your contract dates before the renewal.

Do VMware licensing changes apply when VMware runs on a hyperscaler?

Yes. From 1 November 2025, VMware hosted on a hyperscaler needs a portable VCF subscription that the customer brings. On Azure VMware Solution, the registered cores on each private cloud must exactly match the deployed cores. The hosted estate then has its own core count. On AWS, the customer brings its own VCF licenses as well.

Newsletter

Security Insights, Delivered.

Practical, vendor-neutral analysis of threats, tools, and architecture decisions.

Book a Consultation

A practice principal will contact you within 1 business day.

Thank you! A Signisys principal will be in touch within 1 business day.