Hybrid Operations: Fixing VCF Operations 9 License Entitlement Drift with Orchestrator

In VCF Operations 9, entitlement issues can show up as 'vCenter not fully licensed' even when you think you’re covered. The KB calls out a common cause: vSAN environments require both the VCF core license and the vSAN (TiB) add-on license assigned correctly.

Source KB: https://knowledge.broadcom.com/external/article/422008/vcenter-not-full-licensed-in-vcf-operati.html

The narrow use case

Detect and remediate missing vSAN add-on license assignment on vCenters running vSAN-backed clusters.

Orchestrator action: vCenter + vSAN add-on license audit

Goal: find vCenters attached to vSAN clusters where the expected license mix is incomplete, then notify or open an ops task.

Workflow steps (VMware Aria Orchestrator)

• Create a workflow: 'VCF Ops - vCenter License Entitlement Audit'
• Inputs: vCenter (VC:SdkConnection), notifyEmail (string, optional)
• Step 1: Enumerate clusters and detect which are vSAN-enabled (vSAN service enabled on cluster).
• Step 2: Read license assignments for the vCenter instance (license manager query) and verify both VCF core + vSAN add-on are present when vSAN clusters exist.
• Step 3: If mismatch is found, output a remediation message: 'Assign vSAN (TiB) add-on license to vCenter as add-on entitlement'.
• Step 4: Send a short report to email/Slack/ITSM with the vCenter name + affected cluster list.

Action steps

1. Run this workflow on a schedule (daily) so entitlement drift is caught before it breaks visibility.
2. Wire the output into your change workflow so licensing corrections are tracked like any other production change.
3. Keep the workflow output as JSON so you can trend repeat offenders across vCenters.