# Introduction

{% hint style="info" %}
The Azure DevOps Extension for SonarQube Cloud must be installed in your Azure DevOps organization: see [sonarcloud-extension-for-azure-devops](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/scanners/sonarcloud-extension-for-azure-devops "mention").  
{% endhint %}

1. Before starting, read the [azure-pipelines-integration-overview](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/azure-pipelines/azure-pipelines-integration-overview "mention") page.
2. Create your SonarQube Cloud project. See [setting-up-project](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/managing-your-projects/administering-your-projects/setting-up-project "mention") and [azure-devops](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/managing-your-projects/administering-your-projects/devops-platform-integration/azure-devops "mention").
3. Set up your project integration with Azure Pipelines. See [setting-up-project-integration](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/azure-pipelines/setting-up-project-integration "mention").
4. Add the SonarQube Cloud analysis to your Azure build pipeline. Here are pages deadicated to each of the unique project types:
   * [gradle-or-maven-project](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/azure-pipelines/adding-analysis-to-build-pipeline/gradle-or-maven-project "mention")
   * [dotnet-project](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/azure-pipelines/adding-analysis-to-build-pipeline/dotnet-project "mention")
   * [c-family-project](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/azure-pipelines/adding-analysis-to-build-pipeline/c-family-project "mention")
   * [js-ts-go-python-php](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/azure-pipelines/adding-analysis-to-build-pipeline/js-ts-go-python-php "mention")
   * [monorepo-projects](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/azure-pipelines/adding-analysis-to-build-pipeline/monorepo-projects "mention")
5. Review the [quality-gate-status-in-release-pipeline](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/azure-pipelines/quality-gate-status-in-release-pipeline "mention") page.
6. Once your project has been successfully analyzed in your build pipeline, you can add a quality gate status widget to your project to monitor the status of your projects directly in your Azure DevOps dashboard. See the [#adding-quality-gate-widget](https://docs.sonarsource.com/sonarqube-cloud/~/changes/1027/analyzing-source-code/ci-based-analysis/adding-analysis-to-build-pipeline/various-features#adding-quality-gate-widget "mention") article for more details.