> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Azure DevOps as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/azure-devops

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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`

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

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

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](https://posthog.com/docs/data-pipelines/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 | — |
| `build_definitions` | A build pipeline definition — the configuration a build run is produced from. | Full refresh | — | — |
| `build_timeline_records` | One record in a build's timeline — a stage, phase, job or task, with its own timing and result. | Incremental, Full refresh | build\_finish\_time | — |
| `pipelines` | A YAML pipeline defined in an Azure DevOps project. | Full refresh | — | — |
| `pipeline_runs` | A run of a YAML pipeline, with its state, result and timings. | Full refresh | — | — |
| `pull_requests` | A Git pull request in Azure DevOps. | Incremental, Full refresh | creationDate | — |
| `commits` | A Git commit reachable from a repository in an Azure DevOps project. | Incremental, Full refresh | committer\_date | — |
| `pull_request_threads` | A comment thread on a pull request, covering both reviewer discussion and the system events Azure DevOps records as threads (votes, reviewer changes, merge attempts). | Full refresh | — | — |
| `pull_request_thread_comments` | A single comment inside a pull request comment thread. | Full refresh | — | — |
| `pull_request_reviewers` | A reviewer on a pull request, with their approval vote. | Full refresh | — | — |
| `pull_request_work_items` | A link between a pull request and a work item it resolves or references. | Full refresh | — | — |
| `teams` | A team in an Azure DevOps project. | Full refresh | — | — |
| `team_members` | Membership of a team, one row per member. | Full refresh | — | — |
| `work_item_revisions` | A historical revision of a work item, from the reporting (append-only) feed. | Incremental, Full refresh | changed\_date | — |
| `work_item_types` | A work item type defined by a project's process, such as Bug, Task or User Story. | Full refresh | — | — |
| `work_item_type_states` | A state a work item type can be in, with the state category that groups it. | Full refresh | — | — |
| `work_item_classification_nodes` | One node of a project's area or iteration tree, resolving the area and iteration paths on work items. | Full refresh | — | — |
| `work_iterations` | An iteration (sprint) a team is subscribed to, with its dates and relative timeframe. | Full refresh | — | — |
| `releases` | A classic release created from a release pipeline definition. | Full refresh | — | — |
| `release_deployments` | One deployment of a release to an environment — the grain for deployment frequency and promotion history. | Incremental, Full refresh | lastModifiedOn | — |
| `test_runs` | A test run published against a build or release, with its pass and fail counts. | Incremental, Full refresh | lastUpdatedDate | — |

## Troubleshooting

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/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.