Integrations

Azure DevOps + Outcome

Azure DevOps holds your boards, repos and pipelines. Outcome holds the goals they serve. Together, every backlog item sits under a goal, delivery speed is read from your own pipelines, and a decision becomes a new backlog item.

PreviewEngineeringStructureMeasuresWorkWrite-back

What each brings

Azure DevOps brings the facts. Outcome turns them into decisions.

UseFrom Azure DevOpsWhat Outcome does with it
Structure
  • Projects, teams, area paths and iterations
Each goal gets an owner, and each piece of work a team.
Measures
  • Pull requests merged, cycle time and deployments, by week
  • The share of deployments that failed
A goal's number is read on a schedule, with its history.
Work
  • Backlog items, pull requests and deployments
Placed under the goal it serves, so a goal with nothing behind it shows.
Write-back
  • A new backlog item, signed by whoever approved it
A decision becomes an item in the team's own tool, signed by whoever approved it.
Works well with

Azure DevOps + Microsoft Entra ID + Power BI + GitHub Copilot usage + Outcome

What it never reads
  • Source files
  • Pipeline definitions, variables and secrets
  • Changes to anything already in Azure DevOps
Status

Preview Engineering

Live In the product today. Preview Working, refined with customers.

Setting it up

Connected in minutes, by an admin.

  1. 01Open

    An owner or admin opens Settings, Integrations, Azure DevOps.

  2. 02Connect

    Paste: Personal access token.

  3. 03Read

    Outcome reads it on the schedule you set, from the first day.

  4. 04Send

    Work goes to Azure DevOps only when a person approves it.

Full setup guide for customers

Connect Azure DevOps and see what it brings in on the first sync.

Also in engineering Atlassian · GitHub · File import · Sentry · ServiceNow · PagerDuty · GitLab · Linear