During a design workshop, the customer provided the following requirement:• Business units should not be...

Per the VMware Cloud Foundation 9.0.1 and 9.0.4 Architecture and Automation Design Guides, VCF Automation enables multi-tenancy by assigning dedicated orchestration instances per organization for secure separation of workflows.

The documentation specifies:

“The embedded VCF Operations orchestrator is installed by default as part of the Provider Consumption Organization. Each tenant organization that requires workflow autonomy must deploy its own external VCF Operations orchestrator instance.”

Thus, in a multi-tenant model:

The Provider Tenant uses the embedded VCF Operations Orchestrator instance to manage global workflows.

Each Tenant Organization must use its own external orchestrator instance for isolation, control, and workflow management.

This design ensures logical separation, prevents cross-tenant interference, and aligns with VCF’s security and autonomy best practices for service provider and enterprise models.

References (VMware Cloud Foundation documents):

VMware Cloud Foundation 9.0.1 Design Guide — “VCF Automation Orchestrator Deployment Options (Embedded vs. External).”

VMware Cloud Foundation 9.0.4 Design Guide — “VCF Operations Orchestrator Integration for Multi-Tenant Organizations.”