Introduction
This guide explains how to setup Microsoft Azure DevOps for use with Cyclr, as well as installing a Microsoft Azure DevOps Connector.
Setup & Authentication
Overview
There are two authentication flows setup on the Microsoft Azure DevOps Connector:
- Entra Token (recommended)
- Azure DevOps OAuth app (being retired by Microsoft)
Note: As of April 2025, no new Azure DevOps OAuth apps are able to be created and the Azure DevOps OAuth platform is due to reach end of life in 2026. We recommend the Entra Token authentication type is used instead. More information from Microsoft can be found here.
Entra Token
Remote Setup in Microsoft Azure – performed by Cyclr Partner
Go to your Microsoft Azure account and register an application. More information can be found here.
When prompted, the Redirect URI should be set to your Cyclr Partner Console’s Callback URL.
Partner Setup in Cyclr Console
Having registered an OAuth app within Microsoft Azure, obtain your:
- Application (client) ID
- Client Secret
Now go to your Cyclr Partner Console:
- Go to Connectors > Application Connector Library.
- Use the search box to locate the Microsoft Azure DevOps Connector entry.
- Select the Pencil button.
- Select the Settings tab.
- Enter the below values:
Property | Description |
---|---|
Application (client) ID | The application (client) ID from registering an Azure OAuth app. |
Client secret | The client secret from registering an Azure OAuth app. |
Tenant ID | The tenant ID from registering an Azure OAuth app. |
- Select Save Changes.
Note: If you leave these values blank, they must be provided each time a Microsoft Azure DevOps Connector is installed.
Cyclr Connector Installation
When installing a Microsoft Azure DevOps Connector, the following values are used:
Property | Description |
---|---|
Application (client) ID | The application (client) ID from registering an Azure OAuth app. |
Client secret | The client secret from registering an Azure OAuth app. |
Tenant ID | The tenant ID from registering an Azure OAuth app. |
Organization ID | The organization ID from the Azure DevOps portal. |
Project name | The project name from the Azure DevOps portal. |
Azure DevOps OAuth app
Note: As of April 2025, no new Azure DevOps OAuth apps are able to be created and the Azure DevOps OAuth platform is due to reach end of life in 2026. We recommend the Entra Token authentication type is used instead. More information from Microsoft can be found here.
Remote Setup in Microsoft Azure DevOps – performed by Cyclr Partner
No new Azure DevOps OAuth apps are able to be created. Please see the Entra token authentication method instead.
Partner Setup in Cyclr Console
Having created an OAuth app within Microsoft Azure DevOps to obtain an app ID and client secret, go into your Cyclr Partner Console:
- Go to Connectors > Application Connector Library.
- Use the search box to locate the Microsoft Azure DevOps Connector entry.
- Select the Pencil button.
- Select the Settings tab.
- Enter the below values:
Property | Description |
---|---|
App ID | The application ID from creating an Azure DevOps OAuth app. |
Client secret | The client secret from creating an Azure DevOps OAuth app. |
Scopes | The scopes to request during application setup. Default: vso.work_full A full list of scopes can be found here. |
- Select Save Changes.
Note: The Tenant ID property must not be set when using this authentication type.
If you leave these values blank, they must be provided each time the Connector is installed.
Cyclr Connector Installation
When installing a Microsoft Azure DevOps Connector, the following values are used:
Property | Description |
---|---|
App ID | The application ID from creating an Azure DevOps OAuth app. |
Client secret | The client secret from creating an Azure DevOps OAuth app. |
Scopes | The scopes to request during application setup. Default: vso.work_full A full list of scopes can be found here. |
Organization ID | The organization ID from the Azure DevOps portal. |
Project name | The project name from the Azure DevOps portal. |
Note: The Tenant ID property must not be set when using this authentication type.