August 2026 release notes for Orchestrator in Automation Cloud Public Sector.

Authenticate Azure Storage buckets using Integration Services service-principal connections instead of storage-account access keys. This enables customers' security teams to enforce Entra-based identity and access management policies. For configuration details, see Managing storage buckets.

The cross-folder Jobs view now includes all columns available in folder-level Jobs views, including Started/Ended (relative and absolute), Creation Time, Source, Priority, Machine, Hostname, User interaction, and Healing Agent status. All added columns default to hidden; enable them via the Columns dropdown. See Jobs monitoring for details.

Sidepanels now render on top of primary content instead of pushing it aside. Panels are resizable via a drag handle, with user-chosen width persisting per session. No backdrop is displayed, so interactions with the underlying grid or list continue while the panel is open.

Debug jobs now consistently display the [Studio Debugging] Process label regardless of whether they are Desktop or Web session types. This ensures a uniform debugging experience across job types.

The Orchestrator default API specification is now compliant with the OpenAPI 3.0 specification. The previous specification (V20, based on Swagger 2.0) is deprecated as of this release and will be removed in September 2026. For more information and the full deprecation timeline, see Read me.

In the Additional Settings step of process configuration, the machine size fields for cross-platform processes are renamed for clarity: Cloud Robot - Serverless is now Cloud serverless machine size. The Job Priority selector no longer displays a required-field asterisk that incorrectly marked the field as mandatory. For more information, see Managing processes.

When monitoring jobs, you can now access the parent process directly from the job sidepanel header. Selecting the process link displays the process details within the sidepanel (replacing the job sidepanel), improving navigation efficiency during troubleshooting and monitoring.

When creating a trigger, you can now optionally disable it at creation time. By default, triggers are enabled and start processing items immediately. You can disable a trigger during creation to complete configuration and testing before activating it. This applies to all trigger types: queue, event, and time triggers.

When a tenant is provisioned with a serverless machine, the machine is now automatically assigned to the default modern folder. Previously, the serverless machine was provisioned but required manual assignment to a folder.

For more information, check About Machines.

The job grid displayed in the sidepanel context now hides process-type filters (Type and User interaction) that are not applicable in that context. These filters remain visible in the full jobs grid where they provide value.

For more information on jobs filtering, check the Jobs monitoring page.