Horizon Pod and Block Design Methodology : 5.1 Deployment Models : 5.1.1 Management Block : 5.1.1.2 Shared
   
5.1.1.2 Shared
Using this model, a shared management block is managed in its entirety by the service provider, and only the service provider would have access to the management block vCenter Server. Within the management cluster, resource pools separate each tenant’s virtual machine workloads (see the following figure) which includes the tenant Connection Servers and Access Point appliances. In addition Network I/O Control (NetIOC) is recommended to prioritize management network traffic between tenants.
The tenant management block hosts each vCenter Server responsible for their dedicated resource blocks. The dedicated resource blocks host the tenant desktop and application workloads.
Figure 8. Shared Management vSphere Cluster
vSphere_Management_Cluster
 
Consider, however, that using this approach means that unexpected downtime or maintenance of the entire management block would impact all tenant management functions. Availability of both management and resource blocks are critical in this model. If a particular tenant requires a strict Service Level Agreement (SLA) for availability, then a dedicated Management block may be deployed for that tenant.
For both service providers and enterprises alike, vSAN Ready Nodes are ideal and an online configurator (http://vsanreadynode.vmware.com/RN/RN) is available to help select the most suitable vSAN Ready Node hardware for your environment.
Note A good starting point for the number of tenants per management block is 4. This allows for ease of management and lowers the impact of outages and maintenance to the management cluster, whether planned or unplanned.