VCF Usage Meter Incompatibility with Azure VMware Solution vCenter Server.

Products

• VMware Usage Meter

Issue/Introduction

Integrations between VCF Usage Meter 9.x and Azure VMware Solution (AVS) vCenter may fail when attempting to assign mandatory vCenter privileges to a service account. This issue occurs because AVS restricts the delegation of specific global privileges required for license key reporting and vSAN collection.

• Attempts to add an AVS vCenter to VCF Usage Meter fail with "Incomplete Collection"
• Assigning required roles to a service account fails with the error: Add permission failed. Permission to perform this operation was denied. You do not hold privileges 'datacenter #### : [Cns > Searchable, Global > Licenses]'

Environment

VCF Usage Meter 9.x

VMware vCenter Server 8.0.x (provided by AVS)

Cause

Azure VMware Solution is a provider-managed service that imposes strict restrictions on vCenter privilege delegation. The Global > Licenses and Cns > Searchable privileges required for VCF Usage Meter collection are restricted by the AVS CloudAdmin model.

Additionally, per VMware Cloud Services Provider (VCSP) program policy, Broadcom licenses are only compatible with environments where the partner owns the underlying physical hardware. Because AVS hardware is owned by the service provider (Microsoft) rather than the partner, it is incompatible with VCSP metering.

Resolution

Azure VMware Solution (AVS) is not supported for metering via VCF Usage Meter. Partners must ensure compliance by following these guidelines:

1. Do not attempt to meter AVS vCenter instances using VCSP licenses.
2. Deploy VCF Usage Meter only in environments where the partner owns the underlying physical hardware.
3. For AVS-based workloads, utilize the native metering and licensing provided by the cloud service provider.
4. Contact the assigned Cloud System Provider Solution Architect (CSP SA) for further licensing guidance.