Released for Azure DevOps on July 24th, 2025
Exalate for Azure DevOps now supports OAuth 2.0 as an alternative authentication method to Personal Access Tokens (PATs). This provides greater flexibility for administrators who are unable to use PATs due to organizational or security constraints. More details here.
Key improvements:
Users can now choose between Personal Access Token and OAuth 2.0 during node registration, login, or when updating general settings.
OAuth 2.0 setup includes required fields: Client ID, Tenant ID, Client Secret, and a pre-filled Exalate URL.
Both authentication methods provide full access to all node management and synchronization features.
📊 Access Trend Dashboard from the Exalate Console
Exalate administrators can now securely access a dedicated trend dashboard directly from the UI. This dashboard provides insights into synchronization activity over time, helping admins monitor and understand their node's performance. The link opens in a new tab and is available only to authorized users. More details here.
Additionally, in this release, we've resolved the following issue and implemented improvement:
Bug fixes
- XLT-6402 - Registration failure for AzureNode using OAuth2.0 on standalone setup.
- XLT-6949 - ADO - Error when adding more than one label.
Improvements
- XLT-6852 - Trend dashboard for Exalate;
- XLT-6558 - Added Support for OAuth 2.0 Authentication in Azure DevOps Exalate Nodes.