Azure DevOps Peer Reviewer Assistant

Last updated: Nov 4, 2026


You connect Azure DevOps one time for each organization, in the SCM connections screen. Then, you select the groups whose pull requests the assistant reviews.

1. Open the SCM connections screen

  1. In your organization, go to Integrations.
  2. Open the SCM connections tab.
  3. Click Connect SCM.

2. Select the provider

The Choose your provider window opens. Click the Azure DevOps card.

Choose your provider window with the Azure DevOps card

3. Examine what the connection adds

The Prepare the connection window shows what Fluid Attacks adds to your Azure DevOps organization. It is not a marketplace extension. Thus, it is not in Organization settings, Extensions.

What the connection addsWhy it needs it
A service principal with Basic accessTo read the code and to publish the result on the pull request
Read of code and contribute to pull requestsTo read the code that the assistant examines and to publish its result
View of all projectsTo list the repositories of the projects that you create later
Two service hook subscriptionsTo know when a user creates or updates a pull request
Prepare the connection window for Azure DevOps

4. Sign in and select the organization

  1. Sign in with the work or school account that administers the organization. This sign-in lists the organizations that your account administers.
  2. Select the organization that you want to connect.

Then, the platform sets up the organization. It adds the service principal, gives it the Git permissions, and creates the subscriptions.

The setup asks Microsoft Entra for a second authorization with more permissions. Entra uses the session that you opened. Thus, you see only one sign-in. If Entra cannot use that session, it shows a second sign-in. This occurs the first time that the directory approves the application.

Window that lists the Azure DevOps organizations to connect

A Connection established message confirms the setup.

5. Select the groups that get reviewed

The connection card has a Pull request review section. This section has one toggle for each group in the organization.

Turn on the toggle of each group that you want the assistant to review. If the toggle of a group is off, the assistant does not review that group, and Azure DevOps shows no result.

Pull request review section with one toggle for each group

The assistant reviews the repositories that this group registered as Git roots. The branch of each root is its registered branch. The assistant compares each pull request with this branch. Refer to Add a new Git repository.

6. Make sure that the connection operates

  1. Open or update a pull request in one of the repositories that you added.
  2. Make sure that the status Peer Reviewer Assistant reports on the pull request.
  3. Make sure that a summary comment appears in the conversation.
Azure DevOps pull request where the Peer Reviewer Assistant starts the review

The assistant publishes three items:

What it publishesWhere you see it
A statusIn the pull request, with the result and a link to the platform
A summary commentIn the conversation of the pull request
A comment on the lineIn the diff, on each line that adds a vulnerability
Summary comment of the Peer Reviewer Assistant on an Azure DevOps pull request
Comment of the Peer Reviewer Assistant on a line of an Azure DevOps diff

Which pull requests the assistant reviews

The assistant reviews a pull request only when all these conditions are true. If one condition is false, Azure DevOps shows no result.

ConditionWhere you set it
The group has pull request review onIntegrations, SCM connections, Pull request review
The repository is a Git root of that groupScope section of the group
That root is ActiveScope section of the group
The group has an active Essential or Advanced planGroup information

Block the merges that disobey your policy

The status alone does not block a merge. To block a merge, add a branch policy on the target branch:

  1. Open a pull request. Azure DevOps shows a status in the list only after it receives that status one time.
  2. Open the branch policies of the target branch: Repos, Branches, the More options icon of the branch, Branch policies. You can also go to the same screen from Project settings, Repository, Policies, Branch Policies, and the branch.
  3. Below Status checks, select +.
  4. In Status to check, select fluidattacks/peer-reviewer-assistant. If this status is not in the list, write it.
  5. Set Policy requirement to Required.
Branch policy of Azure DevOps with the Peer Reviewer Assistant status as required

For more information about this mechanism, refer to the Microsoft documentation: Set and manage branch policies.

Manage the connection

The connection card has these controls:

ControlWhat it does
StatusShows Connected or Suspended
Verify againExamines the connection again
DisconnectRemoves the service principal and the subscriptions from the Azure DevOps organization

On this page