Test Cloud release notes

PII in-flight masking now supports four additional country-specific identity entities: Norway Identity Number, Finland National ID, Sweden National ID, and Danish Identity Number. You can enable masking for these entities in your AI Trust Layer policies, alongside the existing supported entities.

For details, see PII masking.

Organizations with strict network security requirements can now connect to Automation Cloud without routing traffic over the public internet. By using Azure Private Link you can establish a private, secure connection between your Azure environment and UiPath Automation Cloud. This means your automation workloads — including Robots and Task Mining devices — connect to UiPath services over a private network path rather than the public internet, reducing exposure to external threats and helping you meet regulatory and compliance requirements.

For more information on Azure Private Link with Automation Cloud, refer to Connecting to UiPath using private link.

This feature is available with the Enterprise licensing plan.

System for Cross-domain Identity Management (SCIM) User Sync is now available in public preview. You can configure it to automate user lifecycle management between your identity provider and your UiPath organization. Built on the SCIM standard, SCIM User Sync eliminates manual user management by synchronizing user creation, updates, and deprovisioning events directly from your corporate directory.

Supported identity providers: Microsoft Entra ID (Azure AD) and Okta. This feature is available in Automation Cloud and Test Cloud only.

For setup instructions, refer to SCIM User Sync.

The outbound IP ranges listed in the AI Trust Layer – Bring your own LLM section of the legacy firewall configuration page were incorrect for most regions. They have now been corrected.

If you use Bring your own LLM, verify that your firewall allowlist matches the outbound IP ranges now listed for your region on the Legacy - Configuring the firewall for Test Cloud page.

Relay client version 26.4.2 supports connecting the persistent tunnel through the standard Automation Cloud URL, cloud.uipath.com:443. This means new 26.4.2 configurations no longer need connectivity to a region-specific relay hostname, such as eu-relay.uipath.com, for the tunnel.

Relay client versions earlier than 26.4.2 continue to work with regional relay hostnames. Keep those hostnames allowlisted until you move to Relay client 26.4.2 or later and connect through cloud.uipath.com.

Availability follows the Relay regional rollout. The new connection path starts reaching standard Test Cloud regions on June 16, 2026, and continues rolling out through June 25, 2026. Delayed regions are scheduled for July 9, 2026. Until the rollout reaches your region, continue using your current Relay client configuration.

For details, see Deploying the Relay client.

Relay client version 26.4.2 adds the relay describe <id> command for inspecting a Relay client's status, service settings, configured paths, and local metadata. The relay list command now shows the relay group name when available, and JSON output includes the full group name.

This release also adds operational controls for log management on installed services. You can set rotated log retention with --log-retention-days during relay start or relay restart, and you can relocate the log directory for an installed service by running relay restart <id> --logs-dir <path>. For container deployments, the Relay client exposes the /healthz endpoint on 0.0.0.0:9090 by default, with --health-addr available to change or disable the bind address.

Data Export is now available in the Admin Portal. Organization administrators can create, manage, and monitor export configurations for UiPath platform data — including Orchestrator events, audit logs, Maestro traces, and agent traces — from a single interface. Supported destinations include Azure Event Hub, AWS SQS, Databricks, Arize, and OpenTelemetry-compatible collectors.

For details, see Data Export.

Data Fabric is now available in the South Korea region with full data residency. For more information about regional availability, see Global cloud regions.

Two new roles - License Viewer and License Administrator - are now available for Automation Cloud organizations. These roles let Org Admins delegate license management without granting full Org Admin access.

The License Viewer role provides read-only access to all Licensing pages in the Admin Console. The License Administrator role provides full access to all licensing actions, equivalent to the licensing capabilities of an Org Admin. Both roles are assignable at the organization level.

For more information, see Licensing roles and Licensing role permissions.

PII in-flight masking now covers files that are dynamically downloaded by agents during runtime and passed as multi-modal inputs to LLMs. This extends existing AI Trust Layer PII protection to file-based agent workflows, ensuring that sensitive content in documents and images is masked before it reaches the model.

No additional configuration is required. Existing AI Trust Layer policies with PII masking enabled for agents automatically apply to dynamically downloaded files.

For configuration details, refer to PII masking.

Correction, June 8, 2026: This feature was released on June 5, 2026, but was not included in the release notes at the time.

You can now run the Relay client as a container image using Podman or Kubernetes, in addition to the existing Linux and Windows installations. The containerized deployment supports high-availability configurations, custom CA certificates, and proxy routing.

For details, see Deploying the Relay client as a container.

Test Cloud now includes two new built-in user groups: App Test Developer and Tester. These groups are optimized for testing scenarios and replace the RPA-centric default groups in Test Cloud contexts.

Groups that are not relevant to your Test Cloud subscription — such as Citizen Developers, Automation Users, Automation Developers, and Automation Express — are now hidden from the groups list unless the corresponding licenses are allocated.

For details, see Managing accounts and groups.

When signing up for Test Cloud Trial using a social sign-in option (Google or Microsoft), the system now displays an error if you authenticate with a personal email, rather than silently routing you to a Community account. A business email account is required to create a Test Cloud Trial organization.

For details, see Accessing the platform.

UiPath is unifying outbound IP ranges across Test Cloud services. The current service-specific outbound IP ranges for several services are being merged and updated into a single set of unified outbound IP ranges per regions (for example, United States, Europe, etc.). Once the transition is complete, one regional set of IP ranges covers all services — you no longer need to maintain separate ranges per service.

What is changing: The following services are transitioning to unified outbound IP ranges: Test Cloud Portal, AI Trust Layer, Notification Service, Orchestrator, Test Manager, Apps, Automation Ops, and Integration Service.

What is not changing: Outbound IP ranges for Insights, IXP, and Automation Cloud Robots - Serverless are not affected and retain their existing, service-specific ranges. Domains and inbound IP ranges are not changing for any service.

United Arab Emirates, Switzerland, and South Korea: These regions were not part of the previous per-service IP model. Their outbound IP ranges appear only on the Configuring the firewall for Test Cloud page. If your tenant is in one of these regions, there are no legacy IP ranges to maintain and no dual-allowlist period applies — only the unified IP ranges are needed.

As part of our ongoing global cloud expansion, the South Korea region is now generally available. New tenants can be provisioned in South Korea, with data stored and replicated across multiple availability zones within the region.

The following services support full data residency in the South Korea region:

The following services are available in the South Korea region, but data is routed to the European Union for processing. No data is stored outside South Korea.

For the full regional availability matrix, refer to Global cloud regions.

Relay is now available in the United States delayed and European Union delayed hosting regions. For details, see Relay.