On-Premises and Cloud Platform Orchestrator come with the same capabilities, with few notable exceptions that make the subject of this page.
Some of the features mentioned here might be added in the future to our cloud or on-premises solution. Make sure to check this page periodically, as it is updated on a regular basis to reflect the differences between On-Premises Orchestrator and Cloud Orchestrator.
Cloud Platform supports inviting users by email address. Invited users can sign in using Microsoft Azure AD, Google, or LinkedIn.
You can’t install other third-party plugins then the ones supported by UiPath by default. Azure Key Vault is supported.
This feature works only with Windows Active Directory enabled.
Auto Login for Microsoft Active Directory Users
The Cloud Platform supports single-sign-on (SSO) using Microsoft Azure AD, Google, and LinkedIn.
Some of the features work differently in Cloud Orchestrator compared to On-Premises Orchestrator. Make sure to check this page periodically, as it is updated on a regular basis to reflect the differences between On-Premises Orchestrator and Cloud Orchestrator.
On-premises Orchestrator uses basic authentication for APIs.
Cloud Platform uses tokens instead of basic authentication. Read more about the mechanism here.
For on-premises Orchestrator, you can publish libraries both at host and tenant level feeds
In Cloud Platform you can publish libraries only at tenant level. To share libraries between tenants, you can use a custom feed.
Updated 8 days ago