Skip to main content
Connectors

Connecting Azure DevOps

Authorize Azure DevOps, select client-approved projects, and bring read-only repository, work-item and build summaries into the relevant claim.

ReviewedAugust 22, 2026

ForClient portal users and claim preparers

Find itClient portal → Connect; consultant Client → Collaboration

The Azure DevOps connector uses Microsoft Entra OAuth and read-only scopes. A client chooses the organization and projects before anything is brought into a claim.

Connect an organization

  1. The client signs in to their SREDlog portal, opens Connect, chooses Azure DevOps, and completes Microsoft authorization.
  2. After returning to SREDlog, choose the Azure DevOps organization if prompted.
  3. Choose Share Projects, select the projects the consultant may access, and save the shared-access list.
  4. The consultant opens the client's Collaboration tab, opens Projects, maps each approved project, sets the activity window, and chooses Save & sync.

What enters SREDlog

SREDlog retrieves commit messages, contributor activity, changed work items, and build results for approved projects and the selected period. It does not store source-code contents or change repositories, work items, or builds.

Disconnect or troubleshoot

If an organization or project does not appear, confirm the Microsoft identity can see it directly in Azure DevOps, then repeat the organization or project-sharing step. Use Sync in Connected sources to refresh evidence. Disconnect and revoke the Microsoft grant to stop access.

See the Azure DevOps setup steps and data boundary.

Was this helpful?

Tell us what was missing and we’ll improve this guide.

Send feedback