> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traversal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure DevOps

> Connect Azure DevOps to correlate incidents with recent code changes.

Connecting Azure DevOps lets Traversal correlate incidents with recent code changes by reading repositories and pull requests, helping it explain "what changed" alongside telemetry evidence. Supports both **Azure DevOps Services** (`dev.azure.com`) and **on-premises Azure DevOps Server**.

This integration is separate from [Azure](/integrations/azure-resource-manager), which covers your Azure cloud resources and Azure Monitor telemetry. Configure both when you want code context together with cloud resource context.

## What Traversal reads

* **Projects** — the projects your token can see, discovered automatically
* **Repositories** — the Git repositories in each project
* **Pull requests** — recent PRs, diffs, reviewers, and review threads
* **Code** — file contents, directory listings, and code search results

## Code access during investigations

Traversal reads code through the Azure DevOps REST API. It can search code across your organization, a single project, or one repository, then open the files it finds. It can also list repository trees and review the pull requests merged around an incident.

For example, you can ask Traversal to:

* "Find where `CheckoutService` configures its database connection timeout."
* "Which pull requests merged into `payments-api` in the hour before this incident?"
* "Compare the failing stack trace with the implementation in the `Platform/orders` repository."

<Note>
  On Azure DevOps Server, code search requires the Code Search extension to be installed and configured for your collection. Without it, Traversal can still browse repositories, read files, and review pull requests.
</Note>

## Setup

<Steps>
  <Step title="Create a personal access token">
    1. In Azure DevOps, open **User settings > Personal access tokens**
    2. Click **New Token**, name it (e.g., `traversal-prod`), and select the organization to scope it to
    3. Grant these read-only scopes:
       * **Code (Read)**
       * **Work Items (Read)**
       * **Build (Read)**
       * **Project and Team (Read)**
    4. Click **Create** and copy the token immediately. Azure DevOps only shows it once

    <Info>
      A username and password will not work. Azure DevOps retired alternate credentials, so a personal access token is the only credential its REST API accepts on both Services and Server.
    </Info>
  </Step>

  <Step title="Find your organization URL">
    * **Azure DevOps Services:** `https://dev.azure.com/your-organization`
    * **Azure DevOps Server:** your collection URL, such as `https://tfs.yourcompany.com/tfs/DefaultCollection`

    Do not include a project name or the `/_apis` path. Traversal adds those automatically.
  </Step>

  <Step title="Configure in Traversal">
    Go to **Company Knowledge > Integrations**, select Azure DevOps, and enter your organization URL and personal access token.

    Click **Save**.

    If the connection check fails, confirm that:

    * the token has not expired and is scoped to the organization you entered
    * the URL is the organization or collection URL, not a project or repository URL
  </Step>
</Steps>

### Scoping access

Traversal sees exactly what the token's user can see. Every project and repository that user can read is available to investigations. To narrow access, create the token under a dedicated user whose permissions are limited to the projects Traversal should read.

## Private network access

If the service endpoint is not directly reachable by Traversal (as is common with self-hosted services), deploy a [Traversal Connector](/architecture/connector) in a network that can reach it. When configuring the integration, select that connector under **Network Access Needed**. The service endpoint does not need public internet exposure.

See [Set up the Traversal Connector](/setup/connector) for deployment and network requirements.

## More information

* [Azure DevOps personal access tokens](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate)
* [Azure DevOps Code Search](https://learn.microsoft.com/en-us/azure/devops/project/search/get-started-search)
* [Azure DevOps REST API](https://learn.microsoft.com/en-us/rest/api/azure/devops/)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.