> 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/2025.1/devops-platform-integration/azure-devops-integration/introduction.md).
# Introduction
The integration of SonarQube Server 2025.1 with Azure DevOps allows you to maintain code quality and security in your Azure DevOps repositories.
It is compatible with both Azure DevOps Server and Azure DevOps Services.
With this integration, you’ll be able to:
* Import your Azure DevOps repositories into SonarQube Server to easily set up SonarQube Server projects.
* Smoothly integrate your SonarQube Server analysis into your Azure build pipeline with our [Azure DevOps Extension](/sonarqube-server/2025.1/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops.md). This includes multi-branch analysis features. See these pages for ALM-specific instructions for adding your analysis using yaml or the Azure Classic editor:
* [Gradle or Maven project](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/gradle-or-maven-project.md)
* [.NET project](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/dotnet-project.md)
* [C family project](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/c-family-project.md)
* [JS, TS, Go, Python, PHP, etc. project](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/js-ts-go-python-php-project.md)
* [Monorepo projects](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/monorepo-projects.md)
* Report the analysis’ quality gate status right in Azure Pipeline’s Build Summary page.
* [Setting up project integration](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/project-integation.md#prevent-pull-request-merges-when-the-quality-gate-fails)
* View issues detected on a pull request in Azure DevOps.\
Each issue will be a comment on the Azure DevOps pull request. If you change the status of an issue in SonarQube Server, that status change is immediately reflected in the Azure DevOps interface.
{% hint style="info" %}
Check out this [video](https://www.youtube.com/watch?v=oYvMmN6G3F0) on SonarQube Server integration with Azure DevOps.
{% endhint %}
## Related pages
* [Azure Pipelines integration overview](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/azure-pipelines-integration-overview.md)
* [Setting up integration at global level](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/setting-up-integration-at-global-level.md)
* [Creating and configuring your project](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/creating-your-project.md)
* [Setting up project integration](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/project-integation.md)
* [Introduction](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/introduction.md) to Adding analysis to your Azure pipeline
* [Troubleshooting analysis](/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/troubleshooting-analysis.md)
---
# 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/2025.1/devops-platform-integration/azure-devops-integration/introduction.md?ask=&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.
