orchestrator
latest
false
- 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
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Configuring VPN for cloud robots
- Configuring an ExpressRoute connection
- Live streaming and remote control
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Configuring an ExpressRoute connection

Orchestrator user guide
Last updated Apr 30, 2025
Configuring an ExpressRoute connection
With the ExpressRoute gateway deployed, you can now connect your on-premises networks to it. Creating this connection differs from a standard setup because you are configuring how to use your pre-existing ExpressRoute circuit—the dedicated, private connection you have already established with Microsoft Azure. This process involves integrating your UiPath Gateway, or another Microsoft Azure resource, into that existing ExpressRoute infrastructure.
The gateway card displays the public IP address, which is an essential information for the tunnel connection.
On the Connections list, the Address Space and Public IP Address fields are empty and do not apply to the ExpressRoute connection. Unlike VPNs, ExpressRoute uses Border Gateway Protocol
(BGP) for routing by default.