vRealize Automation provides several extensibility options designed to support a variety of use cases and integrations.

The following diagram illustrates vRealize Automation internal components, and the integration of those components with other external components and the supporting infrastructure of the Consolidated SDDC.

Figure 1. vRealize Automation Logical Architecture, Extensibility, and External Integrations

Fabric Endpoints

vRealize Automation can leverage existing and future infrastructure that represent multi-vendor, multi-cloud virtual, physical, and public cloud infrastructures. Each kind of infrastructure supported will be represented by a fabric endpoint. 

Call vRealize Automation Services from Existing Applications

vRealize Automation provides a RESTful API that can be used to call vRealize Automation application and infrastructure services from IT service management (ITSM) applications such as ServiceNow, PMG Digital Business Platform, and BMC Remedy.

vRealize Business for Cloud

vRealize Business for Cloud is tightly integrated with vRealize Automation to manage the vRealize Automation resource costs by displaying costing information during workload request and on an ongoing basis with cost reporting by user, business group, or tenant. vRealize Business for Cloud supports pricing based on blueprints, endpoints, reservations and reservation policies for Compute Grouping Strategy. In addition, vRealize Business for Cloud supports the storage path and storage reservation policies for Storage Grouping Strategy.

vRealize Operations Management

The vRealize Automation management pack for vRealize Operation Manager provides the comprehensive visibility into both performance and capacity metrics of a vRealize Automation tenant’s business groups and underlying cloud infrastructure. By combining these new metrics with the custom dashboard capabilities of vRealize Operations, you gain a great level of flexibility and insight when monitoring these complex environments.

Supporting Infrastructure

vRealize Automation integrates with the following supporting infrastructure:

  • Microsoft SQL Server to store data relating to the vRealize Automation IaaS elements.

  • NTP server with which to synchronize the time between the vRealize Automation components.

  • Active Directory supports vRealize Automation tenant user authentication and authorization.

  • SMTP sends and receives notification emails for various actions that can be executed within the vRealize Automation console.


NSX and vRealize Automation integration provides several options for designing and authoring blueprints with the networking and security features provided by NSX, and takes full advantage of all the NSX network constructs such as switches, routers, and firewalls. This integration allows you to use an on-demand load balancer, on-demand NAT network, on-demand routed network and on-demand security groups within a blueprint, which is automatically provisioned by vRealize Automation when the blueprint is requested. The integration with NSX eliminates the need for networking to be provisioned as a separate activity outside vRealize Automation.

Cloud Management Platform Usage Model

The Cloud Management Platform (CMP), of which vRealize Automation is a central component, enables a usage model that includes interaction between users, the CMP itself, the supporting infrastructure, and the provisioning infrastructure. The following diagram illustrates the usage model of the CMP in relation to these elements.

Figure 2. vRealize Automation Usage Model

The following table lists the vRealize Automation elements, and the components that in turn comprise each of these elements.




Cloud administrators

Tenant, group, fabric, infrastructure, service, and other administrators as defined by business policies and organizational structure.

Cloud (or tenant) users

Users within an organization that can provision virtual machines and directly perform operations on them at the level of the operating system.

Tools and supporting infrastructure

VM templates and blueprints are the building blocks that provide the foundation of the cloud. VM templates are used to author the blueprints that tenants (end users) use to provision their cloud workloads.

Provisioning infrastructure

On-premise and off-premise resources which together form a hybrid cloud.

Internal Virtual Resources

Supported hypervisors and associated management tools.

External Cloud Resources

Supported cloud providers and associated APIs.

Cloud management portal

A portal that provides self-service capabilities for users to administer, provision, and manage workloads.

vRealize Automation portal (Administrative access)

You use the default root tenant portal URL to set-up and administer tenants and global configuration options.

vRealize Automation portal (Tenant access)

Refers to a subtenant which is accessed using an appended tenant identifier.


A tenant portal might refer to the default tenant portal in some configurations. In this case the URLs match, and the user interface is contextually controlled by the role-based access control permissions assigned to the tenant.