> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/azure-devops/configuring-azure-devops-in-avo-assure.md).

# Configuring Azure DevOps in Avo Assure

This section explains how to set up Azure DevOps in Avo Assure. You will connect Avo Assure to your Azure DevOps account by providing the necessary credentials, repository URL, and API token.

To configure Azure DevOps in Avo Assure, perform the following actions:

1. On the **Home** page, under **Projects**, select the required **Project**.
2. Select **Manage Integration**.
3. Select the **Versioning** tab and select **Azure DevOps**.
4. Enter the required configuration details:
   * **Connection Name**: Enter a name for the Azure DevOps connection.
   * **Access Token**: Enter the token used to authenticate with your Azure DevOps account.
     * **Personal access token (PAT)**: If you use a personal access token, then select the PAT checkbox and enter the token.

{% hint style="info" %}
**Note**: To know more about **Access Token** generation in Azure DevOps, [click here](/avo-assure/integrations-in-avo-assure/versioning/azure-devops/api-token-generation-in-azure-devops.md).
{% endhint %}

* **Repository URL**: Enter the URL of the Azure DevOps repository.
* **Username**: Enter Azure DevOps Username associated with the account.

5. Select **Create** button to finalize the Azure DevOps setup.

{% hint style="info" %}
**Note**: To reset the **Azure DevOps** configuration, select the **Reset** button.
{% endhint %}

<figure><img src="/files/2WEIVEGaOz7lRNaebUf0" alt=""><figcaption></figcaption></figure>

### Roles and permissions in Azure DevOps <a href="#roles-and-permissions-in-bitbucket" id="roles-and-permissions-in-bitbucket"></a>

Azure DevOps controls user access through roles and permissions configured at the repository and branch level.

You can manage access to Azure DevOps repositories using the following permissions:

* **Access Permissions**

  All users can push to and pull from an Azure DevOps repository. The actions they can perform depend on the permissions assigned to the repository and its branches in Azure DevOps.
* **Branch Policies**

  Avo Assure does not restrict pushing to the master branch. Branch restrictions and policies are configured and enforced by the Azure DevOps repository administrator.

The following Avo Assure roles can push and pull test artifacts into Avo Assure.

<figure><img src="/files/61nDQkcmo5hsfuUZHsMz" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**: Quality Engineer (QE) cannot push the test artifacts to Master Branch.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/azure-devops/configuring-azure-devops-in-avo-assure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.