For the
Automation Orchestrator integration, you must deploy a cloud extensibility proxy instance, that can be used for extensibility subscriptions and XaaS (Anything as a Service) operations used for cloud templates. This deployment includes a preconfigured
Automation Orchestrator instance that is created after you deploy and power on your cloud extensibility proxy. You cannot integrate external
Automation Orchestrator instances in
VMware Aria Automation.
Important: Integration of new SaaS-enabled vRealize Orchestrator 7.6 instances is not supported. Existing vRealize Orchestrator 7.6 SaaS integrations will continue to operate, but you cannot update the configuration of these integrations. To migrate these vRealize Orchestrator 7.6 SaaS integrations to your new
Automation Orchestrator integration, see
Migrating a vRealize Orchestrator 7.6 SaaS instance to the cloud extensibility proxy.
The
Automation Orchestrator integration in
VMware Aria Automation uses a Cloud Services Platform (CSP) authentication that provides the same features as external
Automation Orchestrator deployments that use a
VMware Aria Automation license.
Note:
Automation Orchestrator integration in
VMware Aria Automation does not support changing the license provider for the integration.
For more information on license-based feature availability in
Automation Orchestrator, see
Automation Orchestrator Feature Enablement with Licenses in
Installing and Configuring Automation Orchestrator.
What to do next
To create and edit Automation Orchestrator content in your new integration, navigate to https://your_extensibility_va_FQDN:443.
You can perform additional configuration procedures to your Automation Orchestrator through the cloud extensibility proxy. For more information, go to Additional configuration options for the cloud extensibility proxy.
VMware Aria Automation now includes a
Automation Orchestrator service which enables organization owners to assign
Automation Orchestrator service roles to users who need access to
Automation Orchestrator.
Note: The previous implementation where users had access to
Automation Orchestrator through
Automation Assembler service roles is no longer valid.
You can assign the new Automation Orchestrator service roles through the Identity and Access Management menu. For more information on editing service roles, go to How do I edit user roles in VMware Aria Automation. For more information on the Automation Orchestrator service roles, go to Organization and service user roles in VMware Aria Automation.