> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure DevOps on Vortex IQ

> Monitor Azure DevOps health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Azure DevOps health, cost and reliability signals, and catch incidents and runaway spend early.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=azure-devops)

<CardGroup cols={5}>
  <Card title="24">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="0">
    prepared fixes
  </Card>

  <Card title="0">
    proven workflows
  </Card>

  <Card title="836">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                         |
        | ----------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Build Duration**              | Watch only         | Average of (finishTime - startTime) in milliseconds across status=completed builds queued within the last 30d.                         |
        | **Avg Commits / Active Repo (30d)** | Watch only         | 30d commit count / count of scanned repos with at least 1 commit in 30d; concentration of delivery across the fleet.                   |
        | **Build Failure Rate Alert**        | Alert band 95 / 80 | Build success rate (result=succeeded / completed) queued within 30d; fires when it crosses the vc\_ci\_pass\_rate band (bad at \<80%). |
        | **Build Success Rate (30d)**        | Alert band 95 / 80 | Builds with result=succeeded / all completed builds (status=completed) queued within 30d, x100, across the top 10 scanned projects.    |
        | **Builds (30d)**                    | Watch only         | Count of builds queued within the last 30d from GET .../build/builds across the top 10 scanned projects.                               |
        | **Commits by Repository**           | Watch only         | Commits in the last 30d grouped by repo full name (project/name), top 10 by count.                                                     |
        | **Median Open PR Age**              | Alert band 3 / 14  | Median of (now - creationDate) in days across all status=active pull requests; drives vc\_pr\_age\_days (lower is better).             |
        | **Most Active Repo (30d)**          | Watch only         | The scanned repo with the most commits in the last 30d; value = commit count, detail = repo full name (project/name).                  |
        | **Open PRs by Repository**          | Watch only         | Open (status=active) pull requests grouped by repo full name (project/name), top 10 by count.                                          |
        | **PR Age Alert**                    | Alert band 3 / 14  | Median open-PR age in days; fires when it crosses the vc\_pr\_age\_days band (bad at >14d).                                            |
        | **Repositories by Project**         | Watch only         | Scanned repositories grouped by their parent project name, top 10 by count.                                                            |
        | **Stale PRs (>14d)**                | Watch only         | Count of status=active pull requests whose age (now - creationDate) exceeds 14 days.                                                   |
      </Accordion>

      <Accordion title="Grow revenue (6 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                                                                                           |
        | ------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Commits (30d)**         | Alert band 0 / -50 | Count of commits from GET .../repositories/{repositoryId}/commits (author.date within 30d) summed across the top 15 scanned repos; change\_pct vs the p  |
        | **Completed PRs (30d)**   | Watch only         | Count of pull requests with status=completed and closedDate within the last 30d (searchCriteria.status=completed) across the top 15 scanned repos.       |
        | **Deploy Cadence Trend**  | Alert band 0 / -50 | Daily commit count over the last 30d (author.date), summed across the top 15 scanned repos; value = 30d total, change\_pct vs the prior 30d drives vc\_d |
        | **Deploy Stall Alert**    | Alert band 0 / -50 | Commit-count change\_pct vs the prior 30d; fires on a stall per the vc\_deploy\_cadence band.                                                            |
        | **Open Pull Requests**    | Watch only         | Count of pull requests with status=active from GET .../pullrequests?searchCriteria.status=active across the top 15 scanned repos.                        |
        | **Pipeline Health Score** | Alert band 90 / 70 | 0-100 composite = 0.4 x build success rate (30d, result=succeeded / completed) + 0.3 x PR-age score (100 at \<=3d median open-PR age, 0 at >=14d)        |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                    | Alert behaviour | What it tracks                                                                                                                                     |
        | ------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned PRs (30d)**   | Watch only      | Count of pull requests with status=abandoned and closedDate within the last 30d (searchCriteria.status=abandoned) across the top 15 scanned repos. |
        | **Canceled Builds (30d)** | Watch only      | Count of builds with result=canceled, queued within the last 30d, across the top 10 scanned projects.                                              |
        | **Failed Builds (30d)**   | Watch only      | Count of builds with result=failed and status=completed, queued within the last 30d, across the top 10 scanned projects.                           |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                                                          |
        | ----------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------- |
        | **Daily Commits Trend** | Watch only      | Commits grouped by day over the last 30d (author.date), summed across the top 15 scanned repos.                         |
        | **Projects**            | Watch only      | Count of projects returned by GET /{organization}/\_apis/projects (state=wellFormed).                                   |
        | **Repositories**        | Watch only      | Count of repositories returned by GET .../{project}/\_apis/git/repositories, summed across the top 10 scanned projects. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="CI pass rate below 80%">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 CI runs is failing. At this rate, a genuinely broken change is more likely to slip through unnoticed (lost in the normal noise of failures) and developers waste time re-running or diagnosing failures that have nothing to do with their own change, slowing the whole team down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CI-001`
      </Accordion>

      <Accordion title="Delivery cadence dropped more than 50% vs the prior period">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Deploys or merges have dropped by more than half compared to the prior period. That usually means fixes and improvements, including fixes for issues this same audit has flagged elsewhere, are not shipping, which slows the whole team's ability to respond to anything urgent.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CADENCE-001`
      </Accordion>

      <Accordion title="Median open pull-request age above 14 days">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Half of open pull requests have been waiting more than two weeks. Work that is done but not merged is not delivering any value yet, and the longer a PR sits open, the more it tends to drift from the main branch, making it harder to merge later than it would have been today.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-PR-001`
      </Accordion>
    </AccordionGroup>

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **420 read** and **416 write** operations across apidashboarddashboardwidgets, apigitrepositorypullrequestreviewers, apiserviceendpointendpoints, apisymbolrequests, apiauditstreams, apibuildbuilds on Azure DevOps. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=azure-devops)

    #### Ready to build your first Azure DevOps workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource                             | Read operations | Write operations |
      | ------------------------------------ | --------------- | ---------------- |
      | apidashboarddashboardwidgets         | 2               | 6                |
      | apigitrepositorypullrequestreviewers | 2               | 6                |
      | apiserviceendpointendpoints          | 2               | 6                |
      | apisymbolrequests                    | 2               | 6                |
      | apiauditstreams                      | 2               | 4                |
      | apibuildbuilds                       | 2               | 4                |
      | apibuilddefinitions                  | 2               | 4                |
      | apidashboarddashboards               | 2               | 4                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>