# Importing your Azure DevOps repository
Once the [Binding to Azure DevOps](/sonarqube-server/2026.2/instance-administration/devops-platforms/azure-devops.md) with Azure DevOps is complete, you can create your SonarQube Server project by importing your Azure DevOps repository. You can also create it manually but you won’t benefit from the integration features.
{% hint style="warning" %}
It’s highly recommended to create your SonarQube Server project before running your first analysis. Creating the project from the first analysis has side-effects (e.g., you can’t choose the main branch name).
{% endhint %}
## Before your first repository import
On your first repository import, you will have to insert an Azure Personal Authentication Token (PAT) so that you are able to list the repositories you have access to in Azure DevOps.
Proceed as follows to create your Azure PAT:
1\. Log in to Azure DevOps.
2\. Go to your Azure DevOps organization **User settings** > **Personal access tokens** and select **+ New token**.
3\. On the next page, under **Scopes**, make sure that you specify at least the scope **Code** > **Read**.
4\. Click **Create** to generate the token.
5\. When the personal access token is displayed, copy it (you will have to paste it during your first repository import as described below).\
You may ask your administrator to encrypt this token. See [Sensitive settings](/sonarqube-server/2026.2/instance-administration/security/encrypting-settings.md) for more details.
## Importing your Azure DevOps repository
To import your repository, you need the Create Projects permission in SonarQube Server.
The so-created SonarQube Server project is "bound" to its Azure DevOps repository. With a bound project:
* You can see in the SonarQube Server UI with which repository the project is associated.
* You benefit from pull request integration features.
To import an Azure DevOps repository into SonarQube Server:
1. In the top navigation bar of SonarQube Server, select the **Projects** tab.
2. In the top right corner, select the **Create Project > From Azure DevOps** button.
3. If it’s your first repository import, you’ll be prompted to enter the Azure PAT you created as described in *Before your first repository import* above. Enter your PAT and select **Save**.
4\. If your instance has multiple Azure DevOps Integrations, select the **Azure** **DevOps configuration** from which you want to import your project.
5\. Select the repository to be imported.
## Importing a monorepo
Starting in [Enterprise edition](https://www.sonarsource.com/plans-and-pricing/enterprise/), you can import an Azure DevOps monorepo. See [Managing monorepo projects](/sonarqube-server/2026.2/project-administration/monorepos.md).
## Related pages
* [About Azure Pipelines integration](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/integration-overview.md)
* [Binding to Azure DevOps](/sonarqube-server/2026.2/instance-administration/devops-platforms/azure-devops.md)
* [Setting up Azure integration for your project](/sonarqube-server/2026.2/project-administration/creating-project/azure-devops/setting-up-project-integration.md)
* [Adding analysis to your Azure pipeline](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/introduction.md)
* [Troubleshooting analysis with Azure](/sonarqube-server/2026.2/analyzing-source-code/ci-integration/azure-pipelines/troubleshooting-analysis.md)
* [Creating your project manually](/sonarqube-server/2026.2/project-administration/creating-project/creating-project-manually.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/project-administration/creating-project/azure-devops/import-repos.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.