Azure DevOps

Overview

Heeler connects to Azure DevOps at the project level within an organization. To do so, Heeler requires a Personal Access Token with required permissions for Heeler to perform assessments.

Create Personal Access Token

Heeler uses a Personal Access Token to authenticate with an Azure DevOps project and to define its permissions.

1. To create the token, navigate to the specific project of interest and then click on User Settings near your profile icon in the upper righthand corner.

1. In User Settings, click on Personal access tokens

1. Add a New Token. Give it a Name and set a custom Expiration for a time period of your choice. The longest allowable is 365 days. N.b., once the token expires, you will need to repeat this process to re-establish the connection so a longer duration reduces reduces integration maintenance.

1. Then add permissions (Code example in image below). The required permissions are:

• Code: Read

• Graph: Read

• Project and Team: Read

• Work Items: Read

1. After saving, confirm a) the permissions are correct and b) note the Organization because it will be required in Heeler. Copy the token

Add Azure DevOps to Heeler

1. In Heeler, select the Settings icon from the top navigation
2. Select Connections -> Code Organizations then select Add Code Organization

1. Enter a Name for Azure DevOps Organization. It does not need to match the name of the token created, but should be related to the Azure DevOps project for clarity

2. Enter the Organization that matches the organization of the token (see the last step in Azure DevOps)

3. Paste the Access Token

4. Select Save

1. After saving, confirm the connection is Healthy