- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- About licensing
- Unified Pricing: Licensing plan framework
- Flex: Licensing plan framework
- Activating your Enterprise license
- Upgrading and downgrading licenses
- Requesting a service trial
- 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
- Testing in your organization
- AI Trust Layer
- External applications
- Notifications
- Logging
- Troubleshooting
- Migrating to Automation Cloud
Automation Cloud admin guide
This page lists the domains (FQDNs) and outbound IP ranges (CIDRs) that must be allowed for Automation CloudTM and associated UiPath services to function correctly in environments where network access is restricted to approved destinations. Depending on how your organization manages outbound and inbound traffic, these allow lists may be applied in your firewall or in another network security layer that governs external connectivity.
- DNS domain allowlist (FQDNs):
Apply when users, robots, or on-premises components connect to UiPath.
Examples include signing into Automation Cloud Portal, Orchestrator, or Test Manager, or accessing any UiPath interface. In these scenarios, your environment is the requester and the connectivity is controlled by DNS names. These domains must always be allow listed by FQDN (referred to in this page as domains), because their underlying infrastructure is distributed.
- Outbound IP ranges (CIDRs):
Apply when UiPath connects to your systems.
Examples include Automation Cloud Portal accessing your Azure Key Vault for Customer-Managed Keys, IXP syncing with Microsoft Exchange, Test Manager connecting to SAP, or Integration Service and Apps calling your endpoints. In these scenarios, UiPath is the requester, and your firewall sees traffic originating from UiPath outbound IP ranges. To allow traffic originating from UiPath, you must allow the corresponding CIDR blocks (referred to in this page as Outbound IP ranges).
To ensure uninterrupted access to UiPath services:
- Identify the UiPath services used in your tenant.
- For each service:
- Configure the domain allow list with all the mentioned domains.
- Configure the outbound IP ranges
where UiPath connects to your systems.
Note: When specified, use the outbound ranges that correspond to your tenant’s region.
If your tenant migrates to another region, update outbound IP ranges accordingly.
The following sections provide the required domains and outbound IP ranges that should be allowed for UiPath services.
The current outbound IP ranges used by several UiPath services will be removed on January 26, 2026. Starting from October 15, 2025 you have 103 days to allow the upcoming IPs to your firewall. January 26, 2026 is the date when our list of upcoming outbound IP ranges becomes enabled and active.
The affected services include:
- Automation Cloud Portal
- Apps
- Automation Ops
- AI Trust Layer, specifically the Bring your own LLM capability
- Integration Service
- Test Manager
What you need to do
Allow these domains used by Automation Cloud Portal:
|
Scenario |
Domains |
|---|---|
|
Sign in with basic authentication |
https://account.uipath.com
|
|
Sign in with Microsoft |
https://aadcdn.msftauth.nethttps://account.uipath.com
https://login.live.comhttps://login.microsoftonline.comhttps://platform-cdn.uipath.com |
|
Sign in with Google |
https://account.uipath.com
https://accounts.google.comhttps://google.comhttps://lh3.googleusercontent.comhttps://platform-cdn.uipath.comhttps://www.gstatic.com |
|
Sign in with LinkedIn |
https://account.uipath.com
https://cloud.uipath.com
https://lnkd.demdex.nethttps://platform-cdn.uipath.comhttps://platform.linkedin.comhttps://static-exp1.licdn.comhttps://www.linkedin.com |
|
Sign in with Azure Active Directory (Azure AD) |
https://aadcdn.msftauth.net
https://cloud.uipath.com
https://login.microsoftonline.com |
|
Sign in with UiPath Assistant (basic email) |
*-signalr.service.signalr.netFor events related to signing in with basic authentication: https://account.uipath.com
https://platform-cdn.uipath.com |
|
Sign in with UiPath Studio (basic email) |
https://api.nuget.org*-signalr.service.signalr.nethttps://gallery.uipath.comhttps://pkgs.dev.azure.comFor events related to signing in with basic authentication: https://account.uipath.com
https://platform-cdn.uipath.com |
|
Sign in for the first time / Reset password |
uipath.eu.auth0.comaccount.uipath.com |
|
Static assets: Fonts, Styling and CDN hosted scripts |
Fonts: https://use.typekit.nethttps://fonts.gstatic.comhttps://platform-cdn.uipath.comImages: https://s.gravatar.comhttps://secure.gravatar.comhttps://*.wp.comhttps://*.googleusercontent.comhttps://i.ytimg.comhttps://platform-cdn.uipath.comCSS: https://fonts.googleapis.com/csshttps://use.typekit.nethttps://p.typekit.nethttps://platform-cdn.uipath.comScripts: https://primer.typekit.nethttps://use.typekit.nethttps://platform-cdn.uipath.com |
|
Sign in via Auth0 (for EU) |
uipath.eu.auth0.com |
|
Update services |
ctldl.windowsupdate.comTo configure network connections, use Microsoft documentation. |
| Download Autopilot for Everyone from the AI Trust Layer admin section |
|
Outbound IP ranges to enable a firewall for the customer-managed key
Required only when the Automation Cloud Portal must connect to your Azure Key Vault for Customer-Managed Key (CMK) scenarios. These outbound IP ranges represent the source IP ranges that your firewall must allow. For details, refer to the Enabling the firewall for the customer-managed key documentation.
| Regions | Existing outbound IP ranges | Upcoming outbound IP ranges |
|---|---|---|
| Australia |
|
|
| Canada |
|
|
| Community |
|
|
| European Union |
|
|
| European Union (delayed) |
|
|
| India |
|
|
| Japan |
|
|
| Singapore |
|
|
| United Kingdom |
|
|
| United States |
|
|
| United States (delayed) |
|
|
| Switzerland |
|
|
| United Arab Emirates |
|
|
Domains
The following table lists the domains used by Action Center that we recommend allowing, based on the functionality you plan to use:
|
Scenario |
Domains to Allow |
|---|---|
|
Authentication |
|
| Navigate to Action Center page |
|
| View/Assign/Un-assign/Delete an Action |
|
| Storage bucket (File upload/download) |
|
Domains
The following table lists the domains used by AI Center:
|
Module or Scenario |
Domains to Allow |
|---|---|
|
AI Center | |
|
Identity Server |
|
|
PkgManager |
|
|
Deployer |
|
|
Helper |
|
|
Trainer |
|
|
AppManager |
|
|
Upload files |
Australia:
https://aifproddataauetraining.blob.core.windows.netCanada:
https://aifproddatacactraining.blob.core.windows.netEurope:
https://aifproddatawetraining.blob.core.windows.netJapan:
https://aifproddatajaetraining.blob.core.windows.netSingapore:
https://aifproddataseatraining.blob.core.windows.netUSA:
https://aifproddataeustraining.blob.core.windows.netGXP:
https://aifgxpdatawetraining.blob.core.windows.net |
|
Third-party Services | |
|
AppInsights |
|
|
Static Assets |
|
|
Navigate to AI Center | |
|
Permissions |
|
|
OpenId configuration |
|
The following table lists the endpoint values and server locations used by AI Computer Vision:
|
Endpoint Value |
Server Location |
|---|---|
|
|
Nearest geolocation based on the request IP |
|
|
West Europe |
|
|
US |
|
|
Delayed enterprise ring deployment, located in the United States |
Outbound IP ranges
Allow the following outbound IP ranges to establish communication between the Bring your own LLM functionality of AI Trust Layer, and your own system:
| Region | Current outbound IP ranges | Upcoming outbound IP ranges |
|---|---|---|
| Australia |
|
|
| Canada |
|
|
| Europe (European Union) |
|
|
| European Union delayed |
|
|
| Community (Europe) |
|
|
| India |
|
|
| Japan |
|
|
| Singapore |
|
|
| United Kingdom |
|
|
| United States |
|
|
| United States delayed |
|
|
Domains
The following table lists the domains used by Apps that you need to allow:
| Scenario | Domains to Allow |
|---|---|
| Navigate to Apps |
|
| Create apps, or create apps via import, or add or delete process |
|
| Export, clone, share, delete, edit, or publish an app |
|
| Run or preview an app |
|
| Select on Processes or Create rule |
|
| Bind process |
|
| General or Permission |
|
| Create or delete a page, or create or delete History |
|
| Connect to Apps |
|
Outbound IP ranges
The Apps service uses the outgoing IP ranges listed below for all external communications. The following table shows the available outbound IP ranges for each region.
| Region | Current outbound IP ranges | Upcoming outbound IP ranges |
|---|---|---|
| Europe |
|
|
| Europe (Secondary) |
|
|
| Europe - Community |
|
|
| Europe - Community (Secondary) |
|
|
| US |
|
|
| US (Secondary) |
|
|
| Canada |
|
|
| Canada (Secondary) |
|
|
| Singapore |
|
|
| Japan |
|
|
| Japan (Secondary) |
|
|
| Australia |
|
|
| Australia (Secondary) |
|
|
| India |
|
|
| India (Secondary) |
|
|
| UK |
|
|
| UK (Secondary) |
|
|
| GXP US (Secondary) |
|
|
| GXP US |
|
|
Traffic from this IPs needs to be allowed through the Organization DMZ firewall and any other intermediate firewalls including the firewall on the computer/s in which Orchestrator application is hosted.
- The associated port on which Orchestrator application is hosted needs to be exposed through the DMZ on all relevant firewalls (see the previous point).
- An Orchestrator user who has read and execute access to relevant processes whose credential will be used from UiPath Apps to talk to Orchestrator.
- If using local robot process execution through RobotJS, please ensure RobotJS is properly configured using instructions provided at RobotJS.
Best practices
- Ensure that the On-Premise hosted Orchestrator is only accessible through a secure HTTPS channel.
- Create a low privilege user in Orchestrator that only has read and execute access to just the desired processes/folders and use that for the integration.
CORS policy requirements for Storage Buckets
https://cloud.uipath.com to the acceptedRootURLs list in
the UiPath.Orchestrator.dll.config file.
- If your Orchestrator instance is hosted in Automation Cloud, this configuration is already in place.
- For external buckets, configure the allowed origins as described in the CORS and CSP configuration guide.”
UiPath Apps uploads and downloads files using the SAS URL generated by Orchestrator when interacting with storage buckets hosted in an on-premises environment. End users must have the appropriate permissions granted through that SAS URL to perform both upload and download operations.
If users encounter errors when uploading or downloading files through UiPath Apps, the storage account’s SAS policies or access restrictions should be reviewed and updated by the storage owner to ensure the required level of access.
Content types to add to the allow list
application/octet-stream and
application/zip for downloading specific DLL files required to run
and preview created applications. It is important to ensure the following content types
are allowed within your network settings to avoid interruptions in app
functionality:
application/zip
application/octet-stream
application/json
text/html
application/javascript
text/css
font/woff2
image/vnd.microsoft.icon
image/svg+xml
image/bmp
image/jpeg
image/png
image/gifapplication/zip
application/octet-stream
application/json
text/html
application/javascript
text/css
font/woff2
image/vnd.microsoft.icon
image/svg+xml
image/bmp
image/jpeg
image/png
image/gifKey Considerations
Apps are developed using Blazor technology, which processes assemblies directly in the browser. If restrictions for the required content types cannot be lifted within your network, Apps may not function as expected, as there are currently no alternative solutions to bypass these limitations.
Apps in Studio Web as an alternative
Apps in Studio Web are designed with a different architecture, that does not require downloading DLL files. If network restrictions prevent the use of Standalone Apps, consider adopting Apps in Studio Web (RPA Apps). This architecture eliminates dependency on restricted content types, ensuring smoother compatibility in restricted network environments.
Outbound IP ranges
Outbound IP ranges for Automation Cloud Robots - Serverless enable you to route outbound network traffic through a dedicated, static IP address ranges managed by UiPath. This allows you to whitelist or securely integrate with external systems that restrict incoming connections to known IPs.
Configuration
You can enable static outbound IP ranges while creating the Serverless template and going to the Network Configuration page.
Availability
The outbound IP ranges can sometimes change as a result of infrastructure deployments. To help keep you on top of any changes, we have compiled a list of up-to-date static outbound IP ranges, in the following tables.
Community Users
| Region | CIDR | Outbound IP ranges |
|---|---|---|
| Europe |
|
|
Enterprise Users
| Region | CIDR | Outbound IP ranges |
|---|---|---|
| Australia |
|
|
| United States |
|
|
| Japan |
|
|
| Europe (European Union) |
|
|
Domains
The following table lists the domains used by Automation Hub:
| Scenario | Domains to Allow |
|---|---|
| Navigate to the Automation Hub page |
http://*.userpilot.io
|
| Use OpenAPI for Automation Hub | https://automation-hub.uipath.comhttp://ah-gxp-openapi-us.uipath.com |
Domains
The following table lists the domains used by Automation Ops:
|
Scenario |
Domains to Allow |
|---|---|
|
Navigate to the Automation Ops page |
|
Outbound IP ranges
| Region | Current outbound IP ranges | Upcoming outbound IP ranges |
|---|---|---|
| Australia |
|
|
| Japan |
|
|
| United States |
|
|
| United States GXP |
|
|
| Europe |
|
|
| Europe GXP |
|
|
| Canada |
|
|
| Singapore |
|
|
| India |
|
|
| UK |
|
|
| Switzerland |
|
|
| United Arab Emirates |
|
|
Domains
The following table lists the domains that IXP uses:
|
Scenario |
Domains to Allow |
|---|---|
|
Admin Portal / Identity Server |
|
| Static assets |
|
| Azure SignalR |
|
| Telemetry |
|
| LaunchDarkly Feature Flags |
|
| Pendo (clickable in-app guides) |
|
| Performance monitoring |
|
Inbound IP ranges
Add the following inbound IP ranges to your allow list to use IXP and create connections:
| Region | Inbound IP ranges |
|---|---|
| Europe |
|
| US |
|
| Japan |
|
| Australia |
|
| Canada |
|
| Singapore |
|
Outbound IP ranges
Allow the following outbound IP ranges for IXP to sync emails from your Exchange. For details, check the Overview Exchange integration.
| Region | Outbound IP ranges |
|---|---|
| Europe |
|
| US |
|
| Japan |
|
| Australia |
|
| Canada |
|
| Singapore |
|
Domains
The following table lists the domains used by Data Fabric:
|
Scenario |
Domains to Allow |
|---|---|
|
All Data Fabric operations |
|
|
Fetching static frontend content |
|
|
Sending notifications to notification hub |
|
|
Getting Feature Flag information |
|
|
Collection of telemetry |
|
Domains
The following table lists the domains used by Document Understanding:
| Module or Scenario | Domains to Allow |
|---|---|
| Navigate to Document Understanding |
|
| Azure |
|
| Network |
|
| Feature flags |
|
| Telemetry |
|
| Azure SignalR |
|
| Storage |
|
| Pendo |
|
| Public endpoints | Check the Public endpoints page for the full list of public endpoints URLs. |
Domains
The following table lists the domains used by Insights:
|
Scenario |
Domains to Allow |
|---|---|
|
Navigate to the Insights page |
|
Outbound IP ranges
Outbound IP ranges allow you to add a list of IPs for Log Export and Real Time Data Export features to the allowlist and not open your network to all external IPs. If the Blob storage regions correspond to the respective Insights service region, you cannot use public IPs.
| Insights service region | Blob storage region | Functionality | Outbound static IP ranges |
|---|---|---|---|
| Europe |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| United States of America |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| Australia |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| Japan |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| Canada |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| Singapore |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| India |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| United Kingdom |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| GXP United States of America |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
| ||
| GXP Europe |
| Log Export |
|
| Real Time Data Export |
| ||
| Looker SFTP notifications |
|
Limitations
For Log Export, Google Storage does not support inbound IP restriction.
- Insights US: North Europe, East US
- Insights Europe: North Europe, West Europe (For Community Licensing)
- Insights UK: North Europe, UK South
- Insights Canada: North Europe, Canada Central
- Insights Singapore: North Europe, Southeast Asia
- Insights India: North Europe, Central India
- Insights Australia: North Europe, Australia East
- Insights Japan: North Europe, Japan East
- Insights GXP Europe: North Europe, East US
- Insights GXP US: East US
Outbound IP ranges
Add the following outbound IP ranges to your allow list to use Integration Service and create connections, as described in the following table.
| Region | Existing outbound IP ranges | Upcoming outbound IP ranges | Environment |
|---|---|---|---|
| Australia |
|
| Production |
| Canada |
|
| Production |
| Europe |
|
| Production |
| Japan |
|
| Production |
| India |
|
| Production |
| Singapore |
|
| Production |
| United Kingdom |
|
| Production |
| United States |
|
| Production |
| GxP United States
(Delayed update organizations) |
|
| Production |
| Community |
|
| Production |
*IP addresses marked with an asterisk (*) are designated for newly incorporated Azure regions. These IPs will supersede the existing regional IPs upon completion of the scheduled tenant migration process. For details, refer to the Integration Service release notes.
Domains
Robots send traffic to these Automation CloudTM Orchestrator domains. We recommend that you allow these domains to ensure proper functioning of your automations, as described in the following table:
|
Module or Functionality |
Domains to Allow |
|---|---|
|
UiPath Orchestrator |
https://cloud.uipath.com
https://orch-cdn.uipath.comhttps://account.uipath.com |
|
Automation CloudTM Robots - VM |
https://cloud.uipath.com
|
|
Storage |
*.blob.core.windows.netIf using Amazon s3 buckets:
|
|
Package and library feeds (library, tenant processes, and others) |
https://pkgs.dev.azure.com |
|
Azure SignalR |
*.service.signalr.net |
|
Studio and Robot auto-update functionality |
https://download.uipath.com |
|
Traffic Manager (internal) |
*.trafficmanager.net |
Outbound IP ranges
We recommend allowing these outbound IP ranges, which send traffic from Orchestrator towards your resources. For details, refer to Orchestrator outbound IP ranges.
|
Region |
CIDR |
Outbound IP ranges |
|---|---|---|
|
Europe (European Union) |
|
|
|
Region |
CIDR |
Outbound IP ranges |
|---|---|---|
|
Australia |
|
|
|
Canada |
|
|
|
United States |
|
|
|
Japan |
|
|
|
Europe (European Union) |
|
|
|
Singapore |
|
|
|
United Kingdom |
|
|
|
India |
|
|
|
Switzerland |
|
|
|
United Arab Emirates |
|
|
Delayed update organizations
|
Region |
CIDR |
Outbound IP ranges |
|---|---|---|
|
Europe (European Union) |
|
|
|
United States |
|
|
Domains
| Module or Scenario | Domains to Allow |
|---|---|
| Identity Server |
|
| Static assets |
|
| Azure SignalR |
|
| Telemetry |
|
| Upload files |
|
| LaunchDarkly Feature Flags |
|
Domains
The following table lists the domains used by Solutions:
|
Scenario |
Domains to Allow |
|---|---|
|
Navigate to the Solutions Management page |
|
|
Storage | *.blob.core.windows.net |
Domains
The following table lists the domains used by Studio Web:
| Module or Functionality | Domains to Allow |
|---|---|
|
Azure SignalR |
|
|
UiPath products |
|
|
UiPath products (in-app feedback) |
|
|
UiPath products (static assets) |
|
|
UiPath products (telemetry) |
|
|
Third-party services (clickable guides) |
|
|
Third-party services (feature flags provider) |
|
|
Third-party services (storage) |
|
|
Third-party services (telemetry) |
|
|
Third-party services (translations helper) |
|
Domains
If your company uses proxies, the URLs, described in the following table, need to be added to the Firewall Exceptions so the Task Mining desktop components connect to our web servers.
|
Component |
URL |
Port |
|---|---|---|
|
Admin Portal |
|
443 |
|
Web Portal |
|
443 |
|
Pendo |
|
443 |
|
Azure App Insights |
|
443 |
| Azure Signalr |
|
443 |
|
Avatars |
|
443 |
This section lists the domains used by Test Manager and the outbound IP ranges that you should consider allowing if you want to use various Test Manager capabilities.
Domains
The following table lists the domains used by Test Manager that we recommend allowing, based on the functionality you plan to use:
| Module or functionality | Domains to allow |
|---|---|
| UiPath Test Manager |
|
| Azure SignalR |
|
Outbound IP ranges for RFC connection
Allow the following outbound IP ranges to establish communication between UiPath Test Manager and your SAP system via an RFC connection. The following table shows the available outbound IP ranges for each region.
| Region | Current outbound IP ranges | Upcoming outbound IP ranges |
|---|---|---|
| Australia |
|
|
| Canada |
|
|
| Europe (European Union) |
|
|
| India |
|
|
| GXP United States |
|
|
| Japan |
|
|
| Singapore |
|
|
| United Kingdom |
|
|
| United States |
|
|
Outbound IP ranges for web service connection
Allow the following static outbound IP ranges to enable the communication between UiPath Test Manager and your SAP system, via a web service connection.
Allow these outbound IP ranges through your firewall:
| Regions | Outbound IP ranges |
|---|---|
| Australia |
|
| Canada |
|
| Community |
|
| European Union |
|
| European Union (delayed) |
|
| India |
|
| Japan |
|
| Singapore |
|
| United Kingdom |
|
| United States |
|
| United States (delayed) |
|
Outbound IP ranges for connectors
If you enhance your system's security with a firewall, consider allowing only Test Manager outbound IP ranges for using out-of-the-box connectors.
The following outbound IP ranges apply to all supported regions, including: Australia, Canada, European Union, India, Japan, Singapore, United Kingdom, United States, and GxP United States (delayed).
Allow these outbound IP ranges through your firewall:
| Regions | Outbound IP ranges |
|---|---|
| Australia, Canada, European Union, India, Japan, Singapore, United Kingdom, United States, and GxP United States (delayed) |
|
- Overview
- How to use this page
- Upcoming outbound IP ranges
- Automation Cloud Portal
- Outbound IP ranges to enable a firewall for the customer-managed key
- Action Center
- Domains
- AI Center
- Domains
- AI Computer Vision
- AI Trust Layer - Bring your own LLM
- Outbound IP ranges
- Apps
- Domains
- Outbound IP ranges
- Content types to add to the allow list
- Automation Cloud Robots - Serverless
- Outbound IP ranges
- Automation Hub
- Domains
- Automation Ops
- Domains
- Outbound IP ranges
- IXP
- Domains
- Inbound IP ranges
- Outbound IP ranges
- Data Fabric
- Domains
- Document Understanding
- Domains
- Insights
- Domains
- Outbound IP ranges
- Integration Service
- Outbound IP ranges
- Orchestrator
- Domains
- Outbound IP ranges
- Process Mining
- Domains
- Solutions
- Domains
- Studio Web
- Domains
- Task Mining
- Domains
- Test Manager
- Domains
- Outbound IP ranges for RFC connection
- Outbound IP ranges for web service connection
- Outbound IP ranges for connectors
