- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- Tenants and services
- Accounts and roles
- External applications
- AI Trust Layer
- Notifications
- Logging
- Troubleshooting

Automation Cloud Public Sector admin guide
Configuring the firewall
This page lists the domains used by Automation CloudTM Public Sector and our other cloud services. You can use this information to compile an allow list for UiPath® software in the configuration of your company's perimeter network.
In the event that your company restricts access to only allowed websites, you must allow accessing the necessary domains based on the UiPath products you use and the scenarios per product that you use. If you do not allow access to the required domains, Automation CloudTM Public Sector may not function as intended.
The following table lists the domains used by Automation Cloud Public Sector Portal:
Scenario |
Domains to Allow |
---|---|
UiPath Automation Cloud Public Sector |
|
Login flows (configured via SSO) |
|
Sign in with Azure Active Directory (Azure AD) |
|
Sign in with UiPath Assistant (basic email) |
For events related to signing in with basic authentication:
|
Sign in with UiPath Studio (basic email) |
For events related to signing in with basic authentication:
|
Static assets: Fonts, Styling and CDN hosted scripts |
Fonts:
Images:
CSS:
Scripts:
|
Sign in via Auth0 (for EU) |
|
Update services |
To configure network connections, use Microsoft documentation. |
App Insights / Google Tag Manager |
|
The following table lists the domains used by Action Center:
Scenario |
Domains to Allow |
---|---|
Navigate to Action Center page |
|
The following table lists the endpoint values and server locations used by AI Computer Vision:
The following table lists the domains used by Automation Hub:
Scenario | Domains to Allow |
---|---|
Navigate to the Automation Hub page |
|
Use OpenAPI for Automation Hub |
|
Access Public Sector in Automation Hub |
|
The following table lists the domains used by Automation Ops:
Scenario |
Domains to Allow |
---|---|
Navigate to the Automation Ops page |
|
The following table lists the domains used by Data Service:
Scenario |
Domains to Allow |
---|---|
All Data Service operations |
|
Fetching static frontend content |
|
The following table lists the domains used by Document Understanding:
Module or Scenario | Domains to Allow |
---|---|
Network and Storage | https://*.uipath.us |
Telemetry and SignalR | https://*.azure.us |
Public endpoints | Check the Public endpoints page for the full list of public endpoints URLs. |
The following table lists the domains used by Insights:
Scenario |
Domains to Allow |
---|---|
Navigate to the Insights page |
|
Static IPs allow you to add a list of IPs for the Log Export functionality to the allowlist and not open your network to all external IPs.
To ensure proper performance for the Log Export functionality, make sure to add the Outbound IPs from the Automation Cloud Public Sector Portal section to the allowlist.
Limitations
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 USGov Virginia region for the blob storage account. For more information on this limitation, check the Restrictions for IP network rules page from the Microsoft Azure Blob Storage documentation.
Robots send traffic to these Automation CloudTM Public Sector Orchestrator domains. We recommend that you allow them to ensure proper functioning of your automations, as described in the following table:
Module or Functionality |
Domains to Allow |
---|---|
UiPath Orchestrator |
|
Automation CloudTM Public Sector Robots - VM |
|
Storage |
If using Amazon s3 buckets:
|
Package and library feeds (library, tenant processes, and others) |
|
Azure SignalR |
|
Studio and Robot auto-update functionality |
|
Traffic Manager (internal) |
|
Module or Scenario | Domains to Allow |
---|---|
Identity Server |
|
Static assets |
|
Azure SignalR |
|
Telemetry |
|
Upload files |
|