> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/introduction.md).

# Adding analysis to your Azure pipeline

General guidelines to add SonarQube Server 2026.5 analysis to your Azure pipeline.

{% hint style="info" %}
The Azure DevOps Extension for SonarQube Server must be installed in your Azure DevOps organization: see [Azure DevOps Extension](/sonarqube-server/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops.md).
{% endhint %}

1. Before you begin, see [About Azure Pipelines integration](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/integration-overview.md).
2. Create your SonarQube Server project, see [Importing your Azure DevOps repository](/sonarqube-server/project-administration/creating-project/azure-devops/import-repos.md).
3. Set up your project integration with Azure Pipelines. See [Setting up Azure integration for your project](/sonarqube-server/project-administration/creating-project/azure-devops/setting-up-project-integration.md).
4. Add the SonarQube Server analysis to your Azure build pipeline:
   * [Gradle or Maven project with Azure Pipelines](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/gradle-or-maven-project.md)
   * [.NET project with Azure Pipelines](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/dotnet-project.md)
   * [C family project with Azure Pipelines](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/c-family-project.md)
   * [JS, TS, Go, Python, PHP, etc. project with Azure Pipelines](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/js-ts-go-python-php-project.md)
   * [Monorepo projects with Azure Pipelines](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/monorepo-projects.md)
5. Once you have added the SonarQube Server analysis to your build pipeline, you can check the SonarQube Server [Quality gate status in release pipeline](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/quality-gate-status-in-release-pipeline.md).
6. If you want to decorate your pull request with a quality gate status and are not interested to have SonarQube Server annotations in your PR, see the [Setting up Azure integration for your project](/sonarqube-server/project-administration/creating-project/azure-devops/setting-up-project-integration.md#disable-pull-request-annotations) article.

{% hint style="info" %}
The Azure DevOps extension for SonarQube Server running in your Azure pipeline can automatically detect branches or pull requests being built. You don’t need to specifically pass them as parameters to the scanner but you should make sure you have set up the pull request integration in your project. See [Setting up Azure integration for your project](/sonarqube-server/project-administration/creating-project/azure-devops/setting-up-project-integration.md) for more information.
{% endhint %}

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

* [About Azure Pipelines integration](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/integration-overview.md)
* [Binding to Azure DevOps](/sonarqube-server/instance-administration/devops-platforms/azure-devops.md)
* [Importing your Azure DevOps repository](/sonarqube-server/project-administration/creating-project/azure-devops/import-repos.md)
* [Setting up Azure integration for your project](/sonarqube-server/project-administration/creating-project/azure-devops/setting-up-project-integration.md)
* [Troubleshooting analysis with Azure](/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/troubleshooting-analysis.md)

## Related online learning

* <i class="fa-desktop">:desktop:</i> [Configuring code analysis for SonarQube Server with Azure Pipelines](https://www.sonarsource.com/learn/course/sonarqube-server/c4a63806-1807-43c4-bd54-51275a28486a/configuring-code-analysis-for-sonarqube-server-with-azure-pipelines)
* <i class="fa-desktop">:desktop:</i> [Configuring pull request decoration for SonarQube Server using Azure DevOps](https://www.sonarsource.com/learn/course/sonarqube-server/6ab84273-0146-466b-ae2b-476906dc5585/configuring-pull-request-decoration-for-sonarqube-server-using-azure-devops)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/analyzing-source-code/ci-integration/azure-pipelines/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.