Pacia Intelligence

Code integration

Azure DevOps and Pacia

Azure DevOps connects with a Code (Read) personal access token and nothing else — no application registration, no tenant admin consent. Its pull requests are normalised into exactly the same shape as GitHub’s, so a mixed-provider organisation compares like with like.

Talk to us

What Pacia reads from Azure DevOps

  • Pull requests, reviewers, comments and completions

  • Repository and project metadata

  • Build and release signals where available

Connecting it

  1. Create a PAT in Azure DevOps 2 min

    User Settings → Personal Access Tokens → create one with the Code (Read) scope.

  2. Paste it into Pacia 1 min

    Connect Azure DevOps via Access Token, supplying organisation, project, repository and token.

  3. Let the backfill run ~15 min

    Up to 180 days of pull request history pages through per repository.

Limits, stated up front

Every integration page on this site lists what the integration does not do. Finding that out during a trial is worse for both of us than finding it out now.

  • No live webhooks in this phase — repositories refresh on a 20-minute reconcile cycle or on demand.

  • Sign in with Azure DevOps exists but is an unverified OAuth flow; GitHub sign-in is the guaranteed path.

  • The token is encrypted at rest and never returned in any API response.

What this unlocks

Connect Azure DevOps and see your own data

Talk to us