> 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.

## 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 |

## 5. Configure Appmixer Backoffice

Go to the **Connector Configuration** section in the Appmixer Backoffice. Find or add the `appmixer:azuredevops` connector and set the following values:

* **clientId**: The `Application (client) ID` from the Azure portal.
* **clientSecret**: The `Client Secret Value` from the Azure portal.


---

# 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.