# Azure Pipelines integration overview

It allows:

* Integrating smoothly SonarQube analysis into your Azure build pipeline. This includes multi-branch analysis features.
* Reporting the analysis’ quality gate status right in Azure Pipeline’s Build Summary page.
* Checking the SonarQube quality gate status in your Azure release pipeline.

For general information about the SonarQube Server analysis integration into a CI pipeline, see [analysis-overview](https://docs.sonarsource.com/sonarqube-server/2025.2/analyzing-source-code/analysis-overview "mention").

## Extension modes <a href="#extension-modes" id="extension-modes"></a>

The Azure DevOps extension for SonarQube Server can run in one of the following modes depending on your project type:

* **.NET**: for .NET projects. The [introduction](https://docs.sonarsource.com/sonarqube-server/2025.2/analyzing-source-code/scanners/dotnet/introduction "mention") is used.
* **Maven or Gradle**: for Maven and Gradle projects. The [sonarscanner-for-maven](https://docs.sonarsource.com/sonarqube-server/2025.2/analyzing-source-code/scanners/sonarscanner-for-maven "mention") or [sonarscanner-for-gradle](https://docs.sonarsource.com/sonarqube-server/2025.2/analyzing-source-code/scanners/sonarscanner-for-gradle "mention") is used, respectively.
* **CLI**: for the other project types (C family, JavaScript, TypeScript, Go, Python, PHP, etc.). The [sonarscanner](https://docs.sonarsource.com/sonarqube-server/2025.2/analyzing-source-code/scanners/sonarscanner "mention") is used.

The Azure DevOps Extension for SonarQube Server embeds the last compatible version of the SonarScanner for .NET and SonarScanner CLI, which is used by default.

In Maven/Gradle mode, your build task downloads the SonarScanner for Maven or Gradle from the Sonar binaries site.

{% hint style="info" %}
In very particular situations, you may not want to use the extension’s default version but a specific previous version of the SonarScanner for .NET or CLI. In such a case, you can configure your Azure build pipeline to download this specific version from the Sonar binaries site (see [various-features](https://docs.sonarsource.com/sonarqube-server/2025.2/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/various-features "mention")).
{% endhint %}

## SonarQube tasks used in the pipeline definition <a href="#sonarqube-tasks" id="sonarqube-tasks"></a>

The SonarQube Server analysis is integrated into your Azure build pipeline by adding the following SonarQube tasks to your build pipeline definition:

* Prepare Analysis Configuration
* Run Code Analysis\
  This task starts the SonarScanner for .NET or CLI. In the Maven/Gradle mode, it is replaced by a Maven or Gradle task that downloads the SonarScanner for Maven or Gradle, respectively.
* Publish Quality Gate Result\
  With this task, the quality gate status and a link to SonarQube Server are shown in the Azure Pipeline’s Build Summary page.

{% hint style="info" %}
The Publish Quality Gate Result task can significantly increase the overall build time because it will poll SonarQube until the analysis is complete.
{% endhint %}

## Analysis process overview <a href="#analysis-process-overview" id="analysis-process-overview"></a>

The figure below shows the analysis’s main steps with the example of a .NET project :

1. The pipeline’s Run Code Analysis task starts the SonarScanner for .NET embedded in the Azure DevOps Extension for SonarQube Server. (The SonarScanner then downloads its binaries from the server as explained in **Scanner engine and analyzers download** in [analysis-overview](https://docs.sonarsource.com/sonarqube-server/2025.2/analyzing-source-code/analysis-overview "mention").)
2. Once the analysis is complete, the scanner sends the results to SonarQube Server.
3. SonarQube Server sends the quality gate status to Azure DevOps. This information is processed through the pipeline’s Publish Quality Gate Result task.

<figure><img src="https://3577027091-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F69lEOGGgOhCpumODGD9v%2Fuploads%2Fgit-blob-22e80c8a07d6fc5bb4eab76db901eeb7f50a89a5%2Fsonarqube-azure-devops-analysis-process-overview.png?alt=media" alt="The SonarScanner for .NET is invoked twice during the build pipeline in Azure DevOps."><figcaption></figcaption></figure>

## Related pages <a href="#related-pages" id="related-pages"></a>

* [setting-up-integration-at-global-level](https://docs.sonarsource.com/sonarqube-server/2025.2/devops-platform-integration/azure-devops-integration/setting-up-integration-at-global-level "mention")
* [creating-your-project](https://docs.sonarsource.com/sonarqube-server/2025.2/devops-platform-integration/azure-devops-integration/creating-your-project "mention")
* [setting-up-project-integration](https://docs.sonarsource.com/sonarqube-server/2025.2/devops-platform-integration/azure-devops-integration/setting-up-project-integration "mention")
* [introduction](https://docs.sonarsource.com/sonarqube-server/2025.2/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/introduction "mention")
* [troubleshooting-analysis](https://docs.sonarsource.com/sonarqube-server/2025.2/devops-platform-integration/azure-devops-integration/troubleshooting-analysis "mention")