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:
On the Home page, under Projects, select the required Project.
Select Manage Integration.
Select the Versioning tab and select Azure DevOps.
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.
Note: To know more about Access Token generation in Azure DevOps, click here.
Repository URL: Enter the URL of the Azure DevOps repository.
Username: Enter Azure DevOps Username associated with the account.
Select Create button to finalize the Azure DevOps setup.
Note: To reset the Azure DevOps configuration, select the Reset button.

Roles and permissions in Azure DevOps
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.

Note: Quality Engineer (QE) cannot push the test artifacts to Master Branch.
Last updated