Action needed: Starting July 20, 2026, analyses running with a Java runtime lower than 21 are no longer supported.
Read the scanner requirements page for more details.
Ctrlk
Start FreeLogin
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configuring project for Azure Pipelines

This page explains project-level settings required if you use Azure Pipelines for your project analysis.

Adding SonarQube service connection to Azure Pipelines (SonarQube endpoint)

Service connections are authenticated connections between Azure Pipelines and external or remote services. You must declare your SonarQube Cloud as a service connection in your Azure DevOps project.

Proceed as follows:

  1. In SonarQube Cloud, create an authentication token that will be used by Azure DevOps to execute the analysis of your project in SonarQube Cloud. To do so, create a Scoped Organization Token (recommended from the Team plan) or a personal access token, and copy it. For more information about tokens, see Managing personal access tokens and Scoped Organization Tokens.

  2. In your Azure DevOps project, go to Project Settings > Service connections.

  3. Select New service connection and then select SonarQube Cloud from the service connection list.

Search for "sonar" when adding a new service connection to your Azure DevOps pipeline.

  1. Set the parameters:

    • In Region (optional) field: If you use the SonarQube Cloud’s US instance, select US. Otherwise, make sure Global is selected (default value).

    • In SonarQube Cloud Token, enter the token created in the first step.

    • In Service Connection Name, enter a memorable name (You will need this name when configuring your Azure build pipelines).

In the example below, the US instance is used.

Enter the service connection parameters. By default, the EU instance (sonarcloud.io) is used. Select US if you use the US region.

  1. Select Verify to verify the connection to the SonarQube Cloud's instance.

  2. Select Save to save your connection.

Enabling the pull request analysis in your build pipeline

The Azure DevOps extension running in your Azure pipeline can automatically detect branches or pull requests being built (you don't need to pass them as parameters to the scanner).

To enable the pull request analysis in your Azure pipeline of code stored on Azure DevOps, you must configure a pull request trigger on the target branch (main development branch) as explained on the Configuring Azure DevOps project binding page.

If your code is stored on GitHub or Bitbucket Cloud, open the expandable content below.

GitHub or Bitbucket Cloud

To configure a pull request trigger in your Azure build pipeline for code stored on GitHub or Bitbucket Cloud:

  1. Select Edit to modify your build pipeline.

  2. Go to the Triggers tab.

  3. Select the correct repository under Pull request validation.

  4. Select Enable pull request validation.

  5. Set up the branch filters: Note that this is the target branch of the pull request. See the Microsoft documentation for more details.

  6. Select Save to update your pipeline.

Related pages

Related online courses

PreviousAzure Pipelines integration overview
NextAdding analysis to build pipeline

Last updated

Was this helpful?