Of all the decisions in a VCF deployment, the tenancy model is the one I see made worst. Not because it is hard, but because of when it gets made.
The pattern is familiar. Infrastructure goes in, the platform team is busy, and somebody needs organisations and projects created so the pilot can start. So they get created, sensibly enough, based on whatever the org chart looked like that week. Eighteen months later there are forty projects, a quota model nobody can explain, and a request to reorganise it all that quietly never gets scheduled because too much now depends on it.
Tenancy is the one decision in the whole build that gets more expensive every month you leave it. Worth spending a fortnight on properly.
Decision zero, which kind of organisation
I used to open this conversation with hierarchy. That was wrong, and it took watching a customer get a long way down the wrong road to see why. VCF Automation 9.1 is bimodal. There are two kinds of organisation, they are not two flavours of the same thing, and almost everything below depends on which one you are in.
An Organisation for VM Apps carries traditional VM-based workloads on VLAN-backed or NSX-backed networking. It is the road out of Aria Automation, and if you are upgrading a legacy Aria estate, the converted environment becomes the first organisation in the new instance whether you planned it that way or not.
An Organisation for All Apps carries the modern platform services: VM Service, vSphere Kubernetes Service, Database Services Manager, VPC-based networking. It needs a vSphere Supervisor cluster, either enabled on a cluster with spare capacity or on a new one. Broadcom's own guidance for greenfield with no Aria dependency is to start here.
The useful part of 9.1 is that both can share one vCenter Server and one NSX instance. That is Mixed Tenancy Mode, and it is a feature flag rather than an architecture. Before this, each organisation generally wanted its own workload domain with its own vCenter and NSX, which is why so many tenancy designs from the 9.0 era look more expensive than the requirement justified.
On deployment shape, there are three. Both organisations on a shared cluster, which is cheapest and carries real contention risk, and which Broadcom positions for small or pilot environments. Separate clusters under the same vCenter, better performance isolation, more hardware, and the documentation calls this mandatory for large deployments with diverse mission-critical workloads. And multi-fleet, which as above is VM Apps only.
What a tenant actually is
With the organisation type settled, you can ask the question that usually gets asked first. In most enterprises a tenant is one of three things, and plenty of places have all three.
A department or business unit
A project or application team
An external customer
Write down which one you mean before you create anything. If the answer is more than one, you need a hierarchy that accommodates both, and that is much easier to design up front than to retrofit.
Where quota actually lives
Quota is not a property of a tenant, which is the part that catches people out. It sits at two specific places in a four-level containment, and if your design does not say which, it is not finished.
A Region Quota is the allocation an organisation receives from a region. It is defined per vSphere Zone and it covers CPU and memory, as limits or as reservations, plus the VM classes and the storage classes that organisation can see. The sentence worth underlining is that a single Supervisor cluster can be mapped to multiple organisations through a Region Quota. That is the mechanism that makes shared infrastructure multi-tenant rather than merely crowded.
Below that, projects hold members, shared catalogue items, approval and reclamation policies. vSphere Namespaces sit inside projects, bound to the scope of the project they belong to, and they carry the CPU, memory and storage limits along with the network the workloads land on. Isolation between All Apps organisations is described as total, and the thing doing the isolating is that namespace boundary. Tenants do not need their own service accounts into the infrastructure, which is worth saying out loud to a security reviewer who is expecting to see them.
The five decisions
1. Hierarchy depth
2. Quota strategy
3. Isolation boundaries
4. Who is the provider
5. What happens at the end
Where the newer constraints bite
There is a ceiling on namespaces, and it is lower than most people assume
Region is a hard edge for GitOps
The public cloud door has closed in VM Apps organisations
GPU tenancy is its own conversation
Edition boundaries shape what tenants can be offered
Two smaller things that will bite an integration team
Broadcom publishes six patterns worth reading first
There is a named set of multi-tenancy consumption patterns in the design library, and it sits a couple of clicks away from the deployment models page that most people land on, so it is easy to miss. Read it before you draw anything. The shape I describe below sits alongside these rather than replacing any of them, and four of the six cover ground that otherwise gets improvised in a workshop.
- Resource isolation with a single VPC for multiple businesses in one Supervisor zone.
- Resource isolation with multiple VPCs for multiple lines of business in one Supervisor zone.
- Resource isolation with a single VPC for multiple lines of business across three Supervisor zones.
- Resource isolation for multiple organisations with dedicated VRFs or transit gateways.
- Multi-region, multi-tenant resource isolation with dedicated and shared gateways.
- Multi-organisation resource isolation with shared NSX across workload domains.
If you are a business-unit tenancy with everything in one region, you are pattern one or two and the choice is whether each line of business gets its own VPC. If isolation has to be a security boundary, pattern four is where that argument gets settled. If you are multi-region, pattern five is the starting point and the GitOps constraint above is already waiting for you there.
A shape that usually works
Not a recommendation for your estate, just the pattern I find myself drawing most often for a mid-sized enterprise. In the vocabulary above it is an All Apps organisation per business unit, sitting closest to patterns one and two.
Organisation per business unit, with the business unit owning its budget. Project per application team or product, created from a template so they are consistent. Tiered quota expressed as a Region Quota with a guaranteed floor per project and a shared burst pool at organisation level. Network isolation at the organisation boundary, not the project, because project-level isolation multiplies quickly and rarely earns its complexity. And a named provider team with a published service description, so people know what they are getting and what they are not.
The bit people skip is the service description. If a tenant cannot find out what the platform promises without asking someone, they will keep raising tickets, and you will have built self-service that nobody self-serves.
Before you create anything
- Decide VM Apps or All Apps, and if both, create the VM Apps organisation first.
- Write down what a tenant means in your organisation, in one sentence.
- Decide hierarchy depth across all three levels, and what sits at each.
- Pick a quota model, anchor it to the Region Quota, and name who can change one and how quickly.
- Decide whether isolation is a security boundary or an expectation.
- Decide whether your VPCs are overlay or VLAN-backed, knowing the private network trade-off.
- Name the provider team and write a one-page service description.
- Design decommissioning, including accelerator memory if GPUs are in scope, and test it once.
- Check the region constraint and the 30-namespace ceiling against your GitOps plans.
- Check nothing in the catalogue depends on native public cloud management.
- Read the six consumption patterns and say which one you are closest to.
- Model what this looks like at three times the current tenant count.
That last one catches most design problems. A model that works for six tenants and falls apart at twenty is common, and you only find out when you are already at fifteen. The namespace ceiling is the first wall you will hit, and it arrives sooner than the organisation count suggests.
Tools that go with this
Tenancy is a design problem, but it sits on top of two counting problems. Estate Readiness Triage tells you which clusters can carry any of this, and Upgrade Runway tells you whether there is time to get them there before support runs out.
Free to use, including with customers. Nothing you enter leaves your browser. All tools.
Sources
All of the below checked on 5 November 2026 against VCF 9.1.1. These pages move, and at least one of them has moved since this post first went up: the tenancy deployment models page now carries a last-updated date of 26 October 2026.
- Tenancy deployment models with VMware Cloud Foundation: the five supported shapes.
- Understanding the VCF Automation All Apps organisation multi-tenancy model: the containment, the Region Quota definition, and the namespace isolation boundary.
- Bimodal consumption design for VM Apps and All Apps workloads: Mixed Tenancy Mode, the ordering constraints, the deployment shapes, and the index of the six consumption patterns.
- VCF Automation 9.1.1.0 release notes: the 30-namespace Argo CD limit, VLAN-backed VPCs, the public cloud deprecation, the vcfa_api scope, and the region quota deletion issue.
- VCF 9.1 design documentation.
- Centralizing GitOps at enterprise scale with VCF 9.1.1: the one-instance-per-namespace behaviour and region scoping.
- The hierarchy of modern infrastructure: namespaces across VCF, VKS and VCF Automation.
- Optimizing AI Deployments with VCF, Part 1: GPU utilisation figures and the VM co-location constraint.
- VCF 9.1 and VVF 9.1 feature comparison: edition boundaries.