# Configure Azure DevOps Integration

The Azure DevOps Incidents ingestion plan allows Sprinto to automatically ingest and monitor incident data from your Azure DevOps environment. Once configured, Sprinto syncs incident records from selected Azure DevOps projects and surfaces them under the Incidents module in the Data Library.

You can authenticate the integration using either:

* Azure DevOps credentials
* A Personal Access Token (PAT)

After authentication, you must configure the projects that Sprinto should monitor.

### Prerequisites

Before configuring the integration, ensure that:

* You have administrator access to Azure DevOps.
* You have access to the Azure DevOps organisation you want to connect.
* You have the required project permissions to access incidents and work items.
* If you are using a Personal Access Token, ensure that the token has the required read permissions.

### Configure the Azure DevOps Incidents ingestion plan

1. Log in to the Sprinto dashboard.
2. Go to **Ingestion**.
3. Open the **Plans** tab.
4. Click **New Plan**.

<figure><img src="/files/vVoiM9SozIC1PjGbCGrk" alt="" width="563"><figcaption></figcaption></figure>

5. Click **New Plan**.
6. Select **From Template**.

<figure><img src="/files/9D6Kds4Nixd8u8tBZ44o" alt="" width="563"><figcaption></figcaption></figure>

7. Click **Preview** next to **Azure DevOps Incidents**.

<figure><img src="/files/bILoC57sKGfLwyvtUeOG" alt="" width="375"><figcaption></figcaption></figure>

5. Click **View** to open the template.
6. Click **Connect to Azure DevOps (Incidents)** connection.

<figure><img src="/files/Ikp9DdtK8YqGVE1mAJBQ" alt="" width="375"><figcaption></figcaption></figure>

You can now choose one of the following authentication methods:

* My credentials
* Personal access token

<figure><img src="/files/aOTLtOLEMEP2SKwoRqtm" alt="" width="347"><figcaption></figcaption></figure>

***

## Authenticate using Azure DevOps credentials

1. In the authentication window, select **My credentials (recommended)**.
2. Click **I am an admin**.
3. Review the required permissions.
4. Click **Next**.

<figure><img src="/files/EM393oQoozgaDltMKGoX" alt="" width="346"><figcaption></figcaption></figure>

5. Enter your **organization name**.

<figure><img src="/files/BU03VvQxlpmt849zqh9v" alt="" width="354"><figcaption></figcaption></figure>

6. Click **Open Window**.
7. Sign in to your Micorsoft account and follow the on-screen instructions.
8. Complete the authentication flow.

***

## Authenticate using a Personal Access Token

You need to generate a personal access token for this. To do that:

### Generate a Personal Access Token

To learn how to generate a Personal Access Token in Azure DevOps, refer to the official Microsoft documentation:

[Create a Personal Access Token in Azure DevOps](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?utm_source=chatgpt.com)

After the credentials are attached successfully:

1. Wait approximately 45 minutes for the initial sync to complete.
2. Return to the ingestion plan.
3. Click **Refresh**.

<figure><img src="/files/Zl8KzQrD1NZ975Em1N5u" alt="" width="375"><figcaption></figcaption></figure>

Proceed to the next section to configure monitored projects.

### Required permissions for Personal Access Token authentication

The Personal Access Token must include the following read permissions:

<table><thead><tr><th>Permission</th><th width="129.28125">Access level</th><th>Purpose</th></tr></thead><tbody><tr><td>Work Items</td><td>Read</td><td>Required for ticket sync and changelog passthrough</td></tr><tr><td>Project and Team</td><td>Read</td><td>Required for collections sync</td></tr><tr><td>Identity</td><td>Read</td><td>Required for user sync</td></tr><tr><td>Member Entitlement Management</td><td>Read</td><td>Required for user roster enumeration</td></tr></tbody></table>

Ensure that all required permissions are enabled before generating the Personal Access Token.

After that, return to Sprinto:

1. In the authentication window, select **Personal access token**.

<figure><img src="/files/AQi9g3wk219AorQaVLXd" alt="" width="352"><figcaption></figcaption></figure>

2. On the administrator access screen, click **I am an admin**.
3. Review the required read access permissions.
4. Click **Next**.

<figure><img src="/files/EM393oQoozgaDltMKGoX" alt="" width="346"><figcaption></figcaption></figure>

5. Enter your Azure DevOps username.
6. Enter your password.
7. Click **Next**.

<figure><img src="/files/dDrDvYqohdTYlhJHcQ2g" alt="" width="345"><figcaption></figcaption></figure>

8. Enter your Azure DevOps organisation name.
9. Click **Next**.

