Study guide

6.5 License Management in VMware Cloud Foundation

VMware Certified Professional - VMware Cloud Foundation Administrator VCP-VCF 2V0-17.25

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Private Cloud Vision & Architecture

1.1 Private Cloud Principles & The Modern Cloud Operating Model 1.2 VMware Cloud Foundation Architecture & Full-Stack Value Proposition 1.3 Private Cloud Use Cases, Service Models & Workload Strategy

2 Chapter 2: VMware Compute Fundamentals

2.1 ESXi Host & vCenter Architecture and Deployment 2.2 vSphere Cluster Design, High Availability (HA), and DRS 2.3 Virtual Machine Deployment, Advanced Hardware, & Management 2.4 Managing Virtual Machines Through vCenter: Day-2 Operations

3 Chapter 3: VMware Storage Fundamentals

3.1 vSphere Core Storage Architecture: VMFS, NFS, & vVols 3.2 vSAN Architecture: Express Storage Architecture (ESA) vs. Original Storage Architecture (OSA) 3.3 vSAN Cluster Deployment, Storage Pools, & Disk Configurations 3.4 Storage Policy-Based Management (SPBM), Fault Tolerance, & Space Efficiency 3.5 vSAN Resilience & Data Availability: FTT, Fault Domains, and Stretched Clusters 3.6 vSAN Space Efficiency: Compression, Deduplication, TRIM/UNMAP & Reclamation

4 Chapter 4: VMware Network Fundamentals

4.1 VCF Network Architecture & NSX Core Components 4.2 NSX Virtual Network Fabrics, Transport Nodes, & Geneve Overlays 4.3 Edge Clusters, Tier-0/Tier-1 Gateway Routing, & Uplink Connectivity 4.4 NSX Distributed Firewall (DFW) & Distributed Network Services 4.5 VCF 9.0 Virtual Private Clouds (VPCs) & Transit Gateway Connectivity

5 Chapter 5: VCF Deploy and Configure

5.1 VCF Deployment Models: Standard vs. Consolidated & Prerequisites 5.2 VCF Installer Bring-Up & Management Domain Deployment 5.3 VI Workload Domain Deployment, Commissioning Hosts, & Storage Attachment 5.4 vSphere Supervisor Configuration & vSphere Kubernetes Service (VKS) Integration 5.5 VCF Deployment Components & Additional Required Infrastructure 5.6 Deploying & Configuring the VCF Network Gateway 5.7 VCF Networking Deployment: NSX Instances, Transport Fabric & Edge Clusters 5.8 Workload Domain Storage: Principal vs. Supplemental Storage

6 Chapter 6: VCF Manage & Lifecycle Operations

6.1 VCF Fleet Management & Existing vCenter Import Workflows 6.2 Identity Federation, VCF Identity Broker, & RBAC 6.3 Certificate & Password Lifecycle Management in VCF Operations 6.4 Lifecycle Management (LCM), Upgrade Bundles, & Drift Remediation 6.5 License Management in VMware Cloud Foundation

7 Chapter 7: VCF Operations: Architecture, Metrics & Health Diagnostics

7.1 VCF Operations Architecture, Cluster Nodes, & Deployment Options 7.2 Metrics, Properties, Symptom Definitions, & Alerting Mechanics 7.3 Health Diagnostics, Troubleshooting Workflows, & Operational Policies

8 Chapter 8: VCF Operations: Monitoring, Logs & Compliance

8.1 Dashboards, Views, & Management Reporting in VCF Operations 8.2 Storage, Network, and Workload Application Monitoring 8.3 Log Analytics & Troubleshooting with VCF Operations for Logs 8.4 Security Compliance Benchmarks, Hardening, & Configuration Drift 8.5 VCF Operations for Networks: Flow Analytics, Path Troubleshooting & Micro-Segmentation Planning

9 Chapter 9: VCF Consume & Automate: Architecture, Tenancy & Networking

9.1 VCF Automation Architecture, Services, & Automation Use Cases 9.2 Regions, Cloud Zones, Projects, & Multi-Org Tenancy 9.3 Provider Networking, Org Networks, & Content Library Integration

10 Chapter 10: VCF Consume & Automate: Templates, Extensibility & Governance

10.1 Cloud Templates (Blueprints), Schema, & Infrastructure as Code 10.2 Extensibility: Action-Based Extensibility (ABX) & Orchestrator Workflows 10.3 Governance Policies: Approvals, Leases, Resource Quotas, & Day-2 Actions 10.4 Supervisor-Based Services, vSphere Kubernetes Service (VKS), & Modern App Consumption

6.5 License Management in VMware Cloud Foundation

Key Takeaways Explain This Topic AI

From version 9.0 you license VCF and vSphere Foundation using a VCF Operations instance together with the VMware Cloud Foundation Business Services console at vcf.broadcom.com.

Traditional 25-character license keys are eliminated for version 9 products; entitlement is a term-based subscription with a capacity allocation instead.

