October 2026 release notes for Integration Service in Automation Cloud Public Sector.

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.

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.

Perplexity is retiring its Sonar Chat Completions API (supported until September 27, 2026) in favor of the new Agent API. The Perplexity connector in Automation Cloud Public Sector now uses the Agent API for every activity and the Completed Asynchronous Chat Job trigger. Existing workflows keep working, and saved Sonar model IDs are mapped to the matching preset automatically. Re-test any workflows that parse the output of these activities, because the output format, citations, or model behavior may differ slightly.

This release also includes the following changes:

For details, refer to the Perplexity activities release notes.

Microsoft Teams connections can now target Microsoft national clouds. Use the new Environment field to select US Government L4 or US Government L5, the Public Sector domains, 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.