orchestrator
2020.10
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Audit
- Managing Credential Stores
- CyberArk® Integration
- CyberArk® CCP Integration
- Azure Key Vault Integration
- Actions
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Action Catalogs
- Profile
- System Administrator
- Identity Server
- Authentication
- Other Configurations
- Integrations
- Classic Robots
- Troubleshooting
Azure Key Vault Integration
OUT OF SUPPORT
Orchestrator User Guide
Last updated Dec 12, 2023
Azure Key Vault Integration
To be used as an Orchestrator credential store, Azure Key Vault must be enabled in
UiPath.Orchestrator.dll.config
and then configured by the Host
administrator.
In the App Registrations pane of the Azure Portal, follow these steps:
- Create a new app registration.
- Copy the Application (Client) ID for later use.
- Go to Manage > Certificates & Secrets > New client secret, and add a new client secret. Make a note of the expiration you chose and create a new secret before that.
- Copy the Value of the secret for later use.
In the Azure Key Vault, follow these steps:
- Access the Key Vault's Overview page, and copy the Vault URI and Directory ID for later use.
- Select Settings > Access Policies from the menu on the left.
- Click Add access policy.
- From the Configure from template (optional) drop-down menu, select Secret Management.
- Click None selected in the Authorized application section to enable the Select principal field.
- Enter the app registration name, confirm that the Application ID is correct, and select this principal.
- Click Add.
- Click Save.
You are now ready to use Vault URI,Directory ID,Application (Client) ID and the secret's Value to configure a new credential store.