At least one license server must be added to each VCF Operations instance used for license management; it is a protected repository that holds the licensing data.

Licenses are assigned to vCenter instances, and the components connected to that vCenter — ESX hosts, NSX, HCX, and automation tooling — are licensed automatically as a result.

Primary licenses cover VCF and vSphere Foundation and are measured in CPU cores, while add-on licenses cover vSAN capacity in TiB and VMware Private AI Foundation with NVIDIA in cores.

Last updated: September 2026

6.5 License Management in VMware Cloud Foundation

Exam Focus: "Given a scenario, configure license management within VMware Cloud Foundation" is an explicit blueprint objective, and it is one of the areas most transformed by the move to VCF 9.0. Candidates who learned VCF on 5.x will recall pasting 25-character keys into SDDC Manager. That model no longer exists for version 9 products.

What Changed, and Why It Matters

The shift from the 8.x model is fundamental rather than cosmetic:

Earlier VCF / vSphere VCF 9.0 and later

Entitlement artifact 25-character license keys per component Term-based subscription with a capacity allocation; keys are eliminated

Where managed SDDC Manager and vCenter, per component VCF Operations plus the VCF Business Services console (vcf.broadcom.com)

  • Assignment target Each component licensed individually The vCenter instance ; connected components inherit
  • Local store Held in the component's own inventory A dedicated license server appliance
  • The Two Halves of the System
  • The Business Services Console

vcf.broadcom.com is the central licensing hub. It is where an organisation manages subscriptions, views available capacity, and handles license distribution. It is Broadcom-hosted and sits outside the customer environment.

The VCF Operations Instance

Inside the environment, a VCF Operations instance acts as the local licensing manager . It must be registered with the Business Services console , and registration happens in one of two modes:

Connected mode (recommended) — VCF Operations synchronises licensing data with the console automatically.

Disconnected mode — for environments with no path to Broadcom, licensing is maintained through manual license file uploads .

The License Server

Between those two halves sits the license server : a protected repository within the environment that holds the licensing data .

The operational rules worth memorising:

At least one license server must be added to each VCF Operations instance used for license management. A VCF Operations instance without one cannot license anything.

Once the license server is added, licenses must then be added to it before any vCenter or other asset can be licensed. Adding the server is a prerequisite, not the completion of the task.

A license server is deployed during new VCF and vSphere Foundation deployments , and during upgrades to version 9.1 and later . From 9.1 the license server is one of the default VCF management services the installer deploys.

Primary and Add-On Licenses

Two categories exist, and the unit of measure differs:

  • Category Covers Measured in
  • Primary VMware Cloud Foundation, VMware vSphere Foundation CPU cores
  • Add-on vSAN capacity TiB
  • Add-on VMware Private AI Foundation with NVIDIA Cores

An add-on supplements a primary license rather than standing alone, so vSAN capacity entitlement sits on top of a core-based VCF or vSphere Foundation entitlement.

The Default License

The system automatically creates a default license — a capacity pool assembled from all active subscriptions of the same product within your Site ID . This is what allows capacity to be consumed without hand-allocating an entitlement to every instance, and it is why the Site ID matters: subscriptions pool within a site boundary.

Version 8.x Coexistence

A subscription delivers both a version 9+ default license and license keys for version 8.x of the product . Estates mid-migration therefore hold both artifacts simultaneously, which is deliberate rather than a defect.

The Assignment Model

This is the single most examinable behavioural change:

You assign licenses to vCenter instances. The components connected to that vCenter — ESX hosts, NSX, HCX, and automation tooling — are then licensed automatically.

The practical consequences:

Adding hosts to a licensed vCenter does not require a separate licensing step, though it does consume core capacity from the pool.

Licensing scope collapses from managing many individual component licenses to managing product capacity allocations .

Capacity, not key placement, becomes the thing to monitor. Running out means insufficient subscribed cores rather than an unlicensed component.

Configuring License Management: The Order of Operations

Deploy or identify the VCF Operations instance that will act as licensing manager.

Register it with the Business Services console in connected or disconnected mode.

Add at least one license server to that VCF Operations instance.

Add licenses to the license server.

Assign licenses to vCenter instances, which licenses their connected components.

Monitor consumed against subscribed capacity .

Exam Watch: Key Scenarios and Candidate Traps

Warning

Do not select "enter the license key in SDDC Manager". Version 9 products have no 25-character keys, and the SDDC Manager UI is deprecated. Licensing runs through VCF Operations and the Business Services console.

Important

Adding the license server is step three, not the last step. A scenario in which an administrator has added a license server but still cannot license a vCenter is almost always missing the step of adding licenses to that server.

Tip

Disconnected sites are supported. If a scenario stipulates no internet connectivity, the answer is disconnected-mode registration with manual license file uploads, not an unlicensed or evaluation-mode deployment.

Loading diagram... VCF 9.0 Licensing: Console, VCF Operations, License Server, and Assignment