> 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-cloud/discovering-sonarcloud/integration-with-devops-platforms/azure-devops.md).

# Azure DevOps

SonarQube Cloud’s integration with Azure DevOps allows you to maintain code quality and security in your Azure DevOps repositories. It is compatible with Azure DevOps Services.

{% hint style="success" %}
To get started analyzing your Azure DevOps projects with SonarQube Cloud, see [Getting started with Azure DevOps](/sonarqube-cloud/getting-started/azure-devops.md).
{% endhint %}

## Key features <a href="#key-features" id="key-features"></a>

With this integration, you’ll be able to:

* Sign in to SonarQube Cloud with your Azure DevOps credentials.
* Import your Azure DevOps repositories into SonarQube Cloud to easily set up SonarQube Cloud projects. The bulk import of all existing repositories is supported.
* Use automatic analysis to quickly analyze your code without the need to configure a CI-based analysis. This lets you analyze the main branch and any pull request.
* Use the Azure DevOps extension for SonarQube to integrate SonarQube Cloud analyses into your Azure build pipeline. This includes multi-branch analysis features.
* Report the analysis’ quality gate status right in Azure Pipeline’s Build Summary page.
* 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 Cloud, that status change is immediately reflected in the Azure DevOps interface.
* Import your monorepo into SonarQube Cloud to easily manage the related projects.

<div align="left"><figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2Fgit-blob-f35ec737721acd79df927d68c27678df0f6d3242%2F1b0a1eaa4e44b0ef6c364ebaccb8c00a393d51b6.png?alt=media" alt="SonarQube Cloud and Azure DevOps integration overview."><figcaption><p>How the Azure DevOps extension for SonarQube integrates with SonarQube Cloud</p></figcaption></figure></div>

## Related pages

* [Automatic analysis](/sonarqube-cloud/analyzing-source-code/automatic-analysis.md)
* [Azure Pipelines integration overview](/sonarqube-cloud/analyzing-source-code/ci-based-analysis/azure-pipelines/azure-pipelines-integration-overview.md)
* [Getting started with Azure DevOps](/sonarqube-cloud/getting-started/azure-devops.md)
* [Importing Azure DevOps organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-azure-devops-organization.md)
* [Azure DevOps Extension](/sonarqube-cloud/analyzing-source-code/scanners/sonarcloud-extension-for-azure-devops.md)
* [Azure pipelines](/sonarqube-cloud/analyzing-source-code/ci-based-analysis/azure-pipelines.md)
* [Adding analysis to build pipeline](/sonarqube-cloud/analyzing-source-code/ci-based-analysis/azure-pipelines/adding-analysis-to-build-pipeline.md)
* [Checking quality gate in release pipeline](/sonarqube-cloud/analyzing-source-code/ci-based-analysis/azure-pipelines/quality-gate-status-in-release-pipeline.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-cloud/discovering-sonarcloud/integration-with-devops-platforms/azure-devops.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.