# JS, TS, Go, Python, PHP, etc. project with Azure Pipelines
The setup is different depending on whether you use YAML or the Azure Classic interface.
{% hint style="info" %}
* The use of the Classic editor is not always possible (e.g. if your code is stored on GitHub).
* If you use YAML, SonarSource can provide you with YAML templates or code examples.
{% endhint %}
## Before you start
Before you begin, read [About Azure Pipelines integration](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/integration-overview.md).
The prerequisites are:
* The Azure DevOps Extension is installed in your Azure DevOps organization: see [Azure DevOps Extension](/sonarqube-server/2026.2/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops.md).
* Your project is created in SonarQube Server (see [Importing your Azure DevOps repository](/sonarqube-server/2026.2/project-administration/creating-project/azure-devops/import-repos.md)) and configured for Azure Pipelines (see [Setting up Azure integration for your project](/sonarqube-server/2026.2/project-administration/creating-project/azure-devops/setting-up-project-integration.md)).
* The pull request and branch analysis are enabled in your pipeline.
If you need to use a specific scanner version, see [Using Azure DevOps extension's features](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/various-features.md).
## Using YAML
Add the following SonarQube tasks to your YAML pipeline:
1. Before your build task, add a Prepare Analysis Configuration task.
2. After your build task, add a Run Code Analysis task.
3. After the Run Code Analysis task, add a Publish Quality Gate Result task.
See the YAML file example below. See also our [YAML pipeline templates](https://github.com/SonarSource/sonar-scanner-azdo/tree/master/its/fixtures). For information about the SonarQube task inputs, see [SonarQube tasks for Azure Pipelines](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/sonarqube-tasks.md).
{% hint style="info" %}
Make sure the SonarQube task version used in your YAML file is the correct one.\
For example, in `SonarQubePrepare@7`, `7` should correspond to the version of the [Azure DevOps Extension](/sonarqube-server/2026.2/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops.md) you’re using.
{% endhint %}
YAML file example
```yaml
trigger:
- main # or another name representing your main branch
- feature/*
steps:
# Checkout the repository
- checkout: self
# Disable shallow fetch
fetchDepth: 0
# Prepare Analysis Configuration task
- task: SonarQubePrepare@8
inputs:
SonarQube: ''
scannerMode: 'cli'
configMode: 'manual'
cliProjectKey: ''
# Add your build task(s) here
# Run Code Analysis task
- task: SonarQubeAnalyze@8
inputs:
jdkversion: 'JAVA_HOME_17_X64'
# Publish Quality Gate Result task
- task: SonarQubePublish@8
inputs:
pollingTimeoutSec: '300'
```
## Using the Classic editor
In the procedure below, the manual configuration mode is used to define analysis parameters at the pipeline level. You may use the `sonar-project.properties` file instead (or another specified configuration file). For more information, see the [Using Azure DevOps extension's features](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/various-features.md) page.
Proceed as follows:
1. In the Azure DevOps’ Classic editor, create or edit your build pipeline.
2. Add a **Prepare Analysis Configuration** task before your build task:
* In **SonarQube Server Service Endpoint**, select the SonarQube service connection you created during setup. See the [Setting up Azure integration for your project](/sonarqube-server/2026.2/project-administration/creating-project/azure-devops/setting-up-project-integration.md) page for more information about adding a connection.
* Under **Choose a way to run the analysis**, select **Use Standalone SonarScanner CLI**.
* Select the **Manually provide configuration** mode.
* In the **Project key** field, enter your project key.
3. Add a new **Run Code Analysis** task after your build task.
4. Add a new **Publish quality gate Result** on your build pipeline summary.
5. Ensure that the pipeline runs automatically for all the branches you want:
* Under the **Triggers** tab of your pipeline, select **Enable continuous integration** and select all the branches for which you want SonarQube Server analysis to run automatically.
6. Save your pipeline.
## Related pages
* [Gradle or Maven project with Azure Pipelines](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/gradle-or-maven-project.md)
* [.NET project with Azure Pipelines](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/dotnet-project.md)
* [C family project with Azure Pipelines](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/c-family-project.md)
* [Using Azure DevOps extension's features](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/various-features.md)
* [SonarQube tasks for Azure Pipelines](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/sonarqube-tasks.md)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/js-ts-go-python-php.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.