- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Orchestrator testing
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting

Orchestrator user guide
Configuring SSO: Microsoft Entra ID
This page describes how to enable the Microsoft Entra ID integration at the host level so that all users of Orchestrator can benefit from SSO.
Host-level versus organization-level integration
If you enable the Microsoft Entra ID integration at the host level, as described on this page, you cannot enable it at the organization/tenant level.
The integration at the host level only enables SSO. But if enabled at the organization/tenant level, the integration allows for SSO, but also for directory search and automatic user provisioning.
To set up the Microsoft Entra ID integration, you need:
- admin permissions in both Orchestrator and Microsoft Entra ID (if you don't have admin permissions in Azure, collaborate with a Microsoft Entra ID administrator to complete the setup process);
- an organization administrator UiPath account that uses the same email address as a Microsoft Entra ID user; the Microsoft Entra ID user does not require admin permissions in Azure;
- UiPath Studio and Assistant version 2020.10.3 or later;
- UiPath Studio and Assistant to use the recommended deployment .
- if you previously used local user accounts, make sure that all your Microsoft Entra ID users have the email address in the Mail field; having the email address in the User Principle Name (UPN) field alone is not enough. The Microsoft Entra ID integration links directory user accounts with the local user accounts if the email addresses match. This allows users to retain permissions when they transition from signing in with their local user account to the Microsoft Entra ID directory user account.
- Log in to the Azure portal as an administrator.
- Go to App Registrations, and select New Registration.
- In the Register an application page, fill in the Name field with a name for your Orchestrator instance.
- In the Supported account types section, select Accounts in this organizational directory only.
- Set the Redirect URI by selecting Web from the drop-down list and filling in the URL of your Orchestrator instance, plus the suffix
/identity/azure-signin-oidc
. For example,https://baseURL/identity/azure-signin-oidc
. - At the bottom, select the ID tokens checkbox.
- Select Register to create the app registration for Orchestrator.
- Save the Application (Client) ID to use it later.
Now that Orchestrator is integrated with Microsoft Entra ID Sign-In, user accounts that have a valid Microsoft Entra ID email address can use the Microsoft Entra ID SSO option on the Login page to sign in to Orchestrator.
Each administrator must do this for their organization/tenant if they want to allow login with Microsoft Entra ID SSO.
- Log in to Orchestrator as an administrator.
- Add local user accounts for your users, each with a valid Microsoft Entra ID email address.