Orchestrator differences

UiPath Orchestrator has roughly the same capabilities across deployment options, but for a few notable exceptions, which are described on this page.
The information on this page refers to the following deployment options for Orchestrator:

  • Standalone Orchestrator (on-premises, latest version)
  • Orchestrator service in UiPath Automation CloudTM (cloud)

Check this page periodically, as it is updated on a regular basis to reflect the differences between the deployment options.


Differences in feature behavior

Standalone Behavior

Cloud Behavior

API Authentication

Standalone Orchestrator can use:
basic authentication
the OAuth flow (2021.4 and later)

Automation Cloud, and therefore Orchestrator as well, can use two mechanisms:
tokens instead of basic authentication. More...
the OAuth flow

Libraries Feeds

For standalone Orchestrator, you can publish libraries both at host and tenant level feeds

In Automation Cloud you can publish libraries only at tenant level. To share libraries between tenants, you can use a custom feed.

Password Complexity Settings

As the host administrator of an on-premises Orchestrator, you can manage the password complexity for your organization.

By default, when users sign up for Automation Cloud and create their account, the password they set must meet specific requirements, which cannot be modified.
You can choose to change your Authentication Settings to use the Azure Active Directory integration, which allows you to configure password requirements.

Aktualisiert vor 29 Tagen

Orchestrator differences

Auf API-Referenzseiten sind Änderungsvorschläge beschränkt

Sie können nur Änderungen an dem Textkörperinhalt von Markdown, aber nicht an der API-Spezifikation vorschlagen.