Automation Orchestrator feature enablement with licenses
Automation Orchestrator
feature enablement with licensesAccess to certain
Automation Orchestrator
features is based on the license applied to your Automation Orchestrator
deployment.After authentication, your
Automation Orchestrator
instance is assigned a license based on the license
edition of the authentication provider. Licenses control access to the following
Automation Orchestrator
features:- Git integration
- Role management
- Multi-language support (Python, Node.js, and PowerShell)
You can manually change the license of the
Automation Orchestrator
server from the
Licenses
page of the Control Center.There is no limit to the number of
Automation Orchestrator
deployments
to which you can apply the same license, regardless of the license type. For
VMware Aria Automation
licenses,
having a deployed and configured VMware Aria Automation
environment is not required. Authentication | Current licensing | Legacy licensing | Git Integration | Role management | Multi-language support |
|---|---|---|---|---|---|
vSphere | VMware vSphere Standard VMware vSphere Foundation | vSphere vCloud Suite Standard | No | No | No |
vSphere | Manually added VMware Cloud Foundation license | VMware Aria Automation VMware Aria Suite Advanced or
EnterprisevCloud Suite Advanced or Enterprise | Yes | Yes | Yes |
VMware Aria Automation
| VMware Cloud Foundation | VMware Aria Automation VMware Aria Suite Advanced or
EnterprisevCloud Suite Advanced or Enterprise | Yes | Roles are managed from the VMware Aria Automation instance used to authenticate Automation Orchestrator . | Yes |
Legacy licenses such as vSphere and
VMware Aria Automation
continue to be
valid. However, if your deployment is uses a VMware Cloud Foundation or VMware vSphere
Foundation license, the older licence becomes irrelevant.