DevOps & Code

Connect Azure DevOps

Reads Azure DevOps Boards, Repos, and Pipelines — work-item throughput & lead time, build/deployment frequency, change-failure rate, and repository staleness, CI coverage, and branch-policy coverage — to compute Delivery Health and Technical Debt from real data.

What you'll need

Your Azure DevOps organization name (the dev.azure.com/<org> segment — not a project), and a read-only Personal Access Token with Custom-defined Read scopes for Code, Build, Work Items, and Project & Team. Optionally scope the sync to a single project.

Credential

Personal Access Token (read-only)

Requested scopes

Code (read), Build (read), Work Items (read), Project & Team (read)

Powers

Delivery Health, Technical Debt

What it pulls

Organization + projects, Git repositories, completed builds over the last 30 days (deployment frequency + change-failure rate), and Boards work items (30-day throughput, created→closed lead time, open/aging) for Delivery Health; plus, across a repository sample, latest-commit staleness (legacy-code debt), build-pipeline coverage (test debt), and branch-policy coverage (architecture debt) for Technical Debt.

What you’ll enter

The exact fields the connect form asks for — and where to find each value.

Organization
The “your-org” part of the dev.azure.com/your-org web address (your organization, not a project).
Personal Access Token
dev.azure.com/<org>/_usersSettings/tokens → New Token → Custom defined → Read for Code, Build, Work Items, Project & Team → copy it (shown once).
Project (optional — limits the sync to one project)
Leave blank to sync the whole organization; set a project name to limit the sync to just that project.

Step-by-step setup

  1. 1

    Find your organization name

    Sign in at dev.azure.com — the URL shows dev.azure.com/<your-org>. That <your-org> segment is your Organization (NOT a project name). No org yet? Create one there first.

  2. 2

    Open the tokens page directly

    Go to https://dev.azure.com/<your-org>/_usersSettings/tokens (replace <your-org>) to land straight on Personal Access Tokens.

  3. 3

    Create a token with Custom scopes

    New Token → name it “ShipReady Metrics”, pick your organization, set an expiration, then switch the scope view from Recommended to “Custom defined”.

  4. 4

    Grant read-only scopes

    Under Custom defined, check Read for Code, Build, Work Items, and Project & Team. Leave everything else unchecked.

  5. 5

    Create + copy, then connect

    Click Create and copy the Personal Access Token now (shown once). Back here: put your org (dev.azure.com/<org> or just the name) in Organization, paste the token into Personal Access Token, optionally set a single Project, and click Connect.

Create a Personal Access Token → Connect in the app

Read-only PAT over Basic auth — validated live against Azure DevOps, encrypted at rest, then synced into Delivery Health (lead time + deployment frequency + change-failure rate) and Technical Debt (legacy-code, test, and architecture debt from repo/pipeline/policy signals). Mocked-fetch tested; connect a real PAT to verify ingestion.