---
title: Configuring Tool Chain Management applications
slug: configuring-tool-chain-management-applications
docTags: 
createdAt: 2026-05-28T13:01:35.119Z
---

Learn how to add applications and their CICD pipeline tools in Toolchain Management to enable the observability of CICD pipeline tools that support services in your hybrid IT estate.

DevOps Intelligence teams commonly use peripheral tools to monitor and manage services for themselves and customers. As services are deployed and updated, and as those updates are developed and deployed, a library of tools is often used to understand both the efficiency and effectiveness of related activities. This provides insights into the tools and teams that are responsible for those tools.

For example, frequent build fails for services that typically pass QA testing can indicate that either testing is not adequate or that existing build processes should be examined to understand why the service passes Test but cannot reliably pass Build. These insights are much easier using tools such as Qmetry and JFrog artifactory and what they tell us about the performance of services on which DevOps and customers rely.

## Configuration procedure

Use the following procedure to configure an application for a new service:

1. Click + **Configure new Application**. the service Navigates to **Step 1 Create Application & Add Tools**.
2. Enter the application name in the **Application Name** field.
3. Select a  DevOps Intelligence phase, for example **Plan**.
4. Click **+ Add Tool(s)**. The service displays the Add Tool(s) panel, and confirms your selected phase, for example **Add Tool(s) to Plan phase**.
5. You have the option of selecting an onboarded tool or adding a new tool, which has not been onboarded.

### Selecting an existing (onboarded) tool

:::Paragraph{listStyleType="decimal" listRestartPolite="1" indent="2"}
Click the down arrow on the **Tool Name** field to display a dropdown list of all onboarded tools.
:::

:::Paragraph{listStyleType="decimal" listStart="2" indent="2"}
Click the tool of choice from the list.
:::

:::Paragraph{listStyleType="decimal" listStart="3" indent="2"}
Enter the URL for the tool instance used for the service in question. For example the URL for the Azure Board project used by your team for the service.
:::

:::Paragraph{listStyleType="decimal" listStart="4" indent="2"}
Click the green plus to add an addtional tool or **Save&#x20;**&#x74;o add the tool(s).
:::

### Creating a new tool

1. Click **Create a new tool +**. The service displays the **Tool Name** and **Tool URL** fields.
2. Enter the tool name in the **Tool Name** field.
3. Enter the URL for the tool instance used for the service in question.
4. Click **Create & Add** tool. The service adds the tool and displays a green plus sign (**+**) and a red **X**.

### Adding additional tools

1. To add an additional tool, click the green plus sign (+)
2. To remove a tool, click the red **X**
3. When all tools have been added, click **Save**.
4. Continue adding tools to each phase until the application is complete.
5. Click **Next**. The service presents the Tools Configuration list displaying all tools added for each phase.
6. Click **Submit**.

## Editing applications

You can edit the application configuration by editing each phase of an application as needed to add and remove tools. Use the following procedure:

1. Click the down arrow next to the application name to expand the application, displaying the eight DevOps Intelligence phases and all tools that have been added.
2. Click the vertical ellipsis located at the far right end of the phase you want to edit to display the overflow menu, containing the **Edit** menu item.
3. Click **Edit** to display the tools for the selected DevOps Intelligence phase.
4. Click **+ Add Tools** to add tools to the phase using the Add tools procedure in the previous section (*Configuration procedure*) or the vertical ellipsis to display the overflow menu with the items **Edit&#x20;**&#x61;nd **Delete**. **Edit&#x20;**&#x61;llows you to edit the URL. **Delete&#x20;**&#x64;eletes the tool from that phase.
