---
title: "Azure DevOps - Boards"
description: "Baz's Azure DevOps Boards Integration"
---

By pulling in work item information like titles, descriptions, types, acceptance criteria, and stakeholder comments, Baz ensures that every change request is grounded in intent. Reviewers no longer need to switch between Azure DevOps Boards and GitHub to understand why a change exists - they get the full context, right where the code is.

Baz uses this context to:

* Enrich AI-generated summaries and topics with business objectives.
* Tailor prompts to reflect the goals and constraints from the Boards ticket.
* Help reviewers focus on what’s important by aligning code changes to the original intent.

<figure><img src="/docs/docs-assets/screenshot-2025-12-18-at-15-49-44.png" alt="" width="704" height="441"><figcaption>Configure Azure DevOps Boards integration</figcaption></figure>

## **Configuring Baz & Azure DevOps Boards**

To enable Azure DevOps Boards support:

1. Go to the **Azure DevOps integration** located in Settings > Integrations.
2. Click **Configure** and follow the authentication flow.
3. Once connected to your Azure DevOps organization, Baz will automatically attach ticket context to linked change requests.

> **Tip:**\
> Baz detects relevant work items when the branch name includes a work item ID (e.g. `AB#12345`), or when the PR description contains a link to an ADO Boards work item.

## **How Baz Uses Azure DevOps Boards Work Item Data**

When connected, Baz pulls:

* **Work item title and description** - used to inform review summaries and reasoning.
* **Work item type** (feature, bug, task) - guides reviewer expectations.
* **Acceptance criteria** - injected directly into prompts for better validation.
* **Comments and discussion threads** - used to provide full context in reviews.

This information flows into all Baz workflows:

* Summaries reflect the purpose and constraints defined in the work item.
* Break down topics based on feature or flow relevance.
* Guide reviewers to evaluate changes through the lens of what the ticket was designed to accomplish.

## FAQ

<details>

<summary>How does Baz know which Azure DevOps Boards item a change relates to?</summary>

From a work item ID in the branch name, for example `AB#12345`, or a link to the work item in the pull request description.

</details>

<details>

<summary>What does Baz read from Azure DevOps Boards?</summary>

Work item title and description, work item type, acceptance criteria, and comments and discussion threads.

</details>

<details>

<summary>Does connecting it change what reviewers see in the code host?</summary>

Yes, in the sense that the review itself gets richer: summaries, topics, and agent prompts carry the intent from Azure DevOps Boards, so reviewers do not have to open the tracker to understand why a change exists.

</details>

<details>

<summary>Nothing is attached to my pull request, what should I check?</summary>

Check that the integration is connected under Settings, Integrations, that the branch name or pull request description carries a recognizable identifier, and that the connected account can see the item in Azure DevOps Boards.

</details>