Automation Ops release notes

The outbound IP range migration announced on October 15, 2025 is now complete for Automation Ops. The IP ranges in the Deprecated Outbound IP ranges column of the firewall configuration page are no longer active. Only the ranges in the Current Outbound IP ranges column are now in use.

What you need to do: Remove the deprecated ranges from your firewall configuration. For the full list of current and deprecated outbound IP ranges, refer to the Automation Ops section of the Configuring the firewall for Automation Cloud page or its Test Cloud equivalent.

Azure DevOps connections in Source Control now use Microsoft Entra ID for authentication, replacing the previous Azure OAuth app registration flow. This change aligns with Microsoft’s ongoing deprecation of legacy OAuth and ensures that your source control integrations remain secure and compliant with current identity standards.

With Entra ID authentication, connecting to Azure DevOps works the same way from a user perspective — you authorize through a familiar Microsoft sign-in flow. Behind the scenes, Entra ID handles token exchange and refresh, providing improved security and better alignment with your organization’s identity and access management policies.

If you have existing Azure DevOps connections, they will continue to work. New connections will use Entra ID authentication by default. A deprecation banner in the Source Control settings alerts you to re-authenticate existing connections at your convenience.

For more information, see Source Control.

When you create a new Azure DevOps connection in Source Control, Automation Ops now automatically detects and reassigns orphaned pipelines that were previously linked to a removed or invalid connection. This eliminates the need to manually reconfigure pipelines after connection changes, reducing downtime and manual effort.

Previously, if a source control connection was removed or became invalid, any pipelines tied to that connection would enter an orphaned state and require manual intervention. With this update, the system identifies matching repositories on the new connection and reassigns affected pipelines automatically in the background.

This change only applies to newly created connections. Existing pipelines that are already in a healthy state are not affected.

For more information, see About CI/CD Pipelines.

We’ve updated the model controls in the AI Trust Layer policy. The existing Azure Open AI toggle has been renamed to Open AI.

This change reflects expanded support for both Azure OpenAI and direct OpenAI services. The Open AI toggle now governs access to all OpenAI models, regardless of whether they are accessed via Azure or directly.