---
title: "Azure DevOps integration for design controls | Qualio"
canonical: "https://www.qualio.com/integrations/azure-devops"
updatedDate: "2026-11-02T11:44:35.000Z"
description: "Design controls from your Azure DevOps work items and Test Plans results. Qualio reads the project you choose, read-only, every hour, and links each test result to its test case and requirement in the trace matrix."
---

# Azure DevOps integration for design controls | Qualio

Design controls from your Azure DevOps work items and Test Plans results. Qualio reads the project you choose, read-only, every hour, and links each test result to its test case and requirement in the trace matrix.

## Requirements and test results from Azure DevOps, traced and controlled in Qualio

Qualio reads the work items and Test Plans results from the project you choose, read-only, and links each result to its test case and requirement.

## What Qualio reads from Azure DevOps

Qualio reads the work item types you choose, with the title, description, state, tags, acceptance criteria and your custom fields, what each links to and a link back to Azure DevOps. A Test Case's steps arrive as a table.

It reads the runs and results from Azure Test Plans, each with its outcome, who last updated it and when, so a result lands on its test case as passed, failed or blocked.

## Connect it with a token and choose the project

Give Qualio your organisation URL and a personal access token. Choose the project, then the work item types and states that count as requirements and test cases. Preview, save, and Qualio reads the project straight away, then every hour.

## One connection, and the trace matrix needs no second test tool

Your requirements and test runs already live in the same tool, so one connection brings both into Qualio, linked to the risks they control.

#### The traceability matrix rebuilds itself on every change

Qualio links each result to its test case and each test to the work item it verifies. An amber mark shows any requirement with no test or test with no result.

#### Your engineers stay in Azure DevOps, and the design controls keep up

Each change to a work item reaches its element on the next read. The element carries Qualio's own control status, and shows the Azure DevOps state beside it only if you map it as a field.

#### Approve the design review and the documentation generates itself

The approvers you name sign the review electronically. On approval the trace matrix, risk file, specifications and test plans generate and export with the test evidence and change history.

## Read-only, and paused the moment the token expires

Comments, attachments, repositories, commits and pull requests stay in Azure DevOps. Qualio reads work items and test results and writes nothing back.

#### If the token expires or is revoked

If the token expires or is revoked, the connection shows as Disconnected on the Integrations page, with a banner, and reads pause until an admin reconnects it.

#### Delete a work item

Delete a work item and Qualio marks it deleted within about six hours; removing it from the design controls is an approval in Qualio. Results already read stay as recorded.

## Read more on integrations and design controls

## Questions about the Azure DevOps integration

### Does our Azure DevOps project have to change?

No. You choose the project and the work item types and states that count, then tell Qualio which level each one is. Qualio reads the project as it is, with no field for you to add. Whatever you leave out stays out.

### Do we need Xray, TestRail or another test tool as well?

Not if your tests are in Azure Test Plans. Qualio reads the test cases and their runs from the same project as the requirements, so one connection builds the trace matrix. A team that also runs TestRail connects it separately, and both read into the same product.

### Who needs a seat?

People who write or approve in Qualio pay: the product manager who signs a review, the person who owns the procedures. Everyone who reads or trains is free. An engineer who works in Azure DevOps needs no seat, because the work items and test runs reach Qualio without the engineer logging in.

### How often does it read, and what does it write back?

It reads the project the moment you save the connection, then every hour, taking only what changed since the last read. It writes nothing to Azure DevOps. The token you create is read-only, and that is all the access Qualio holds.

### What permission does the token need?

Read on work items and read on test management, for a user who can see the project. Qualio stores the token and never shows it back. When it expires or is revoked, an admin pastes in a new one and reads resume.

## See one connection build the trace matrix

See an Azure DevOps project read into Qualio on the demo: work items as requirements, Test Plans runs as results on their test cases, nothing changed in Azure DevOps.