> 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/remove-integration-access/azure-devops.md).

# Azure DevOps: Remove Sprinto Access

Remove the access Sprinto was given in Azure DevOps. Covers every way Sprinto can be connected to Azure DevOps and the steps to take in Azure DevOps for each.

Use this guide to remove the access you gave Sprinto in Azure DevOps. These steps are done in Azure DevOps, not in Sprinto. To connect Azure DevOps to Sprinto again later, see [Azure DevOps Integration (Access Review & Version Control)](https://docs.sprinto.com/integrations/overview/azure-devops-integration-access-review-and-version-control.md), [Azure Devops Integration (Version Control System)](https://docs.sprinto.com/integrations/overview/azure-devops-integration-version-control-system.md) or [Azure Devops Ticketing System Integration](https://docs.sprinto.com/integrations/overview/azure-devops-ticketing-system-integration.md).

## Which connection method did you use?

Sprinto can be connected to Azure DevOps in 3 ways. Find the method you used, then follow the steps in that section.

| Connection method                                                                           | How to tell                                                                                                                                                                     |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Azure DevOps sign-in (legacy OAuth)](#azure-devops-sign-in-legacy-oauth)                   | You were sent to an approval page on app.vssps.visualstudio.com (Azure DevOps branding) to authorize Sprinto, not a Microsoft sign-in consent screen.                           |
| [Microsoft Entra sign-in](#microsoft-entra-sign-in)                                         | You signed in on a Microsoft (login.microsoftonline.com) consent screen, optionally after entering a Microsoft Entra tenant ID in Sprinto.                                      |
| [Ticketing connection (personal access token)](#ticketing-connection-personal-access-token) | Azure DevOps was connected as a ticketing / change-management / incidents source by entering an Azure DevOps username, organization name and personal access token in a pop-up. |

***

## Azure DevOps sign-in (legacy OAuth) <a href="#azure-devops-sign-in-legacy-oauth" id="azure-devops-sign-in-legacy-oauth"></a>

**Who must do this:** The Azure DevOps user who authorized; Project Collection Administrator for the admin path

**What gets removed:** Sprinto's Azure DevOps OAuth authorization for the user who connected.

### Steps

1. The person who connected: sign in at `https://dev.azure.com/{yourorganization}` and select **User settings** → **Profile**.
2. Select **Authorizations**.
3. Next to Sprinto's app, select **Revoke**, then **Revoke** again. The app may be listed as Sprinto.
4. If that person has left, a Project Collection Administrator can revoke their OAuth authorizations with the Token Admin Revoke Authorizations REST API, or Microsoft's PowerShell script linked from "Revoke personal access tokens for organization users".
5. If you turned off Third-party application access through OAuth (**Organization settings** → **Policies**) to cut Sprinto off, turn it back on before reconnecting with this method.

### Confirm it's removed

Sprinto no longer appears under User settings → Profile → Authorizations for that user.

{% hint style="warning" %}
Microsoft is removing Azure DevOps OAuth in 2026; reconnecting will use Microsoft Entra sign-in instead.
{% endhint %}

**Official guide:** [Microsoft Learn](https://learn.microsoft.com/en-us/azure/devops/organizations/settings/manage-authorizations?view=azure-devops)

***

## Microsoft Entra sign-in <a href="#microsoft-entra-sign-in" id="microsoft-entra-sign-in"></a>

**Who must do this:** Cloud Application Administrator (or Application Administrator) in the Entra tenant your Azure DevOps organization uses

**What gets removed:** Sprinto's enterprise application (service principal) and its consents in your Microsoft Entra tenant.

### Steps

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator in the tenant your Azure DevOps organization is connected to.
2. Browse to **Entra ID** → **Enterprise apps** → **All applications** and search for Sprinto's app. The app may be listed as Sprinto; note its Application ID.
3. Select it, then under Manage select **Properties** → **Delete** → **Yes**.
4. Permanently delete it (otherwise it stays soft-deleted for 30 days): in Graph Explorer run `GET https://graph.microsoft.com/v1.0/directory/deletedItems/microsoft.graph.servicePrincipal?$filter=appId eq '{Application ID}'`, then `DELETE https://graph.microsoft.com/v1.0/directory/deletedItems/{id}`.
5. If a Conditional Access policy targets this app (for example to block it), remove the app from that policy so reconnecting works.

### Confirm it's removed

Sprinto's app no longer appears in Enterprise apps, and the deletedItems query for its Application ID returns nothing.

**Official guide:** [Microsoft Learn](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/delete-application-portal)

***

## Ticketing connection (personal access token) <a href="#ticketing-connection-personal-access-token" id="ticketing-connection-personal-access-token"></a>

**Who must do this:** The Azure DevOps user who created the token; Project Collection Administrator for the admin path

**What gets removed:** The Azure DevOps personal access token created for Sprinto's ticketing connection.

### Steps

1. The person who connected: sign in at `https://dev.azure.com/{organization}`, open **User settings** → **Personal access tokens**.
2. Select the token you created for Sprinto (usually Full access).
3. Select **Revoke**, then **Revoke** in the confirmation dialog.
4. If that person has left, a Project Collection Administrator can revoke their tokens with the Token Admin Revoke Authorizations REST API or Microsoft's PowerShell script (see "Revoke personal access tokens for organization users").
5. Optional: delete any saved copy of the token.

### Confirm it's removed

The token shows as revoked on the user's Personal access tokens page.

{% hint style="warning" %}
Microsoft stops all global personal access tokens on December 1, 2026. When you reconnect, create an organization-scoped token.
{% endhint %}

**Official guide:** [Microsoft Learn](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops)


---

# 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/remove-integration-access/azure-devops.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.
