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.
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.
| Scope | Unlocks |
|---|---|
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
dev.azure.com/<organization>.Repository full names are project/repository. Azure DevOps connects with a
token only; there is no sign-in button.
Resources
| Resource | Available | Notes |
|---|---|---|
repositories | Yes | Every Git repository in the organization that the token can read |
commits | Yes | The default branch, or the branch you choose, in the date range |
pull_requests | Yes | Active, completed (merged) and abandoned (closed) |
issues | Yes | The project's work items, of every type; type is the work item type |
releases | No | Azure Repos has no release objects: read tags instead |
tags | Yes | |
branches | Yes | |
contributors | From commits | Commits in the date range, counted per author e-mail |
pipeline_runs | Yes | The 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
| Resource | Empty columns |
|---|---|
repositories | description, archived, language, stars, forks, open_issues, created_at, updated_at, pushed_at |
commits | author_login, parents, additions, deletions |
pull_requests | author_login, updated_at, additions, deletions, changed_files, comments |
issues | author_login, assignee_login |
tags | tagged_at |
branches | protected |
contributors | login |
pipeline_runs | run_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
| Response | Code | Cause | What to do |
|---|---|---|---|
| 401, or a sign-in page | PROVIDER_ACCESS_DENIED, stage auth | The token expired, was revoked or mistyped, belongs to another organization, or is a global token after 2027-01-27 | Create an organization-scoped token for this organization and choose Replace configuration |
| 403 | PROVIDER_ACCESS_DENIED, stage permissions | A scope is missing. details.missingScopes names it, for example Work Items (Read) | Edit the token's scopes in Personal access tokens, then test again |
| 404 | NOT_FOUND | The organization, project or repository does not exist, or the token cannot see it | Check the organization name and the full name project/repository |
| Redirect | NOT_FOUND | The repository moved or was renamed | Select the repository under its new name |
| 429 | RATE_LIMITED | Usage is over the limit | Retry after details.retryAt; scheduled refreshes wait by themselves |
| — | VALIDATION_FAILED | releases was chosen | Read tags instead |