---
title: Azure Pipelines configuration
slug: azure-pipelines-configuration
docTags: 
createdAt: 2026-05-28T13:01:35.539Z
---

Learn how to configure  DevOps Intelligence for the integration of Azure Pipelines to broaden the observability of your hybrid IT estate.

To enable effective data synchronization from Azure Pipelines Build into  DevOps Intelligence, it's crucial to establish an adequately configured Azure DevOps connection. This connection is a secure bridge between the two platforms, allowing seamless data transfer and management. Establishing this connection enables DevOps Intelligence  to leverage Azure Pipeline's robust capabilities, enhancing its monitoring and reporting features. This configuration enhances the accuracy and efficiency of data handling and amplifies the overall functionality of the  DevOps Intelligence tool.

**Access rights**: The connection must have the following access right:

- **Build**: Read access right.
- **User profile**: Read access right.

# Roles required

As a user, your permissions determine the actions you can perform on the bring-your-own (BYO) template data. You must view, create, update, and delete roles to perform the respective actions. By default, these permissions are granted to the **Editor**. The **Viewer**, on the other hand, is only endowed with the view role.

# Configuring  DevOps Intelligence for Azure Pipelines recent customers

:::hint{type="info"}
Note: 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 * DevOps Intelligence * for Azure Pipelines, legacy customers*.
:::

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

:::hint{type="info"}
Note: 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 Pipeline as part of the configuration procedure.
:::

1. Click** Settings & Utilities** → **Application Configuration**. You will see a list of existing applications.
2. Select the existing application for which you want to configure Azure Pipelines or create a new application.
3. Click the overflow menu (vertical ellipsis) on the Build row for the selected application.
4. Select **Add New Tool Configuration** from the overflow menu. The service displays the **Add Tool Configuration** form.
5. Select **Build** for **Build Categories**. The service displays the **Tool Engine** field.
6. Select Azure Pipelines for **Tool Engine**. The service displays the **Status** field.
7. Enter the current statuses of the builds of the Azure Pipelines (Passed, Failed and In Progress, multiselect).
8. Click **Submit**.

# Onboarding Azure Pipelines

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

1. Click the overflow menu for the selected application.
2. Select **Onboard Technical Service**. The service displays the Onboard Technical Service form.
3. Select **Build** for **DevOps Phase**. The service displays the Tool Engine field.
4. Select **Azure Pipelines** for **Tool Engine**. The service displays the **Select Connection** field.
5. Select the appropriate connection. The service displays the **Select Organization** field.
6. Select the appropriate organization. The service displays the **Select Projects** field.
7. Select the appropriate project. The service displays the Repository Name field.
8. Select the appropriate repository.
9. Click **Onboard**. The service navigates to the Application Configuration page.
10. You now have the option of clicking the overflow menu for Develop and selecting **Edit/Delete Tools Configuration** to confirm that Azure Pipelines has been fully configured.

# Deleting Azure Pipelines as a technical service

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

1. Navigate to DevOps Intelligence → **Settings & Utilities** → **Application Configuration**.
2. Expand the application to view all associated phases.
3. Click the Overflow menu for **Build**.
4. Click **Delete Technical Service**.
5. Click Azure Pipelines for **Select Tools Configured**. The service displays the **Select Organization** field.
6. Select the appropriate organization. The service displays the **Select Projects** field.
7. Select the appropriate project.
8. Click **Delete**.

# Configuring  DevOps Intelligence for Azure Pipelines, legacy customers

:::hint{type="info"}
Note: The procedures in this section are valid only for customers onboarded before 6 June 2024.
:::

You must choose the Project and Organization and add a Technical Service and additional configurations for customizations to establish the configuration. Extra settings are available to handle the states of **Passed**, **Failed** and **In Progress**, which are terms employed in the  DevOps Intelligence dashboards. You have the flexibility to introduce custom terms for these states. For instance, any value input under the **Passed** category will be interpreted as passed when displayed on the dashboard. Once you have made these selections complete the following steps to configure AWS CodePipeline:

1. Within Kyndryl application, click the overflow **Menu** button from the top left corner, navigate to  DevOps Intelligence and expand the menu.
2. Expand **Settings & Utilities,** then select **Tools Configuration.**
3. Select **Add configuration +** and a **Add tool configuration** form will be displayed; here, you will select:
4. **Azure Pipeline - Build** from the **Tool Engine** dropdown menu.
5. The **Connection**, **Test type**, **Technical service**, **Organization **and **Project** each one from its dropdown menu.
6. And you can fill in the** Additional configuration for customization** section at the bottom of the form if you would like to personalize it with custom terms for **Passed**, **Failed** or **In progress** statuses.
7. Select the **Add configuration** button at the bottom of the form.

After completing the configuration, you can view the configuration details in the table on the configuration page. A sample image showcasing this is provided below for your reference.