Broadcom's Big VCF Shakeup: A Calm Guide to the Licensing Changes

Broadcom did more than shuffle the VMware deck. It threw the cards in the air and told everyone to catch what they need before the licensing winds change again.

Since Broadcom closed its $61 billion acquisition of VMware back in November 2023, everyone knew changes were coming: fewer products, more bundles, and a tighter grip on licensing. Now that the dust is settling around VMware Cloud Foundation (VCF), IT teams are seeing what those changes really mean, and it's… a lot.

This guide is meant to make sense of the shakeup in the calm, clear version that cuts through the vendor slides and budget panic.

VCF: the TL;DR version

If you're new here, VMware Cloud Foundation is VMware's all-in-one private cloud stack. It pulls together the essential ingredients (vSphere for compute, vSAN for storage, NSX for networking, Tanzu for containers, and Aria for cloud management) into a pre-built platform. Think of it as a boxed set with a lifecycle manager (SDDC Manager) baked in.

Instead of manually syncing version dependencies and praying a patch doesn't wreck everything, you get one platform that installs and upgrades as a unit. It's infrastructure with guardrails.

The licensing change that hit like a freight train

Starting November 1, 2025, Broadcom will no longer bundle VCF licenses with public cloud offerings. That means platforms like Azure VMware Solution (AVS), Google Cloud VMware Engine, and AWS VMware Cloud won't include VCF in their SKU anymore. Instead, customers need to bring their own portable licenses, bought directly from Broadcom.

In fact, Microsoft already pulled the plug on bundled VCF sales through AVS as of October 15, 2025. For any new cloud capacity from now on, you're flying solo on licensing.

Broadcom spins this as flexibility, since you can move your licenses between on-prem and cloud more freely. In the real world, it shifts procurement cycles, messes with budgets mid-fiscal, and drops a whole bunch of work into procurement and platform teams' laps.

What's actually new in VCF 9.0

At VMware Explore 2025, Broadcom rolled out VCF 9.0, and the platform clearly isn't standing still. The highlights:

• Private AI as a service. VCF now includes infrastructure for private AI workloads, aiming to keep sensitive models and data inside the perimeter.
• An AI assistant that gives built-in help navigating VCF itself, a nod to the complexity it's trying to manage.
• Cyber Compliance Advanced Service, with more knobs and dashboards for regulated industries and security-heavy environments.
• Tanzu Data Intelligence, which adds support for lakehouse-style data processing within the same stack.

The overall feel is faster, more automated, and closer to modern enterprise goals, if you're ready to lean into it.

The real impact right now

If your organization runs workloads on AVS or Google Cloud VMware Engine, here's your checklist for Q4 2025:

• Check your reserved instance dates. If you bought before October 16, 2025, you're fine until those expire.
• Plan for license procurement. New nodes won't work without your own Broadcom VCF license.
• Expect cost turbulence. Many customers saw 2 to 4x price jumps moving from à la carte licensing to bundles like VCF or vSphere Foundation. Core-based licensing has shifted, too: it's now 16 cores per CPU license, down from 32, and that's not a typo.

If you're not tracking your core counts and license usage with surgical precision, now's the time to start.

Four ways teams are responding

No one's reacting the same way, but patterns are emerging.

1. Hold steady and optimize. These teams are locking things down: audit hosts, kill unused clusters, track license entitlements. It's not flashy, but it's effective, especially when you don't want to get blindsided by renewal costs in Q1 2026.

2. Go hybrid with intent. Others are carefully embracing the new license portability to run VCF both on-prem and in the cloud. The trick is choosing workloads that actually need VCF semantics and then mapping license flows intentionally, because every move now has a cost implication.

3. Diversify the platform stack. Some orgs are using the moment to evaluate alternatives such as Proxmox, Nutanix, and Hyper-V, or even ditching the hypervisor model altogether for native IaaS. The point is controlling future risk.

4. Plan a cloud migration off VMware. A growing set of teams are treating AVS as a transitional bridge. They rehost now, refactor over time, and retire the VMware layer entirely within 1 to 2 years, a deliberate runway out rather than a jump off a cliff.

What to ask in your next strategy call

• Do we have a full inventory of licensed CPUs, including how they map to the 16-core-per-license rule?
• What cloud instances cross the October 2025 threshold? When do those reservations expire?
• Which workloads actually need to stay on VCF for the next three years?
• Are we using, or planning to use, VCF 9.0 features like private AI or Tanzu Data Intelligence?
• Who owns license tracking, and are we prepared for audits?

You don't need to answer all of these today, but you definitely need someone asking them.

Governance and cost tips that actually work

• Gate every new host request by adding a license check to your provisioning workflow. It slows you down slightly and saves massive rework later.
• Right-size hardware to the license model. High core-count CPUs might cost more in licenses than they save in performance, so consider 16-core sweet spots.
• Use cloud reservations wisely. If you've got AVS reserved through late 2026, that's breathing room to test, migrate, or replatform before committing to a new path.
• Don't bake off hypervisors on benchmarks alone. Look at manageability, tooling, and org-wide impact, because cost savings can disappear if operations get messy.

What to tell developers and data teams

You don't need to drop a licensing deck on their desk, but you do want to give a heads-up:

1. New capacity might take longer to approve, especially if license pools are tight or workloads need to shift platforms.
2. VCF 9.0 brings legit value. If they care about data security, private AI, or automating pipeline management, there's real stuff to explore here, so invite them to pilot features where it makes sense.

So, what now?

Here's your calm-in-the-chaos plan:

• Map your estate by inventorying hosts, licenses, and expiration dates.
• Get your procurement story straight and start licensing convos with Broadcom before you're under deadline pressure.
• Pilot what matters. Try VCF 9.0 features that meet a real need and ignore the rest, for now.
• Start platform evaluations early. If you're considering alternatives, bake off now instead of when your renewal clock runs out.

Above all, don't drift. VCF just changed, and whether you double down, branch out, or break away, make it a choice rather than a surprise.