> For the complete documentation index, see [llms.txt](https://docs.kosmoslabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kosmoslabs.ai/connecting-azure-devops.md).

# Connecting Azure DevOps

***

This guide walks you through connecting Azure DevOps to Kosmos.

Kosmos connects to Azure DevOps Boards to sync work items — bugs, tasks, stories, features, and other issue types — as signals for correlation.

### Prerequisites

* An Azure DevOps account with access to the organization you want to sync
* Admin access to Kosmos to configure the integration

***

### Step 1: Start the Connection

1. In Kosmos, navigate to **Settings → Integrations**
2. Find the **Azure DevOps** card and click **Connect**
3. A dialog appears asking for your Azure DevOps organization name

***

### Step 2: Enter Your Organization Name

Enter your Azure DevOps organization name — this is the name that appears in your URL at `dev.azure.com/{organization}`.

For example, if your Azure DevOps URL is `https://dev.azure.com/contoso`, enter `contoso`.

Click **Continue** to proceed.

***

### Step 3: Authorize via Microsoft Entra ID

1. You'll be redirected to Microsoft to authorize the connection
2. Sign in with your Microsoft account if prompted
3. Review the requested permissions and click **Accept**
4. You'll be returned to Kosmos with the connection established

Azure DevOps access tokens expire approximately every hour. Kosmos automatically refreshes them in the background — you won't need to reconnect.

***

### Step 4: Configure Sync Settings

After connecting, you can configure which data Kosmos syncs:

**Projects** Select the specific Azure DevOps projects you want Kosmos to analyze. Leave the selection empty to sync all projects in your organization.

**Work Item Types** Choose which work item types to include (e.g., Bug, Task, Story, Feature, Epic). By default, all types are synced.

**Additional options:**

* **Sync Comments** — Include work item comments for deeper context in correlations
* **Sync Links** — Include linked work items to surface related issues

Click **Save Settings** when done.

***

### Step 5: Verify the Connection

Once saved, Kosmos begins syncing work items from your Azure DevOps organization.

Navigate to the **Signals** tab to confirm work items are flowing in from your connected organization.

***

### Revoking Access

**From Kosmos:** Settings → Integrations → Azure DevOps → Disconnect

**From Microsoft:** [My Apps](https://myapps.microsoft.com/) → Find the Kosmos app → Remove access, or via your Azure Entra ID admin portal

***

### Data Access

For details on what Kosmos reads from Azure DevOps, see [Integration Permissions](/integration-permissions.md#azure-devops).

All access is **read-only**. Kosmos never creates, updates, or deletes any records in your Azure DevOps organization.

***

**Questions?** Contact <support@kosmoslabs.ai> | [app.kosmoslabs.ai](https://app.kosmoslabs.ai/)

© 2026 Kosmos AI Labs, Inc.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kosmoslabs.ai/connecting-azure-devops.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.