By Technical Architecture Team | 4 min read
If you attended VMware Explore 2026 in Las Vegas or followed the updates remotely, one clear reality emerged from every keynote and breakout session: VMware Cloud Foundation (VCF) 9.1 is the designated destination for private cloud infrastructure.
Yet, as we spoke with platform leaders, enterprise architects, and IT directors across the floor, a familiar concern kept resurfacing. Holding many organisations back isn’t scepticism about VCF’s capabilities, but the assumption that adopting VCF 9.1 requires changing hardware, networking fabrics, storage arrays, and operating models all in one high-risk, big-bang event.
It doesn’t.
The biggest takeaway from Explore 2026 wasn’t just the feature releases; it was that Broadcom has engineered VCF 9.1 for phased, non-disruptive adoption. You don’t have to rip and replace your existing infrastructure to start getting real value from the platform today.
Moving past the hype to operational reality
While the mainstage keynotes highlighted Private AI and agentic platforms, the conversations that mattered most on the show floor were grounded in pure operational economics.
VCF 9.1 delivers long-awaited operational maturity:
- Live patching: Broadcom demonstrated patching running ESXi hosts without host evacuation in up to 80% of maintenance scenarios.
- Memory and storage economics: Features like NVMe memory tiering and enhanced vSAN global deduplication offer up to 40% lower server TCO and immediate capacity headroom without an emergency hardware refresh.
- Parallel cluster upgrades: Upgrade windows for multi-cluster estates can now compress significantly through higher parallel ceiling limits.
These aren’t abstract future concepts—they are immediate efficiency gains. But accessing them doesn’t mean converting your entire data center overnight.
What “not ready for VCF” actually means post-Explore
When teams tell us they aren’t “ready” for VCF 9.1, what they usually mean is that they assume adoption requires turning every VCF component on together on day one, while immediately decommissioning everything outside the VCF stack.
In reality, a phased VCF adoption roadmap allows you to onboard your estate in manageable stages, bringing workloads and infrastructure across as your refresh cycles and team readiness permit.
This isn’t a workaround—it is a core focus of the VCF 9.1 release architecture:
- Importing existing vSphere environments: You no longer need a greenfield rebuild to adopt VCF lifecycle management. Broadcom highlighted streamlined import paths that allow VCF 9.1 to wrap management around existing vSphere 8.0 U3+ environments directly.
- Pragmatic upgrade paths: Broadcom’s documented convergence paths enable you to transition existing vSphere clusters into VCF without rebuilding them from scratch.
What phased adoption looks like in practice
Take networking and storage—the two areas that typically cause the most hesitation for enterprise infrastructure teams:
- Networking on your terms: While VCF 9.1 expands Virtual Private Cloud (VPC) overlays and microsegmentation, you don’t have to overhaul your physical network on day one. You can run existing physical networking (Cisco or otherwise) alongside VCF, utilizing new Virtual Network Appliances (VNA) for stateful services, and gradually transition subnets onto NSX segments and vDefend when it suits your operational window.
- Coexisting storage models: You don’t need to migrate all workloads to vSAN immediately. VCF allows you to retain existing SAN/NAS storage arrays in workload domains alongside vSAN clusters, shifting workloads over gradually as legacy storage contracts expire.
- Targeted security rollouts: Advanced capabilities like vDefend microsegmentation or distributed IDS/IPS can be enabled on a single high-value workload domain first, proven in production, and then rolled out systematically across the wider fleet.
You aren’t choosing between “all-on” or “all-off.” You are choosing where to prove value first and building outward from there.
Where most organisations should start
With vSphere 8 reaching end of general support in late 2027, timing is important—but it is not a reason to rush into an unmanaged full-stack migration.
If there is one starting point regardless of your ultimate target state, it is VCF Operations 9.1.
Deploying VCF Operations first costs nothing in optionality. By pointing it at your existing vCenter clusters, within weeks you gain complete visibility across your estate, including identifying over-provisioned virtual machines and reclaimed capacity. Frequently, this uncovers enough immediate compute and storage headroom to fund the next stage of your roadmap using infrastructure you already own, rather than requiring new capital expenditure.
Own your VCF adoption post-Explore
If your journey to VMware Cloud Foundation has been stalled by fears of a disruptive overhaul, Explore 2026 proved that the platform is ready to be adopted as a sequence of manageable, value-driven milestones shaped by your business requirements.
The difference between a generic vendor roadmap and a successful enterprise transformation is context: starting with your existing contracts, hardware lifecycles, and operational constraints, then mapping out the sequence from there.
Own your VCF adoption on your terms—maximizing the return on your current investment while building a modern, automated private cloud at a pace that works for your organisation.
Interested in assessing your readiness for VCF 9.1? Contact our technical architecture team to discuss a tailored VCF Onboarding Assessment.