October 2026 release notes for Integration Service in Automation Cloud.

The Microsoft OneDrive and SharePoint connector now supports 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 OneDrive and SharePoint authentication.

The Generate Text Completion activity is no longer available for new workflows in the OpenAI and Microsoft Azure OpenAI connectors. Both activities call the legacy Completions API, and OpenAI and Microsoft are retiring every model that runs on it. Use the Generate Chat Completion activity instead.

Existing OpenAI workflows that use the activity fail after OpenAI retires davinci-002 on October 23, 2026.

For details, see the OpenAI and Microsoft Azure OpenAI activities release notes.

In the OpenAI Generate Chat Completion activity, an empty Model name now fails with the error Model Name is required. Please select or provide a model for this activity. Previously, the activity silently used a default model.

For details, see Generate Chat Completion.

The AWS HTTP service name field of Amazon Web Services connections now includes sqs, so you can call Amazon Simple Queue Service (SQS) with the connector's HTTP Request activity.

For details, see Amazon Web Services authentication.

When you select a Vertex AI agent that is not deployed with AdkApp in the Execute Google Vertex Agent activity, the activity now shows a message explaining why the agent has no input fields and how to redeploy it. Previously, the input fields stayed empty without explanation.

For details, see Agent deployment requirement.

The TypeSafe connector is now available in preview. It calls the TypeSafe System One API to make fast choice, score, and yes/no decisions about text or JSON content. You can use its activities in RPA workflows, API workflows, and Maestro agentic processes.

For more information, see About the TypeSafe connector.

The Snowflake and Snowflake Cortex connectors add the External OAuth 2.0 Authorization Code with PKCE authentication type. It signs in through your own identity provider, such as Microsoft Entra ID, without a client secret, and works with any identity provider whose tokens Snowflake accepts through an External OAuth security integration. You provide the provider's authorization, token, and refresh token URLs when you create the connection.

In the Snowflake Cortex connector, the OAuth 2.0 Client credentials authentication type is now named OAuth 2.0 Client Credentials with Microsoft Entra ID.

For details, see Snowflake authentication and Snowflake Cortex authentication.

The Microsoft Teams connector adds the OAuth 2.0 Authorization Code with PKCE authentication type. It connects to an application you register in Microsoft Entra ID as a public client, without a client secret.

For details, see Microsoft Teams authentication.

An administrator can now control whether users in a tenant create Standard connections, Relay connections, or both, using the Connectivity setting on the Feature toggles tab of the Integration Service Automation Ops policy. Both types are allowed by default.

Clearing Standard requires every new connection in the tenant to be created through Relay. Connection types that the policy does not allow are unavailable under Advanced settings when you create a connection.

For details, see Restrict connection types.

The Integration Service Automation Ops policy has a new Custom connectors tab. Administrators can enable or disable custom connectors for each tenant, and configure their authentication types and parameters, as they already do for catalog connectors.

In a tenant where the policy is deployed, custom connectors that are not enabled on the tab are disabled, including custom connectors published after the policy is saved. Existing policies have no custom connector settings, so custom connectors stay disabled in the tenants where those policies are deployed until they are enabled on the new tab.

For details, see Manage custom connectors.

Added October 22, 2026: This change was not included in the release notes when it was released.

Added October 8, 2026: This change was not included in the release notes when it was released.

Microsoft Teams connections can now target Microsoft national clouds. Use the new Environment field to select US Government L4, US Government L5, or China instead of the default Office 365 cloud. Previously, creating a connection for a US Government tenant failed.

For details, see Microsoft Teams authentication.

The Agent 2 Agent (A2A) connector now supports a Scope field for all OAuth 2.0 authentication types: OAuth 2.0 Authorization code, OAuth 2.0 Client credentials, OAuth 2.0 Password, and OAuth 2.0 JWT Bearer. Use it to request a specific scope when the connection authenticates, so the access token is limited to the permissions your automation needs. Existing connections are unaffected and require no changes.