Navigating VxRail and VCF 9—What Greenfield, Brownfield, and “Wait” Really Mean
Archive update (November 2026): This article captures the VCF 9.0/VxRail support position in June 2025. It is not a current support matrix. On June 16, 2026, Broadcom documented a supported in-place upgrade path to VCF 9.1 for qualifying VxRail environments, with Dell-specific version and hardware guardrails. Read VCF 9.1 — Path for Dell VxRail Customers before planning an upgrade. Some original inline diagrams are not reproduced in this archival copy.
Since the launch of VCF 9 earlier this week, I’ve had a dozen customers reach out asking the same big question: How can we move forward with adopting VCF 9? The excitement is real—but so are the limitations this early in the game. Whether you’re trying to architect a brand-new stack or bring existing environments under the VCF umbrella, it’s important to separate what can be done from what should be done—and what’s simply not supported (yet).
Every environment is different. But whether you’re starting from a clean slate or trying to bring an existing environment into compliance, one core question often shapes the path forward: Is your hardware supported for vSphere 9—let alone VCF 9? If you’re running VxRail, this becomes even more nuanced, as your lifecycle and compatibility are bound to Dell’s release cycle and support matrix.
VxRail + VCF: What’s Supported, and What Isn’t (Yet)
Let’s start with the core issue: in-place conversion from standalone vSphere to VCF is not supported on VxRail environments.
That’s because VCF on VxRail has always required a Dell-supported Greenfield deployment, due to the tightly integrated lifecycle model VxRail enforces. Dell manages:
- VxRail Manager
- iDRAC/BIOS firmware
- SDDC Manager bundles
All of this must align with Dell’s tested and validated release bundles. So if you’re thinking about importing your current vSphere-based VxRail clusters into a VCF 9 management domain—you’ll need to pause. That capability simply isn’t available at this time.
? Call to Action: Support Starts with the Vendor The desire for Brownfield support on VxRail is common—and VMware is actively tracking this as part of ongoing roadmap discussions. But make no mistake: enabling it requires Dell to certify and support the integration first. If this functionality matters to your organization, reach out to your Dell team and make your voice heard. Field momentum plays a meaningful role in shaping vendor priorities.
The Compatibility Catch: Dell’s Milestone Drives the Timeline
Just because VCF 9 is GA doesn’t mean it’s ready for your VxRail deployment. Dell has to complete its own validation and publish support before you can proceed.
Here’s a look at historical lag times:
Release Cycle for vSphere and VCF, and Supportability for VxRail
? Watch this space:
Good news? Dell’s VxRail VP760 is already listed as certified for vSphere 9 in Broadcom’s HCL. That doesn’t mean full-stack VCF support is live—but it shows progress.
Brownfield and Greenfield Support in VCF 5.2 and 9.0
Brownfield Import is officially supported in both VCF 5.2 and 9.0—for non-VxRail environments. This gives flexibility to bring existing infrastructure under centralized management without starting from scratch:
- ? JSON-based Brownfield onboarding workflows
- ? Management Domain abstraction across vCenters (9/8/7) and ESXi (9/8/7)
- ? vSAN is no longer required (a big design unlock!)
? Introduction to the VMware Cloud Foundation 5.2 (VCF) Import Tool
You’ll notice I’m not linking to a separate “Import Tool” for VCF 9—because that functionality is now embedded directly into the Management Plane via VCF Operations. Brownfield onboarding is handled through Fleet Management using native JSON-based workflows—no external utilities or downloads required.
But again: VxRail is excluded from Brownfield imports.
Diagram: VCF 9 Deployment Flow Including Fleet Management and Import Logic
What You Can Do Now: Phased and Strategic Steps
Here’s how to plan a practical and supported transition to VCF 9:
- Adopt VCF Operations / Fleet Management First – This is foundational. Whether you’re running vSphere 7, 8, or preparing for 9, adopting the VCF 9 Management Plane enables centralized lifecycle, compliance, and governance right away—without requiring an immediate hardware refresh.
- Greenfield a VCF 9 Management Domain once Dell updates its matrix for VxRail support. This ensures full-stack compliance and lifecycle alignment with Dell bundles.
- Use Brownfield Import for any supported, non-VxRail clusters that meet the HCL and design criteria. This brings legacy infrastructure under centralized control.
- Stay Mixed, Stay Confident – VCF 9 supports vCenters and ESXi hosts across versions 9, 8, and 7 under a single operations plane.
- Avoid Premature Replatforming – Align with vendor timelines to avoid rework and unsupported states. Move when it’s supported—not just when it’s available.
Final Thought: Wait Isn’t Always a Bad Word
Waiting for official support can feel like standing still—but in reality, it gives you time to:
- Build validated architecture (See: Design Guides and VMware Validated Solutions)
- Align with supportable design (See: Compatibility Guide and Dell Supported Configs)
- Reduce future lifecycle risks
Sometimes, “wait” is the best strategy for long-term success. So whether you’re Greenfielding, Brownfielding, or somewhere in-between, the smart play is to move with validation.
Stay tuned for ongoing updates—and as always, lean on the HCL. It’s your compass through this journey.
? Have questions about your path to VCF 9? Drop them in the comments or message me—we’re all navigating this together.
? Like, repost, or tag someone planning their next platform move.
This article is part of the Architect’s Edge Insights series — designed to cut through confusion and deliver clarity on VMware Cloud Foundation. Stay tuned for upcoming posts as we continue to simplify VCF adoption, operations, and optimization.
#ArchitectsEdge #VCF9 #VxRail #VCFOperations #Greenfield #Brownfield #HCLmatters #ValidatedDesigns
Originally published on LinkedIn on June 20, 2025. Historical technical assertions are retained as published; embedded original diagrams will be restored if retrievable.
