Docs
Connections

Azure DevOps

Connect Azure DevOps Services with an organization-scoped read-only personal access token and read Azure Repos, pull requests, work items and Azure Pipelines builds.

An Azure DevOps connection reads one organization's Azure Repos, pull requests, work items and pipeline builds with a personal access token (PAT) that has read scopes only. It calls only dev.azure.com. Azure DevOps Server is not supported. For the tables, columns and limits that every forge shares, see the Git overview.

Preview

Git connections are in Preview and are enabled on request: contact support@xentropy.ai. Until Azure DevOps is enabled for your account it is not offered in the forge selector, and its reads fail with PROVIDER_DISABLED.

Create a read-only token

Create an organization-scoped token. Global tokens, created with All accessible organizations, stop working on 2027-01-27, so do not use one.

In Azure DevOps, open User settings → Personal access tokens and choose New Token.
Name the token. Under Organization, choose your organization, not All accessible organizations. Set an expiration date.
Under Scopes, choose Custom defined, then select Read for the scopes in the table below. Leave everything else unselected.
Create the token and copy it. Azure DevOps shows it only once.

Your organization's administrators can restrict who may create tokens, or limit their scope and lifetime. If New Token is missing or a scope cannot be chosen, ask them.

Token permissions

The form lists these scopes with a copy button.

ScopeUnlocks
Code (Read)Repositories, commits, pull requests, tags, branches and contributors
Work Items (Read)Work items (issues)
Build (Read)Pipeline builds (pipeline_runs)
Project and Team (Read)The organization's projects, for the connection test

Set up the connection

Open Connections, choose New connection, then Git, and choose Azure DevOps.
Name the connection and enter the Organization: the name in dev.azure.com/<organization>.
Paste the token and choose Test connection. The stages are Authentication (the token) and Repository access. The test lists the repositories of every project the token can read.
Choose the repositories to allow, or none to allow every repository the token can read. Choose Save connection.
Open the connection, choose a resource, repositories and a date range, pick fields, preview 100 rows and save a dataset.

Repository full names are project/repository. Azure DevOps connects with a token only; there is no sign-in button.

Resources

ResourceAvailableNotes
repositoriesYesEvery Git repository in the organization that the token can read
commitsYesThe default branch, or the branch you choose, in the date range
pull_requestsYesActive, completed (merged) and abandoned (closed)
issuesYesThe project's work items, of every type; type is the work item type
releasesNoAzure Repos has no release objects: read tags instead
tagsYes
branchesYes
contributorsFrom commitsCommits in the date range, counted per author e-mail
pipeline_runsYesThe project's builds of this repository

Work items belong to a project, not to a repository, so two repositories of the same project show the same work items. A project with 20,000 or more work items in the date range fails with INCOMPLETE_DATA: narrow the range. Choosing releases fails with VALIDATION_FAILED before any request is sent.

Columns left empty

ResourceEmpty columns
repositoriesdescription, archived, language, stars, forks, open_issues, created_at, updated_at, pushed_at
commitsauthor_login, parents, additions, deletions
pull_requestsauthor_login, updated_at, additions, deletions, changed_files, comments
issuesauthor_login, assignee_login
tagstagged_at
branchesprotected
contributorslogin
pipeline_runsrun_number, actor_login

Azure DevOps identities have no login handle, so login columns are empty and contributors are grouped by e-mail. Author names and e-mails are personal data, off by default. The build number is a format string, kept in extra.

Limits

Azure DevOps meters each user's API use over a sliding five-minute window. It first slows requests down, then answers 429 (TF400733), and sends Retry-After, sometimes on successful responses too. Xentropy honours it. See Limits and refresh for pages, rows and deadlines.

Errors

ResponseCodeCauseWhat to do
401, or a sign-in pagePROVIDER_ACCESS_DENIED, stage authThe token expired, was revoked or mistyped, belongs to another organization, or is a global token after 2027-01-27Create an organization-scoped token for this organization and choose Replace configuration
403PROVIDER_ACCESS_DENIED, stage permissionsA scope is missing. details.missingScopes names it, for example Work Items (Read)Edit the token's scopes in Personal access tokens, then test again
404NOT_FOUNDThe organization, project or repository does not exist, or the token cannot see itCheck the organization name and the full name project/repository
RedirectNOT_FOUNDThe repository moved or was renamedSelect the repository under its new name
429RATE_LIMITEDUsage is over the limitRetry after details.retryAt; scheduled refreshes wait by themselves
—VALIDATION_FAILEDreleases was chosenRead tags instead

On this page