- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- About licensing
- Unified Pricing: Licensing plan framework
- Activating your Enterprise license
- Migrate from Test Suite to Test Cloud
- License migration
- Assigning licenses to tenants
- Assigning user licenses
- Deallocating user licenses
- Monitoring license allocation
- License overallocation
- Licensing notifications
- User license management
- Tenants and services
- Accounts and roles
- AI Trust Layer
- External applications
- Notifications
- Logging
- Data Export
- Testing in your organization
- Troubleshooting
- Migrating to Test Cloud
Test Cloud admin guide
This section outlines the UiPath-specific configuration. For Azure portal steps, use Microsoft documentation.
1. Create the private endpoint
Create a Private Endpoint in the VNet where your client workloads run.
Use the following configurations for the endpoint:
- Connection method: Connect to an Azure resource by resource ID or alias
- Resource ID: Use the value from the Available regions section.
- Target sub-resource: Use the Subresource value from the regional table
For detailed Azure instructions, refer to Create a private endpoint by using the Azure Portal.
After the endpoint is created:
- Record the private IP address assigned to the endpoint.
- You will use this IP address when configuring DNS.
After the private endpoint allocates a private IP, make sure your firewall rules allow traffic from your VNet to that IP address.
2. Configure the Private DNS zone
Your VNet must contain a Private DNS zone for cloud.uipath.com. This ensures traffic resolves to the private endpoint instead of the public endpoint.
-
Create the Private DNS zone, using the steps detailed in the Microsoft documentation.
-
Link the
cloud.uipath.comPrivate DNS zone to the VNet where the private endpoint exists. For step-by-step guidance in Azure, refer to the Microsoft documentation. -
Add the following A record to your
cloud.uipath.comPrivate DNS zone:Record name Type TTL Value Notes @A 100 <Private endpoint IP address>Use the private IP assigned to your endpoint -
After configuring DNS, validate that:
cloud.uipath.comresolves to the private endpoint IP from your client subnets.- Clients can authenticate and access Automation Cloud through the private endpoint. If DNS is misconfigured, traffic may fail to connect or may route traffic to the public endpoint.
- The
@record must point to your private endpoint IP. - You are responsible for maintaining this DNS record in your environment.
3. Request private endpoint approval
After completing the private endpoint and DNS configuration:
- Contact UiPath Support.
- Request approval of your private endpoint connection.
The endpoint remains in a Pending state until UiPath approves it from the Application Gateway side.
Once approved, the connection status changes to Approved, and traffic flows through the private connection.