> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/overview/azure-devops-ticketing-system-integration.md).

# Azure Devops Ticketing System Integration

Sprinto integrates with Azure DevOps Ticketing System to monitor change management processes, track work items, and ensure compliance for your audit readiness. This integration connects through Merge.dev to sync your Azure DevOps work items, users, and project data into Sprinto.

This guide explains how to set up the Azure DevOps Ticketing System integration with Sprinto.

## Prerequisites

Before you begin, make sure you have:

* Admin access to your Azure DevOps account.
* A Personal Access Token (PAT) from Azure DevOps with the required permissions.
* Your Azure DevOps organization name ready. You can find this at the top of your Azure DevOps dashboard at <https://dev.azure.com/>.

## Setting up the Integration

{% stepper %}
{% step %}

## Log in to Sprinto

Log in to Sprinto with your credentials.
{% endstep %}

{% step %}

## Navigate to Integrations

Navigate to the Integrations page using either of these options:

* Go to **Settings** at the bottom-left of the screen, then click **Available Integrations**.
* Navigate to **Change Management** under **Data Library** and click **Add System**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FuGfNadKvAMbe38Iqikgv%2Fimage.png?alt=media&amp;token=6eb90789-ab2f-4049-8fc9-e9443c3e9740" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Connect Azure DevOps

Search for **Azure DevOps** under the **Ticketing Software** section and click **Connect**.

A popup window powered by Merge.dev will appear for the connection setup.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2F4CmWYjMG8ZR8JxcTMWZZ%2Fimage.png?alt=media&amp;token=2848ae60-1909-4867-8031-77688d64b923" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Confirm admin access

In the popup window, read the instructions provided. Confirm that you have admin access to your Azure DevOps account, then click **Connect to Azure DevOps**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FcPoMIBIaEHiAi8jJJY4d%2Fimage.png?alt=media&amp;token=2f1299a5-ce84-452a-b6ac-32fc2d9e9945" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Create and enter a Personal Access Token

Enter your Azure DevOps username and the Personal Access Token (PAT) you created.

If you do not have a PAT, create one:

1. Go to <https://dev.azure.com/> and sign in to your Azure DevOps organization.
2. Click your profile icon in the top-right corner and select **Personal Access Tokens**.
3. Click **New Token**.
4. Enter a name for the token, such as `Sprinto Integration`.
5. Set the organization to your Azure DevOps organization.
6. Set the expiration date. An expiration period of 1 year or longer is recommended.
7. Under **Scopes**, select these permissions:
   * **Code:** Read
   * **Build:** Read
   * **Member Entitlement Management:** Read
8. Click **Create** and copy the generated token immediately. The token is shown only once.
   {% endstep %}

{% step %}

## Enter your organization name

Enter your Azure DevOps organization name in the **Organization** field.

You can find your organization name at the top of the page when you log in to <https://dev.azure.com/>.

{% hint style="info" %}
The organization name is the subdomain visible in your Azure DevOps URL, such as `mycompany` in <https://dev.azure.com/mycompany>.
{% endhint %}
{% endstep %}

{% step %}

## Submit the connection

Click **Submit** to connect Azure DevOps.

Sprinto validates the connection through Merge.dev. Once successful, you will see a confirmation message and the integration status will change to **Connected**.
{% endstep %}

{% step %}

## Add Azure DevOps as a change management system

After connecting successfully, navigate to **Change Management** in Sprinto's **Security Hub**.

Click **Add** next to Azure DevOps to add it as a change management system. If you have multiple Azure DevOps accounts, you can add additional accounts.
{% endstep %}

{% step %}

## Select projects for monitoring

Select the projects you want Sprinto to monitor for change management.

Configure the change tracking settings as needed for your compliance requirements.
{% endstep %}
{% endstepper %}

## After Setup

Once setup is complete, Sprinto begins syncing data from your Azure DevOps organization.

The following data is synced into Sprinto:

* **Users** — Members and their roles in your Azure DevOps organization.
* **Collections** — Your Azure DevOps collections/organizations.
* **Tickets** — Work items, bugs, tasks, and user stories.
* **Projects** — Project metadata and configurations.

The initial sync may take 15–30 minutes depending on the size of your Azure DevOps organization. Once complete, Sprinto continuously monitors change management processes and generates evidence for your compliance audits.

## Required PAT Permissions

The Personal Access Token used for this integration requires the following Azure DevOps scopes:

| Scope                             | Permission                                     |
| --------------------------------- | ---------------------------------------------- |
| `vso.code`                        | Read access to code repositories               |
| `vso.build`                       | Read access to build definitions and pipelines |
| `vso.memberentitlementmanagement` | Read access to member entitlements             |

These read-only permissions allow Sprinto to monitor your Azure DevOps change management processes without making changes to your projects.

## Troubleshooting

<details>

<summary>Connection fails after entering credentials</summary>

Verify that your PAT has not expired and has the correct scopes:

* `vso.code`
* `vso.build`
* `vso.memberentitlementmanagement`

Go to <https://dev.azure.com/> and check your Personal Access Tokens. If the token has expired, create a new one and reconnect.

</details>

<details>

<summary>"Organization not found" error</summary>

Ensure you entered the correct organization name.

The organization name is available at the top of the Azure DevOps dashboard. It is case-sensitive, so make sure it exactly matches the name in your Azure DevOps URL.

</details>

<details>

<summary>"Insufficient permissions" error</summary>

Confirm that you have admin access to the Azure DevOps organization you are trying to connect.

Only organization administrators can set up the integration. If you are not an admin, contact your Azure DevOps organization owner.

</details>

<details>

<summary>Data is not syncing after successful connection</summary>

The initial data sync can take 15–30 minutes to complete. If data is still missing after an hour:

* Refresh the Change Management page in Sprinto.
* Verify that the projects are selected and configured for monitoring.
* Check that your PAT has not expired in the Azure DevOps portal.
* If the issue persists, disconnect and reconnect the integration, or contact Sprinto Support.

</details>

<details>

<summary>Reconnecting after PAT expiry</summary>

Azure DevOps PATs have an expiration date. When your PAT expires, Sprinto loses access to your Azure DevOps data.

To reconnect:

1. Create a new PAT in Azure DevOps with the required scopes.
2. Navigate to **Integrations** in Sprinto, find Azure DevOps, and click **Reconnect**.
3. Enter the new credentials in the Merge.dev popup.

</details>

## Need Help?

If you have questions or encounter issues during the integration process, reach out to Sprinto Support through the in-app chat or write to <support@sprinto.com>.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/integrations/overview/azure-devops-ticketing-system-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
