# Linking Azure DevOps as a source - Docs

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

[Learn more](/wizard.md)

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The Azure DevOps connector syncs your project, build, and work item data into PostHog, so you can analyze your engineering activity alongside your product data.

## Prerequisites

You need an Azure DevOps organization and a personal access token with read scopes for the data you want to sync.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Azure DevOps, you'll need:

-   **Organization** – the first path segment of your Azure DevOps URL. For `dev.azure.com/myorg`, enter `myorg`.
-   **Personal access token** – create one under **User settings → Personal access tokens** with read scopes for the data you want to sync (Work Items, Code, Build, and Project and Team).

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| Organization | text | Yes |
| Personal access token | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| projects | A team project in the Azure DevOps organization — a container for repos, builds, and work items. | Full refresh | — | — |
| repositories | A Git repository within an Azure DevOps project. | Full refresh | — | — |
| builds | A build run produced by a build pipeline in Azure DevOps. | Incremental, Full refresh | queueTime | — |
| pull_requests | A Git pull request in Azure DevOps. | Incremental, Full refresh | creationDate | — |
| work_item_revisions | A historical revision of a work item, from the reporting (append-only) feed. | Incremental, Full refresh | changed_date | — |

## Troubleshooting

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better