Multitenant Use of vRealize Operations as a Service : Designing for vRealize Operations as a Service : 4.1 vRealize Operations Manager Deployment Models : 4.1.3 Shared and/or Dedicated Environment with No Tenant Access
   
4.1.3 Shared and/or Dedicated Environment with No Tenant Access
In this scenario, the service provider operates a centralized vRealize Operations Manager instance to collect all data generated by the resource cluster. The primary difference from the scenario described in Section 4.1.1, Shared Multitenant Environment with Tenant and Service Provider Access is that access is only provided for the service provider. This scenario allows for easy management and deployment.
This approach is often used in managed services environments where the service provider focuses on resource optimization.
The following advantages apply:
Easy to deploy and manage
No additional data/configuration distribution for dashboards, policies, and so on necessary
Only one instance to maintain (software updates, management packs and so on)
No complex RBAC necessary
Disadvantages include the following:
Sizing can become complex and larger environments might be limited by sizing parameters. A possible workaround is to build instances per larger resource group.
No customer/tenant access to vRealize Operations Manager possible.
Figure 6. Shared Multitenant Environment with Tenant and Service Provider Access