> 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/creating-your-project.md).
# Creating and configuring your Azure DevOps project
Creating your project by importing an Azure DevOps repository.
Once the [Setting up Azure DevOps integration at global level](/sonarqube-community-build/devops-platform-integration/azure-devops-integration/setting-up-integration-at-global-level.md) with Azure DevOps is complete, you can create your SonarQube Community Build project by importing your Azure DevOps repository. You can also create it manually but you won’t benefit from the integration features.
With the Administer System and Create Projects permissions, you can start an import from **Administration** > **Project coverage**, which shows how many of your repositories are imported and analyzed. See the [Project coverage](/sonarqube-community-build/project-coverage.md) page.
{% hint style="warning" %}
It’s highly recommended to create your SonarQube Community Build 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 %}
## Importing your Azure DevOps repository
To import your repository, you need the Create Projects permission in SonarQube Community Build.
The so-created SonarQube Community Build project is "bound" to its Azure DevOps repository. With a bound project, you can see in the SonarQube Community Build UI with which repository the project is associated.
To import an Azure DevOps repository into SonarQube Community Build:
1. In the top navigation bar of SonarQube Community Build, select the **Projects** tab.
2. In the top right corner, select the **Create Project** > **From Azure DevOps** button.
3. If your instance has multiple Azure DevOps Integrations, select the **Azure** **DevOps configuration** from which you want to import your project.
4. Select the repository to be imported.
{% hint style="info" %}
SonarQube Community Build doesn’t support the import of Azure DevOps monorepos. See [Feature comparison table](/sonarqube-community-build/feature-comparison-table.md) to find out which SonarQube deployments support this feature.
{% endhint %}
## Creating your SonarQube Community Build project manually
You need the Create Project permission in SonarQube Community Build.
Proceed as follows:
1. In the top navigation bar of SonarQube Community Build, select the **Projects** tab.
2. In the top right corner, select the **Create Project** > **Local Project** button.
## Configuring the project analysis parameters
You can configure analysis parameters at different levels:
* In your build environment.
* In the `sonar-project.properties` file.
* In SonarQube Community Build UI.
* At the Azure pipeline level.\
Parameters set at the pipeline level have precedence over parameters set at other levels.
For general information on setting up analysis parameters at the global and project levels, see [Analysis parameters](/sonarqube-community-build/analyzing-source-code/analysis-parameters.md) and the respective SonarScanner section: [SonarScanner for Maven](/sonarqube-community-build/analyzing-source-code/scanners/sonarscanner-for-maven.md), [SonarScanner for Gradle](/sonarqube-community-build/analyzing-source-code/scanners/sonarscanner-for-gradle.md), [Configuring the scanner](/sonarqube-community-build/analyzing-source-code/scanners/dotnet/configuring.md), or [SonarScanner CLI](/sonarqube-community-build/analyzing-source-code/scanners/sonarscanner.md).
## 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)
* [Setting up project integration](/sonarqube-community-build/devops-platform-integration/azure-devops-integration/project-integation.md) at the project level
* [Introduction](/sonarqube-community-build/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline/introduction.md) to adding analysis to your Azure build pipeline
* [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/creating-your-project.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.