> 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-community-build/devops-platform-integration/azure-devops-integration/introduction.md).
# Introduction to Azure DevOps integration
SonarQube's integration with Azure DevOps allows you to maintain code quality and security in your Azure DevOps repositories.
The integration is compatible with both Azure DevOps Server and Azure DevOps Services.
## Key features
With this integration, you’ll be able to:
* Import your Azure DevOps repositories into SonarQube Community Build to easily set up SonarQube Community Build projects.
* Integrate smoothly SonarQube Community Build analysis into your Azure build pipeline with the Azure DevOps extension for SonarQube.
* Report the analysis’ quality gate status right in Azure Pipeline’s Build Summary page.
{% hint style="info" %}
Check out this [video](https://www.youtube.com/watch?v=oYvMmN6G3F0) on SonarQube integration with Azure DevOps.
{% endhint %}
{% hint style="info" %}
SonarQube Community Build doesn’t support the analysis of multiple branches and pull requests. See [Feature comparison table](/sonarqube-community-build/feature-comparison-table.md) to find out which SonarQube deployments support these features and how they integrate with Azure DevOps.
{% endhint %}
## Integration solution overview
Integration is performed at two levels:
* Global: Within your SonarQube instance, an “Azure DevOps Configuration” record is used to manage the SonarQube access to your Azure DevOps Services organization or Azure DevOps Server collection. This record stores:
* Your organization’s or collection’s URL.
* An Azure DevOps Personal Access Token (PAT) which is used by SonarQube to access your Azure DevOps Services organization or Azure DevOps Server collection. This PAT is usually created from a dedicated technical account.
* Project: A project administrator must provide Azure DevOps PAT to import their Azure DevOps repository to SonarQube. SonarQube stores this PAT in its database, enabling it to list and import the repositories the administrator can access.
It means that SonarQube uses two different Azure DevOps PATs:
* The global PAT to access your organization or collection in order to import repositories or report the quality gate status in Azure Pipelines.
* The project PAT to check the user's permissions on repositories when a user imports Azure DevOps repositories.
## Related pages
* [Azure Pipelines integration overview](/sonarqube-community-build/devops-platform-integration/azure-devops-integration/azure-pipelines-integration-overview.md)
* [Setting up Azure DevOps integration at global level](/sonarqube-community-build/devops-platform-integration/azure-devops-integration/setting-up-integration-at-global-level.md)
* [Creating and configuring your Azure DevOps project](/sonarqube-community-build/devops-platform-integration/azure-devops-integration/creating-your-project.md)
* [Setting up project integration](/sonarqube-community-build/devops-platform-integration/azure-devops-integration/project-integation.md)
* [Adding analysis to Azure pipeline](/sonarqube-community-build/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline.md)
* [Troubleshooting analysis](/sonarqube-community-build/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-community-build/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.