- Getting started
- Data security and compliance
- Data security and compliance
- Encryption
- Certificates
- Functional security
- Configuring the firewall for Test Cloud
- Legacy - Configuring the firewall for Test Cloud
- Configuring the firewall for Test Cloud Public Sector
- Configuring the firewall for Test Cloud Dedicated
- Feature rollout
- High availability and disaster recovery strategy
- 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
Unified IP ranges for Test Cloud services, organized by global region to replace per-service firewall configurations.
This page lists the unified IP ranges for Test Cloud services. These ranges are organized by global region and cover all services uniformly — you no longer need to maintain separate IP ranges per service.
Transition in progress — action required by September 16, 2026
As of June 16, 2026, unified IP ranges have been published and must be added to your allowlist alongside the legacy per-service IP ranges. Starting September 16, 2026, the legacy IP ranges will be gradually phased out.
Until September 16, 2026: You must allowlist both the legacy per-service IP ranges and the unified IP ranges on this page simultaneously.
After September 16, 2026: Continue allowlisting both the legacy and unified IP ranges until a subsequent release note confirms the legacy IP ranges can be safely removed.
If you are still using the legacy per-service IP ranges, you can find them on the Legacy - Configuring the firewall for Test Cloud page.
Terminology update — July 31, 2026
We renamed "outbound IP ranges" to IP ranges throughout this page. "Outbound" described UiPath's side of the connection, not yours — these ranges are what UiPath connects from, but from your firewall's perspective this traffic is inbound. Domains/FQDNs remain the outbound side, from your perspective. See the Overview section below for the full distinction.
Overview
UiPath services require two types of allow lists, determined by who initiates the connection:
- DNS domain allowlist (FQDNs): Apply when users, robots, or on-premises components connect to UiPath. This traffic is outbound from your network, so add these domains to your firewall's outbound allow list. They must always be allow listed by FQDN, not IP, because UiPath's underlying infrastructure is distributed.
- IP ranges (CIDRs): Apply when UiPath connects to your systems — for example, when Integration Service calls your endpoints, or Orchestrator connects to your on-premises resources. From your firewall's perspective, this traffic is inbound — UiPath is the one connecting into your network — so add the corresponding CIDR blocks to your inbound allow list.
What changed: Previously, IP ranges differed per service and per region. The new model unifies these into a single set of IP ranges per global region. All affected services share the same IP ranges within a region.
For example, in the European Union region, a single set of IP ranges covers Test Cloud Portal, Orchestrator, Integration Service, Apps, Automation Ops, Test Manager, AI Trust Layer, and Notification Service simultaneously.
Exceptions: The following services retain their own service-specific IP ranges and are not covered by the unified table: Insights, IXP, and Automation Cloud Robots - Serverless. For their IP ranges, see Service exceptions.
How to use this page
To configure your firewall for the unified IP ranges:
- Identify the global region of your UiPath tenant and the region of your organization. Some UiPath service features inherit the organization's region rather than the tenant's region. If they differ, you must allowlist the IP ranges for both. For more information on organization-level and tenant-level services, see Global cloud regions. If your tenant or organization migrates to another region, update your IP ranges accordingly.
- Locate your region in the Unified IP ranges table.
- Add all CIDR ranges listed for your region to your firewall's inbound allow list.
- For services with service-specific IP ranges (Insights, IXP, Serverless), see Service exceptions.
- For domain allow lists and IXP's inbound IP ranges, see the relevant service sections on this page.
Unified IP ranges
The following table lists the unified IP ranges by global region. All affected services share these ranges within a region.
| Region | IP ranges |
|---|---|
| Australia | |
| Canada | |
| Community (Europe) | |
| European Union | |
| European Union (GxP) | |
| India | |
| Japan | |
| Singapore | |
| South Korea | |
| Switzerland | |
| United Arab Emirates | |
| United Kingdom | |
| United States | |
| United States (GxP) | |
Service exceptions
The following services retain their own service-specific IP ranges. These are not covered by the unified table and must be configured separately. Their IP ranges are not changing.
Insights
IP ranges allow you to add a list of IPs for Log Export and 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 | Static IP ranges |
|---|---|---|---|
| Europe |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| United States of America |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| Australia |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| Japan |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| Canada |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| Singapore |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| India |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| United Kingdom |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| GXP United States of America |
| Log Export | 134.33.240.104 |
| Data Export | | ||
| Looker SFTP notifications | | ||
| GXP Europe |
| Log Export | |
| Data Export | | ||
| Looker SFTP notifications | | ||
| Switzerland |
| Log Export | |
| Data Export | | ||
| United Arab Emirates |
| Log Export | |
| Data Export | | ||
| South Korea |
| Log Export | |
| Data Export | |
Limitations
For Log Export, Google Storage does not support inbound IP restriction.
Due to a limitation on Microsoft side for Log Export, you cannot set up inbound IP restriction when your Azure blob storage account and the Insights infrastructure is under the same region in Azure. Because of this, you cannot use the following regions for blob storage account based on the Insights service region:
- 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
For more information on this limitation, check the Restrictions for IP network rules page from the Microsoft Azure Blob Storage documentation.
IXP
Allow the following IP ranges for IXP to sync emails from your Exchange. For details, check the Overview Exchange integration.
| Region | IP ranges |
|---|---|
| Europe | 35.204.220.118 |
| US | 34.71.173.219 |
| Japan | 34.84.107.92 |
| Australia | 34.87.223.173 |
| Canada | 34.152.42.160 |
| Singapore | 34.143.128.81 |
Automation Cloud Robots - Serverless
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 lets you allowlist 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 | IP ranges |
|---|---|---|
| Europe | | |
Enterprise Users
| Region | CIDR | IP ranges |
|---|---|---|
| Australia |
|
|
| United States |
|
|
| Japan |
|
|
| Europe (European Union) |
|
|
| Canada |
|
|
| Singapore |
|
|
| United Arab Emirates |
|
|
| United Kingdom |
|
|
| India |
|
|
- Added on February 18th, 2026.
Test Cloud Portal
Allow these domains used by Test Cloud Portal:
If you use Azure buckets, they must not be located in the tenant's region or in the failover region.
Domains
| Scenario | Domains |
|---|---|
| Sign in with basic authentication | https://account.uipath.comhttps://cloud.uipath.comhttps://platform-cdn.uipath.com |
| Sign in with Microsoft | https://aadcdn.msftauth.nethttps://account.uipath.comhttps://cloud.uipath.comhttps://login.live.comhttps://login.microsoftonline.comhttps://platform-cdn.uipath.com |
| Sign in with Google | https://account.uipath.comhttps://cloud.uipath.comhttps://accounts.google.comhttps://google.comhttps://lh3.googleusercontent.comhttps://platform-cdn.uipath.comhttps://www.gstatic.com |
| Sign in with LinkedIn | https://account.uipath.comhttps://cloud.uipath.comhttps://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.nethttps://cloud.uipath.comhttps://login.microsoftonline.com |
| Sign in with UiPath Assistant (basic email) | *-signalr.service.signalr.net For events related to signing in with basic authentication: https://account.uipath.comhttps://cloud.uipath.comhttps://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.com For events related to signing in with basic authentication: https://account.uipath.comhttps://cloud.uipath.comhttps://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.com To configure network connections, use Microsoft documentation. |
| Download Autopilot for Everyone from the AI Trust Layer admin section | https://autopilot-prd.azureedge.net |
Relay
Allow these domains used by the Relay client to establish connectivity to Test Cloud:
| Purpose | Domains | Protocol | Port |
|---|---|---|---|
| Authentication and relay registration | cloud.uipath.com | HTTPS | 443 |
| Relay server - US region | us-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - EU region | eu-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - Canada region | ca-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - Switzerland region | ch-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - Australia region | au-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - Singapore region | sg-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - Japan region | jp-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - South Korea region | kr-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - UAE region | ae-relay.uipath.com | TCP (TLS passthrough required) | 443 |
| Relay server - UK region | uk-relay.uipath.com | TCP (TLS passthrough required) | 443 |
Action Center
Domains
The following table lists the domains used by Action Center that we recommend allowing, based on the functionality you plan to use:
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 | https://cloud.uipath.comhttps://account.uipath.com/https://lh3.googleusercontent.com/ |
| Navigate to Action Center page | https://cloud.uipath.comhttps://uipath-acc-prod.azureedge.net/https://www.youtube.com/https://platform-cdn.uipath.com/https://fonts.gstatic.com/*.googleapis.com |
| View/Assign/Un-assign/Delete an Action | https://cloud.uipath.comhttps://api.smartling.com/https://uipath-acc-prod.azureedge.net/*.cloudfront.nethttps://platform-cdn.uipath.com/https://fonts.gstatic.com/*.googleapis.com |
| Storage bucket (File upload/download) | *.blob.core.windows.net |
AI Center
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.net Canada: https://aifproddatacactraining.blob.core.windows.net Europe: https://aifproddatawetraining.blob.core.windows.net Japan: https://aifproddatajaetraining.blob.core.windows.net Singapore: https://aifproddataseatraining.blob.core.windows.net USA: https://aifproddataeustraining.blob.core.windows.net GXP: https://aifgxpdatawetraining.blob.core.windows.net |
| Third-party Services | |
| AppInsights |
|
| Static Assets |
|
| Navigate to AI Center | |
| Permissions |
|
| OpenId configuration |
|
AI Computer Vision
The following table lists the endpoint values and server locations used by AI Computer Vision:
The following table lists the endpoint values and server locations used by AI Computer Vision:
| Endpoint Value | Server Location |
|---|---|
https://cv.uipath.com | Nearest geolocation based on the request IP |
https://cv-eu.uipath.com | West Europe |
https://cv-us.uipath.com | US |
https://cv-delayed.uipath.com | Delayed enterprise ring deployment, located in the United States |
AI Trust Layer – Bring your own LLM
AI Trust Layer – Bring your own LLM is covered by the unified IP ranges. See the Unified IP ranges table on this page for your region.
Apps
Domains
The following table lists the domains used by Apps that you need to allow:
| Scenario | Domains to Allow |
|---|---|
| Navigate to Apps | https://cloud.uipath.comhttps://fonts.googleapis.comhttps://cdnjs.cloudflare.comhttps://uipath-apps-prd.azureedge.nethttps://fonts.gstatic.comhttps://dc.services.visualstudio.comhttps://<orgname>.uipath.host |
| Create apps, or create apps via import, or add or delete process | https://cloud.uipath.comhttps://uipath-apps-prd.azureedge.net |
| Export, clone, share, delete, edit, or publish an app | https://cloud.uipath.com |
| Run or preview an app | https://cloud.uipath.comhttps://fonts.googleapis.comhttps://cdnjs.cloudflare.comhttps://uipath-apps-prd.azureedge.nethttps://fonts.gstatic.comhttps://dc.services.visualstudio.comhttps://<orgname>.uipath.hosthttps://api.uipath.com |
| Select on Processes or Create rule | https://uipath-apps-prd.azureedge.net |
| Bind process | https://uipath-apps-prd.azureedge.nethttps://cloud.uipath.comhttps://dc.services.visualstudio.com |
| General or Permission | https://api.smartling.com |
| Create or delete a page, or create or delete History | https://cloud.uipath.comhttps://api.smartling.com |
| Connect to Apps | *.trafficmanager.netwss://*.uipath.systemswss://cloud.uipath.com |
Content types to add to the allow list
UiPath Apps utilizes the content types 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/gif
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/gif
Key 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 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.
Automation Hub
Domains
The following table lists the domains used by Automation Hub:
The following table lists the domains used by Automation Hub:
| Scenario | Domains to Allow |
|---|---|
| Navigate to the Automation Hub page | https://cloud.uipath.comhttp://*.userpilot.iohttps://dc.services.visualstudio.comhttps://ah-prod-ts-blue-eu.uipath.comhttps://ah-prod-ts-blue-us.uipath.comhttps://ah-prod-ts-blue-ja.uipath.comhttps://ah-prod-ts-blue-au.uipath.comhttps://ah-prod-ts-blue-ca.uipath.comhttps://ah-prod-ts-blue-sea.uipath.comhttps://ah-prod-ts-blue-uk.uipath.comhttps://ah-prod-ts-blue-in.uipath.comhttps://ah-gxp-ts-blue-us.uipath.com |
| Use OpenAPI for Automation Hub | https://automation-hub.uipath.comhttp://ah-gxp-openapi-us.uipath.com |
Automation Ops
Domains
The following table lists the domains used by Automation Ops:
| Scenario | Domains to Allow |
|---|---|
| Navigate to the Automation Ops page | https://stdadmstgcdn.azureedge.nethttps://app.vssps.visualstudio.comhttps://stdadmstgcdn.blob.core.windows.nethttps://nexus.ensighten.comhttps://cloud.uipath.comhttps://platform-cdn.uipath.comhttps://use.typekit.nethttps://p.typekit.nethttps://content.usage.uipath.comhttps://dc.services.visualstudio.comhttps://data.usage.uipath.com*-signalr.service.signalr.nethttps://s.gravatar.comhttps://i2.wp.comhttps://github.comhttps://github.githubassets.comhttps://avatars.githubusercontent.comhttps://collector.github.comhttps://api.github.com |
Data Fabric
Domains
The following table lists the domains used by Data Fabric:
| Scenario | Domains to Allow |
|---|---|
| All Data Fabric operations | https://cloud.uipath.com |
| Fetching static frontend content | *.cloudapp.azure.com |
| Sending notifications to notification hub | *.service.signalr.net |
| Collection of telemetry | *.visualstudio.com |
Document Understanding
Domains
To ensure proper connectivity, add the following domains to your allowlist:
| Module or Scenario | Domains to Allow |
|---|---|
| Navigate to Document Understanding | https://*.uipath.com |
| Azure | https://*.azure.com |
| Network | https://*.azureedge.nethttps://*.azurefd.net |
| Telemetry | https://*.visualstudio.com |
| Azure SignalR | https://*.service.signalr.net |
| Storage | https://*.trafficmanager.nethttps://*.blob.core.windows.net |
| Pendo | https://*.pendo.io |
| Public endpoints | Check the Public endpoints page for the full list of public endpoints URLs. |
Cloudflare IP range fallback
If your network equipment does not support DNS-based allowlisting, you can use the Cloudflare IP range 104.16.0.0/13 as a fallback. DNS-based allowlisting is recommended because Cloudflare IP ranges are broad and may change.
Insights
Domains
The following table lists the domains used by Insights:
| Scenario | Domains to Allow |
|---|---|
| Navigate to the Insights page | https://cloud.uipath.comhttps://*.lookercdn.comhttps://uipath-insights-statics.azureedge.net/https://*.looker.uipath.com/ |
Integration Service
Integration Service is covered by the unified IP ranges. See the Unified IP ranges table on this page for your region.
IXP
Domains
The following table lists the domains that IXP uses:
| Scenario | Domains to Allow |
|---|---|
| Admin Portal / Identity Server | https://cloud.uipath.com |
| Static assets | https://fonts.googleapis.comhttps://fonts.gstatic.com |
| Azure SignalR | *.service.signalr.net |
| Telemetry | https://*.in.applicationinsights.azure.comhttps://dc.services.visualstudio.com |
| Pendo (clickable in-app guides) | https://*.pendo.io |
| Performance monitoring | https://o486811.ingest.sentry.io |
Inbound IP ranges
This section applies only to legacy Re:infer customers.
Add the following inbound IP ranges to your allow list to use IXP and create connections:
| Region | Inbound IP ranges |
|---|---|
| Europe | 34.91.100.206 |
| US | |
| Japan | 34.84.144.176 |
| Australia | 35.189.46.91 |
| Canada | 34.152.10.176 |
| Singapore | 35.240.179.214 |
Orchestrator
Domains
Robots send traffic to these Test Cloud 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.comhttps://orch-cdn.uipath.comhttps://account.uipath.com |
| Automation Cloud Robots - VM | https://cloud.uipath.comhttps://download.uipath.com |
| Storage | *.blob.core.windows.net If using Amazon s3 buckets: *.s3.amazonaws.com |
| 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 |
Process Mining
Domains
The following table lists the domains used by Process Mining:
| Module or Scenario | Domains to Allow |
|---|---|
| Identity Server | https://cloud.uipath.com |
| Static assets | https://fonts.googleapis.comhttps://fonts.gstatic.comhttps://content.usage.uipath.comhttps://s.gravatar.comhttps://i1.wp.com |
| Azure SignalR | *.service.signalr.net |
| Telemetry | https://*.in.applicationinsights.azure.com |
| Upload files | *.blob.core.windows.net |
Solutions
Domains
The following table lists the domains used by Solutions:
| Scenario | Domains to Allow |
|---|---|
| Navigate to the Solutions Management page | https://cloud.uipath.comhttps://fonts.googleapis.comhttps://fonts.gstatic.comhttps://dc.services.visualstudio.comapi.smartling.comuse.typekit.netp.typekit.nets.gravatar.comi2.wp.comhttps://platform-cdn.uipath.comhttps://sol-cdn.uipath.comhttps://solutions.uipath.com |
| Storage | *.blob.core.windows.net |
| Azure SignalR | *.service.signalr.net |
Studio Web
Domains
The following table lists the domains used by Studio Web:
| Module or Functionality | Domains to Allow |
|---|---|
| Azure SignalR | wss://*.service.signalr.nethttps://*.service.signalr.netwss://*.trafficmanager.net |
| UiPath products | https://*.uipath.com |
| UiPath products (in-app feedback) | https://studio-feedback.azure-api.net |
| UiPath products (static assets) | https://platform-cdn.uipath.comhttps://content.usage.uipath.comhttps://fonts.gstatic.comhttps://d2c7xlmseob604.cloudfront.nethttps://fonts.googleapis.com/https://*.typekit.nethttps://fonts.gstatic.comhttps://s.gravatar.comhttps://secure.gravatar.comhttps://*.wp.comhttps://*.googleusercontent.comhttps://i.ytimg.com |
| UiPath products (telemetry) | https://data.usage.uipath.com |
| Third-party services (clickable guides) | https://*.pendo.io |
| Third-party services (storage) | https://*.blob.core.windows.nethttps://*.amazonaws.com |
| Third-party services (telemetry) | https://dc.services.visualstudio.com |
| Third-party services (translations helper) | https://api.smartling.com |
Task Mining
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.
The Task Mining Desktop application uses web sockets for real-time communication with the server (telemetry and governance). For the URLs and IPs to be allowed, the transparent proxy is expected to have the HTTPS and WSS protocols enabled.
| Component | URL | Port |
|---|---|---|
| Admin Portal | https://cloud.uipath.com | 443 |
| Web Portal | *.blob.core.windows.net | 443 |
| Pendo | https://content.usage.uipath.com | 443 |
| Azure App Insights |
| 443 |
| Azure Signalr |
| 443 |
| Avatars | i2.wp.com/cdn.auth0.com/avatars | 443 |
Test Manager
This section lists the domains used by Test Manager.
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 | https://cloud.uipath.com |
| Azure SignalR | *.service.signalr.net |
- Overview
- How to use this page
- Unified IP ranges
- Service exceptions
- Insights
- IXP
- Automation Cloud Robots - Serverless
- Test Cloud Portal
- Domains
- Relay
- Action Center
- Domains
- AI Center
- Domains
- AI Computer Vision
- AI Trust Layer – Bring your own LLM
- Apps
- Domains
- Content types to add to the allow list
- Automation Hub
- Domains
- Automation Ops
- Domains
- Data Fabric
- Domains
- Document Understanding
- Domains
- Cloudflare IP range fallback
- Insights
- Domains
- Integration Service
- IXP
- Domains
- Inbound IP ranges
- Orchestrator
- Domains
- Process Mining
- Domains
- Solutions
- Domains
- Studio Web
- Domains
- Task Mining
- Domains
- Test Manager
- Domains