<figure><img src="/files/rzua0zEhl5f8MqpuFBo0" alt="" width="349"><figcaption></figcaption></figure>

Sprinto begins setting up the account and attaching the credentials.

***

## Configure projects for monitoring (Incidents)

After the initial sync completes:

1. Navigate to **Data Library > Incidents**.
2. Open the **Azure DevOps** tab.
3. Click **Manage Azure DevOps** in the top-right corner.

<figure><img src="/files/WXHQfUUhdSjiSwcHKeiw" alt="" width="563"><figcaption></figcaption></figure>

The configuration drawer displays all available Azure DevOps projects.

### Configure monitored projects

For each project:

1. Select or deselect the project checkbox.
2. Configure the closure statuses.
3. Enter the work item type.
4. Click **Save**.

<figure><img src="/files/EzwE0ITyWAtQncNGvALi" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}

#### Important

* The **Work Item Type** field is case sensitive.
* Ensure that the value exactly matches the work item type configured in Azure DevOps.
  {% endhint %}

After saving the project configuration:

1. Navigate back to **Ingestion > Ingestion Plans**.
2. Open the **Azure DevOps Incidents** ingestion plan.
3. Click **Refresh** again.

<figure><img src="/files/i4HCVznMNgjzoaG6AIQu" alt="" width="375"><figcaption></figcaption></figure>

The integration setup is now complete.

### What happens after configuration?

Once configured, Sprinto:

* Syncs incidents from the selected Azure DevOps projects
* Tracks incident statuses and updates
* Maps configured work item types
* Displays incident records under the Azure DevOps tab in the Incidents module

## Configure projects for monitoring (Change Management)

Use the Azure DevOps Change Management integration to monitor ticket approvals and change workflows within Sprinto.

***

### Configure Azure DevOps Change Management

1. Log in to the Sprinto dashboard.
2. Navigate to **Data Library** > **Change management**.
3. In the **Change management systems** tab, select **Ticketing providers**.
4. Click **Add system**.

<figure><img src="/files/D8yqZukBLMb3zqi12RSS" alt="" width="563"><figcaption></figcaption></figure>

5. In the drawer that opens, locate **Azure DevOps Change Management**.
6. Click **Add** next to the integration template.

<figure><img src="/files/YEFi5ZidH294s5Crce97" alt="" width="375"><figcaption></figcaption></figure>

***

### Step 1: Filter tickets to monitor

Configure the Azure DevOps tickets Sprinto should continuously import and monitor.

1. Under **Azure DevOps Change Management Project**, select the project you want to monitor.
2. Under **Advanced filters**, configure the following fields:

| Field                                               | Description                                                                                 |
| --------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **Issue type**                                      | Specify the work item type to monitor. This field is case-sensitive.                        |
| **Ticket status that indicates the change is done** | Specify the ticket status that represents a completed change. This field is case-sensitive. |

3. Under **Change type**, provide details about the type of changes represented by these tickets.
4. Click **Next**.

<figure><img src="/files/g7IAKlyehgdVKsulph0U" alt="" width="375"><figcaption></figcaption></figure>

***

### Step 2: Configure approvals to monitor

Configure the approval states Sprinto should validate before considering a change approved.

1. Under **Approval State 1**, configure:
   * **Ticket state that indicates change is approved**
   * **Who can assign that state**
2. To configure additional approval stages, click **Add another approval state to monitor**.
3. Under **Applicable from**, select the date from which Sprinto should evaluate approval workflows.
4. Under **System Owner**, select the owner responsible for approval-related checks.
5. Click **Finish**.

<figure><img src="/files/sakbw4Bcvci1t3vSOpuR" alt="" width="375"><figcaption></figcaption></figure>

***

### Verify the integration

1. Navigate back to **Data Library** > **Change management**.
2. Open the **Ticketing providers** tab.
3. Verify that the Azure DevOps Change Management project appears in the list.
4. Click **View details** to review the configured integration.

<figure><img src="/files/qQEHAZqIVYnOklwvtSbv" alt="" width="563"><figcaption></figcaption></figure>

### Troubleshoot sync issues

If incidents do not appear after setup:

* Verify that the credentials are active.
* Ensure that the correct projects are selected.
* Confirm that the closure statuses are configured correctly.
* Verify that the work item type matches Azure DevOps exactly.
* Wait for the sync interval to complete and click **Refresh** again.

If the issue persists, contact [Sprinto Support](mailto:support@sprinto.com).


---

# Agent Instructions: 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:

```
GET https://docs.sprinto.com/ingestion/configure-azure-devops-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.