ProviderConsumptionOrg remains visible in NSX after disabling from vCF-A

Products

• VCF Operations/Automation (formerly VMware Aria Suite)
• VCF Automation

Issue/Introduction

After disabling the Provider Consumption Org feature in vCF-A, the ProviderConsumptionOrg entity continues to appear within NSX. Network mappings such as Transit Gateway, VPC, and Load Balancer (LB) configurations are still present.

Environment

VCF Automation 9.0

Cause

The Provider Consumption Org is not created by default. It is instantiated when a service administrator enables the feature flag “Provider Consumption Org.” Once enabled, this organization cannot be deleted—only disabled. Consequently, all associated NSX references and network mappings remain intact.

Resolution

This is expected behavior. Since the Provider Consumption Org cannot be deleted, its references and network mappings in NSX persist even after the feature is disabled. No further action is required.

Disabling the feature stops its functionality but does not remove existing NSX objects.
The mappings (Transit Gateway, VPC, LB, etc.) are permanent once created.

Additional Information

https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/provider-management/managing-organizations/create-a-provider-consumption-organization.html