If you’re planning a VMware Cloud Foundation implementation, one change in VCF 9.1 deserves a place at the top of your design: VCF Operations is now the single console for the whole fleet. Lifecycle management, licensing, monitoring and day-2 operations all come together in one place. That changes how you deploy, who needs access to what, and which appliances you run. Here’s what you need to know.
What Changes in VCF 9.1
- The SDDC Manager UI is deprecated. Lifecycle work such as upgrades and patching moves into VCF Operations.
- Cloud Builder is replaced by the VCF Installer, with a guided UI and JSON configuration templates for day-0 deployment.
- Aria Suite Lifecycle, VMware Identity Manager and Aria Operations for Logs have no 9.1 upgrade path. Their roles move to the new VCF management services.
- Licensing runs through VCF Operations, with a separate VCF License Server appliance deployed during the VCF Operations upgrade.
- VCF Identity Broker handles single sign-on. In embedded mode it’s upgraded together with vCenter.
Why It Matters
Until now, running VCF meant jumping between SDDC Manager, vCenter, Aria Operations, Aria Suite Lifecycle and more, each with its own login, inventory and upgrade process. Consolidating into VCF Operations gives you:
- One inventory of every VCF instance, domain, cluster and appliance across your fleet.
- One lifecycle workflow to plan and run upgrades in the right order.
- One place for licensing, capacity and health.
- Fewer appliances to patch, back up and secure.
Monitoring and Capacity, Built In
Because VCF Operations already has the performance and capacity data, new features plug straight into it. A good example is NVMe Memory Tiering: VCF Operations includes a Memory Tiering dashboard and a “What-If” analysis that models the savings before you enable tiering. The same data drives capacity planning and rightsizing across the fleet.
Sizing the Management Services
The VCF management services run on their own footprint in the management domain, so size them early. In VCF 9.1.1, Broadcom reduced that footprint for day-0 deployments and added a Small HA option in the VCF Installer. That gives smaller environments high availability without jumping to a larger size. Existing Small non-HA deployments can be scaled to Small HA as a day-2 operation.
What to Plan for in a New Implementation
- Design VCF Operations as a core service, not an add-on. It’s now the control point for lifecycle and licensing, so treat it like vCenter: highly available, backed up and monitored.
- Choose the management services size and HA level up front, based on the number of instances and domains you’ll run.
- Plan identity early. Decide how VCF Identity Broker connects to your directory and how SSO will work across the fleet.
- Define roles and access. With one console for everything, role-based access control matters more. Separate who can view, who can operate and who can upgrade.
- Update your runbooks. Procedures that start in the SDDC Manager UI or Cloud Builder need to move to VCF Operations and the VCF Installer.
- Train the team. Day-2 tasks look different, so give operators time in a lab or the Hands-on Labs before go-live.
For Existing Environments
If you’re upgrading rather than building new, the move to 9.1 retires several appliances and migrates their roles. During the upgrade, the old VCF Operations fleet management appliance is decommissioned, and its credentials, inventory, certificates and service accounts are migrated. Take verified backups of all management components first, and check Broadcom’s upgrade sequence guidance for your exact starting version.
Wrapping Up
VCF Operations becoming the single console is less flashy than a new storage or networking feature, but it changes day-to-day operations the most. If you’re designing a VCF environment now, build around it from day one: size it properly, make it highly available, and plan identity and access before go-live.

