> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/integrations-1/impact-sources/build-trackers/azure-pipelines.md).

# Azure Pipelines

## About the integration

Azure Pipelines is the continuous integration tool provided by Azure. It allows you to build, test, deploy your application using automated jobs that are triggered manually or as a consequence of various interactions with your Azure DevOps repository.

It is assumed you already have an active Azure DevOps account and a repository with a working Azure Pipelines configuration.

## Setting up the integration

Refer to the [general instructions on adding Azure DevOps as a code integration](/sleuth-dora/integrations-1/code-deployment/azure-devops.md).

You should also add at least one [Code deployment](/sleuth-dora/modeling-your-deployments/code-deployments.md) based on a Azure repository so that we may use it as a source of Azure Pipelines builds.

## Configuring the integration

Once the integration is successful, find the **Impact sources** section in the sidebar and click the **+ Add** link nested under that section.

![](/files/-MlEpxSKbdLW2cNWeObr)

Select **Azure DevOps** from the dropdown and continue by clicking **Enable and add**.

![](/files/-MlU34LY_HMAR-5ZZ0XI)

Give this build tracking instance a **name** and select which **build** should be used to base the impact measurements on.

![](/files/-MlUIjnYUvgsC2K7HMfy)

That's it! Sleuth will now start verifying your deploys health by tracking whether the selected build is passing or failing. Head over to the Dashboard to start seeing your data in action in the project and deploy health graphs.

## Removing the integration

Refer to the [general instructions on adding Azure DevOps as a code integration](/sleuth-dora/integrations-1/code-deployment/azure-devops.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sleuth.io/sleuth-dora/integrations-1/impact-sources/build-trackers/azure-pipelines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.