Test Cloud release notes

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.