Configure Azure boards and repository

A configured Azure DevOps connection is essential for successful data extraction from Azure Boards in the context of DevOps Intelligence. Similarly, the requirement is to set up an Azure DevOps Intelligence Cloud and Server connection to enable effective data integration from Azure Boards and Azure Repos.

Anticipate future support for the following Azure tools as integral elements of our expanding DevOps Intelligence offering:

Azure Pipelines: This powerful tool enables you to build, test and deploy using CI/CD that is language, platform, and cloud-agnostic. It offers seamless connection capabilities with GitHub or any other Git provider for continuous deployment.

Azure Test Plans: These tools instill confidence in your testing and shipping process. Utilize manual and exploratory testing tools to ensure robust product delivery.

Azure Artifacts: This feature allows you to create, host and share packages within your team and effortlessly add artifacts to your CI/CD pipelines with a single click. The integration of these advanced tools extends the robustness of our DevOps Intelligence platform and ensures streamlined operations and superior output quality.

Access Rights: The connection should possess read permissions for the specific projects and work items we intend to synchronize, ensuring the necessary access for data retrieval.

The following items are prerequisite to integration:

Azure DevOps Account: User must have an active Azure DevOps account. If user don't have one, user can sign up for free on the Azure DevOps account website.

Organization Membership: Ensure that Azure DevOps account is part of at least one organization. User need to be a member of an organization to access its projects and repositories.

Access Policy as Platform Administrator and DevOps Intelligence Administrator: Ensure that the user creating the connection has the necessary access policies. The Platform Administrator role is required to create and manage connections effectively. The DevOps Intelligence Administrator role is also required to create and manage configurations.

DevOps Intelligence currently supports Azure DevOps APIs with version 7.0. Ensure that your Azure DevOps account is on a compatible version to ensure optimal functionality.

Integration of Azure Boards and Azure Repo with DevOps Intelligence

The process for onboarding Azure Boards comprises the following steps, each of which is a multistep procedure:

Create a Personal Access Token.

Create a connection.

Configure the application.

Onboard the Azure Board technical service.

Create a Personal Access Token

Use the following procedure to create a Personal Access Token:

Navigate to Azure DevOps Intelligence homepage.

Click Access User settings → Personal access token → New Token.

Ensure the Organization field is set to All accessible organizations.

Grant Read permissions for Work Items, Code and Project and Team fields.

Alternatively, for full access, choose Full Access to use the same PAT for pulling data from all Azure APIs.

Create a connection

To pull data from Azure Boards, you must establish a connection between DevOps Intelligence and GitHub Actions. Use the following procedure:

Click Settings → IAM → Connections → Add New → Add connection.

Select Add Connection.

For Azure Boards Cloud and Azure Boards Server:

Provide a local connection name.

Set the Host as the Azure DevOps cloud Host URL

Choose Authentication type as 'token'.

For Azure Boards Server (server as host), use the toggle switch to set the host information to Azure DevOps Server.

When the sync-all is enabled, all the organization and repositories for which the user has access will be synced.

When the Archive is enabled, the connection is archived for future use.

Configuring DevOps Intelligence for Azure Boards, recent customers

The procedures in this section are valid only for customers onboarded 6 June, 2024 or after. Procedures for legacy customers are provided in the subsequent section Configuring Azure Boards for DevOps Intelligence, legacy customers.

Having created a connection, you must now configure the application. Use the following procedure:

Click Settings & Utilities → Application Configuration.

Select an existing application or create a new application.

Navigate to Add Tools step.

Select the phase as Plan.

Click Add Tool Configuration.

For Tool engine select Azure Boards.

Complete the configurations, presented in the following tabs:

Release

Work Item Format

Bug Formats

Bug Severity

Bug Status

Click Add Configuration.

Onboarding the Azure Boards technical service

You must now onboard the technical service. Use the following procedure:

Navigate to DevOps Intelligence → Settings & Utilities → Application Configurations.

Click on Overflow menu for the chosen application and click on Onboard Technical Service.

Select the plan for which you want to configure Azure Board. Note It would display all the phase for which this tools has been configured for the application.

For Tool engine, select Azure Boards.

For Connection, select the appropriate connection name from the dropdown list.

You must also select tracking for organizations and repositories.

Organization tracking

For Organization tracking, use the following procedure:

Select an existing application or create a new application.

Navigate to the "Add Tools" step.

For Phase, select Plan.

Click Add Tool Configuration.

For Connection, select the appropriate connection name from the dropdown list.

Select the Organization you want to track.

Leave the Projects field unpopulated.

Repository Tracking

For Repository tracking, use the following procedure:

Navigate to DevOps Intelligence → Settings & Utilities → Tools Configuration → Add Configuration.

For Tool Engine, select Azure DevOps.

For Connection, select the appropriate connection name from the dropdown list.

From the Organization field, select the Organization containing the repository you want to track.

From the Project field, select the repository you want to track.

Deleting the Azure Boards technical service

The administrator may, at will, delete the Azure Boards technical service. Use the following procedure:

Navigate to DevOps Intelligence → Settings & Utilities → Application Configuration.

Expand the application to view all associated phases.

Click the Overflow menu forPlan.

Click Delete Technical Service.

Click Azure Boards for Select Tools Configured. The service displays the Select Organization field

Select the appropriate organization. The service displays the Select Repository field.

Select the appropriate Repository.

Click Delete.

Configuring Azure Repo for recent customers

The procedures in this section are valid only for customers onboarded 6 June, 2024 or after.

Use the following procedure to configure the DevOps Intelligence for Azure Repo:

Tools must be configured for a specific application in a specific DevOps phase. In step 2 of the following procedure you are choosing the application and DevOps phase to associate with Azure Repo as part of the configuration procedure.

Click Settings & Utilities → Application Configuration. You will see a list of existing applications.

Select the existing application for which you want to configure Azure Repo or create a new application.

Click the overflow menu (vertical ellipsis) on the Develop row for the selected application.

Select Add New Tool Configuration from the overflow menu. The service displays the Add Tool Configuration form.

Select Azure Repo for Tool Engine. The service displays the Pull Request Status field.

Enter the status of the pull request for the current version of Azure Repo.

Click Submit.

Onboarding Azure Repo

After configuring Azure Repo, you must onboard the technical service. Use the following procedure:

Click the overflow menu for the selected application.

Select Onboard Technical Service. The service displays the Onboard Technical Service form.

Select Develop for DevOps Phase. The service displays the Tool Engine field.

Select Azure Repo. The service displays the Select Connection field.

Select the appropriate connection. The service displays the Select Organization field.

Select the appropriate organization. The service displays the Select Projects field.

Select the appropriate project. The service navigates to the Application Configuration page.

Click Onboard.

You now have the option of clicking the overflow menu for Develop and selecting Edit/Delete Tools Configuration to confirm that Azure Repo has been fully configured.

Deleting Azure Repo as a technical service

The administrator may, at will, delete the Azure Repo technical service. Use the following procedure:

Navigate to DevOps Intelligence → Settings & Utilities → Application Configuration.

Expand the application to view all associated phases.

Click the Overflow menu for Develop.

Click Delete Technical Service.

Click Azure Repo for Select Tools Configured. The service displays the Select Organization field

Select the appropriate organization. The service displays the Select Repository field.

Select the appropriate Repository.

Click Delete.