> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/azuredevops.md).

# Azure DevOps

The Appmixer Azure DevOps connector uses Microsoft Entra ID (Azure AD) OAuth 2.0 for authentication. You need to register an application in the Azure portal.

## OAuth app properties

| Property                | Value                                                                                                                                                                                                                                                                                                         |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Conditional.** A multitenant app serves users of any Microsoft Entra tenant. Personal Microsoft accounts (MSA) are not supported for Azure DevOps through Entra ID apps.                                                                                                                                    |
| **Vendor review**       | **By scope.** No review of the app. Users can consent to `user_impersonation` themselves unless their tenant restricts user consent; then a tenant admin grants it. Publisher verification is optional; see [Microsoft](https://docs.appmixer.com/connector-configuration/microsoft.md#oauth-app-properties). |
| **Review time**         | Not applicable. Admin consent, when needed, depends on each customer's admin.                                                                                                                                                                                                                                 |
| **Users before review** | No limit.                                                                                                                                                                                                                                                                                                     |
| **App owner**           | Any Microsoft Entra tenant.                                                                                                                                                                                                                                                                                   |
| **Regions**             | One app for the global Microsoft cloud.                                                                                                                                                                                                                                                                       |
| **Client secret**       | Expires after at most 24 months; Microsoft recommends less than 12.                                                                                                                                                                                                                                           |
| **Rate limits**         | Per user: 200 TSTUs (Azure DevOps throughput units) in a sliding 5-minute window. Over the limit, requests are delayed and then blocked with `429`.                                                                                                                                                           |
| **Checked**             | 2026-11-13                                                                                                                                                                                                                                                                                                    |

**Limitations**

* Users who sign in to Azure DevOps with a personal Microsoft account cannot connect. The Azure DevOps organization must be backed by Microsoft Entra ID, and the user signs in with a work or school account.
* The old Azure DevOps OAuth apps (registered at `app.vssps.visualstudio.com`) do not accept new registrations since April 2025 and are scheduled for removal in 2026. This connector uses Microsoft Entra ID, not those apps.
* When the client secret expires, every connected account fails until you set a new secret in the Backoffice.
* A refresh token that is not used for 90 days expires. The user then connects the account again.

Sources: [Microsoft Entra OAuth apps for Azure DevOps](https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/entra-oauth), [Azure DevOps OAuth deprecation](https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/azure-devops-oauth), [Rate and usage limits](https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/rate-limits), [App credentials](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials), [Refresh tokens](https://learn.microsoft.com/en-us/entra/identity-platform/refresh-tokens). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## 1. Register an Application in Azure Portal

Go to the [Azure portal - App registrations](https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade) and click **+ New registration**.

* **Name**: A name for your application (e.g. "Appmixer Azure DevOps").
* **Supported account types**: Select **Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant)**.
* **Redirect URI**: Select **Web** and set it to your Appmixer callback URL, e.g. `https://api.YOUR_SUBDOMAIN.appmixer.cloud/auth/azuredevops/callback`.

Click **Register**.

## 2. Get Application (Client) ID

After registration, you will be taken to the app's **Overview** page. Copy the **Application (client) ID** - this is your `clientId`.

## 3. Create a Client Secret

1. In the left menu, go to **Certificates & secrets**.
2. Click **+ New client secret**.
3. Add a description and select an expiration period (use the longest available).
4. Click **Add**.
5. Copy the **Value** of the newly created secret immediately - this is your `clientSecret`. It will not be shown again.

## 4. Configure API Permissions

1. In the left menu, go to **API permissions**.
2. Click **+ Add a permission**.
3. Select **Azure DevOps**.
4. Select **Delegated permissions**.
5. Check **user\_impersonation**.
6. Click **Add permissions**.

The final set of permissions should include:

| Permission           | Type      | Description                |
| -------------------- | --------- | -------------------------- |
| `user_impersonation` | Delegated | Azure DevOps - Full access |

## Backoffice configuration

Configuration ID: `appmixer:azuredevops` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — The **Application (client) ID** from the app's **Overview** page in the Azure portal. Not needed when Azure DevOps is authenticated through the Appmixer Auth Hub.
* `clientSecret` — The **Value** of the client secret created above. Replace it here before the secret expires. Not needed with the Auth Hub.
* `outputFilePrefix` — Optional. File name prefix of the CSV file that **List Projects** and **Find Work Items** create when their output is set to *File*; the file is named `<prefix>-<component name>.csv`. Default `azuredevops-objects-export`.

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:azuredevops -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>"
}'
```


---

# 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.appmixer.com/connector-configuration/azuredevops.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.
