---
title: Azure Pipeline Deploy configuration
slug: azure-pipeline-deploy-configuration
docTags: 
createdAt: 2026-05-28T13:01:35.643Z
---

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.

**Azure Pipeline Deploy** is an Azure DevOps service that automates application deployment workflows across development, testing and production environments. It helps teams deliver software reliably by orchestrating deployment processes, tracking releases and enforcing deployment controls.

To enable effective data synchronization from Azure Pipeline Deploy into DevOps Intelligence, it's crucial to establish a properly configured Azure DevOps connection. This connection acts as a secure bridge between the two platforms, enabling seamless data transfer and management. By establishing this connection, DevOps Intelligence can leverage Azure Pipeline Deploy data to enhance monitoring, reporting, and deployment visibility. This integration improves the accuracy and efficiency of data handling while providing deeper insights into software delivery performance and overall operational health.

# Access rights

The connection must have the following access right:

- **Pipeline Resources**: Use 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.

# Configuration

You must choose the Project and Organization, Pipeline name, 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. From the Kyndryl Bridge main menu :inlineImage[]{src="https://api.archbee.com/api/optimize/QU1TIK52ntw5Jsos0uOt5/NK7Yw9tQgnlqBGwu7eG4H-20260601-205917.svg" alt caption width="57" height="57"}, go to **Services** → **Platform Services** → DevOps Intelligence → **Settings & Utilities **→ **Tools Configuration**.
2. Select **Add configuration +** and a **Add tool configuration** form will be displayed; here, you will select:
   - **Azure Pipeline - Deploy** from the **Tool Engine** dropdown menu.
   - Select the** Connection** and **Provider** from the dropdown menu.
   - Enter the **Release name**, **Environment** and **Incident host URL.**
3. Select Yes or No on each following field if the configuration is for a production environment.
4. From each dropdown menu, select the **Technical Service,** **Organization**, **Project** and **Pipeline name.**
5. 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.
6. 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.