Noviembre de 2026

November 2026 release notes for Integration Service in Automation Cloud.

November 5, 2026

Outlook 365 and Microsoft 365: OAuth 2.0 Authorization Code with PKCE

The Microsoft Outlook 365 and Microsoft 365 connectors now support the OAuth 2.0 Authorization Code with PKCE authentication type. Use it to connect with your own Microsoft Entra ID app registration without a client secret, so there is no secret to rotate or maintain.

For details, see Microsoft Outlook 365 authentication and Microsoft 365 authentication.

November 4, 2026

Database Hub and Snowflake: record activities for tables without a primary key

For a table without a primary key, the Get Record, Update Record, Replace Record, and Delete Record activities of the Database Hub and Snowflake connectors are now listed but disabled, with a note on which activity to use instead. Previously, Snowflake didn't list them at all. Insert Record and List All Records work with or without a primary key.

For details, see the frequently asked questions for Database Hub and Snowflake.

Clearer connection errors

When a connection fails, the following connectors now explain the cause and what to change:

• Database Hub — a missing or unresolvable host, a refused or timed-out connection, and a port that doesn't complete a TLS handshake now each have their own message, naming the host and port where relevant. Previously, these failures were reported as invalid credentials.
• Amazon Web Services — a temporary session token used with Access Key authentication is now rejected with a message to use an IAM user access key or the Access key assume role method. Previously, the connection failed with Failed to authenticate with Assume role. For details, see Amazon Web Services authentication.
• Salesforce — when Salesforce rejects the credentials, the message now says which setting or credential to check, followed by the original Salesforce error.
• Microsoft Azure — when Microsoft Entra ID rejects the client credentials, the message now explains the AADSTS error, such as a wrong or expired client secret. A Tenant ID of common, organizations, or consumers is now rejected before the token request. For details, see Microsoft Azure authentication.
• Snowflake — a connection test with a mistyped account URL, or a host that resolves only inside your network, now fails within seconds with a clear message, instead of failing with a generic error after several minutes.
• Private keys — Snowflake key-pair connections and connectors that use a private key to sign a JWT, such as ZoomInfo, now accept PKCS#8 and PKCS#1 private keys with any PEM header. When a key can't be used, the message now says why, for example that the key is encrypted and needs its password, that the password is wrong, or that a certificate or public key was entered instead of the private key.
• Private connections — when the target of a private connection isn't registered for the tenant, the message now says to register the host in UiPath Relay or Private Link, or to choose a public connection.

Corrección de errores

• Jira — connections that use basic authentication with a Jira Cloud site URL that includes a page path, such as one copied from the browser address bar, now work, and existing connections are repaired automatically. Previously, some activities failed or returned the page HTML instead of data.
• Salesforce — triggers with an is one of or is not one of filter on a multi-select picklist field now fire when a record has more than one option selected, instead of only when exactly one is selected. The fix applies in all designers except RPA workflows, and existing triggers pick it up after you open the trigger and publish the project again.
• MCP — connections to the Slack MCP server with a pre-registered app now succeed.
• Microsoft Azure — connections for the US Government and China environments no longer fail with Missing required management token scope.
• Private connections — when the Relay node of a private connection stops, Check connection now shows the connection as Disconnected. Previously, it showed an error while the connection status stayed connected.