Azure DevOps required reviewers: Automatically included reviewers
The branch policy Automatically included reviewers adds people or groups as reviewers to every pull request into a branch, or only to those that change certain files and folders. Set to Required, the pull request cannot be completed until they approve; set to Optional, they are added and nothing waits for them. It is separate from Require a minimum number of reviewers, which counts approvals from anyone.
Setting it up
In the branch's policies, select + next to Automatically included reviewers and fill in the new reviewer policy (from Microsoft's branch policies page, updated July 15, 2026):
- Reviewers: people and groups.
- Required means every person added must approve, and at least one member of every group added. When the policy names only one group, you can ask for a minimum number of its members instead.
- Files and folders: the paths that bring these reviewers in. Left blank, they are added to every pull request into the branch.
- Allow requestors to approve their own changes: the pull request's creator can approve to satisfy this policy.
- Activity feed message: a note shown in the pull request.
From the command line, az repos policy required-reviewer create takes --required-reviewer-ids, --blocking true for Required, --path-filter, --message, and the branch with --branch-match-type exact or prefix.
Path filters
- A path starts with
/or with a wildcard. One that starts with anything else has no effect: the filter acts as if it was not there. *matches any number of characters, slashes included;?matches one character.*.sqlis every .sql file,/ConsoleApplication/*everything under that folder,*/.gitignoreevery .gitignore.;separates paths, and!takes out what an earlier path brought in, read from left to right:/WebApp/*;!/WebApp/Tests/*is all of /WebApp except its tests, while!/WebApp/Tests/*alone matches nothing.- Paths are not case-sensitive.
The usual surprises
- One of several people should be enough. Adding them one by one makes every one of them required. Put them in a group and add the group: any member's approval then meets the policy.
- Your own approval counts for one policy and not the other. Both this policy and Require a minimum number of reviewers have their own "Allow requestors to approve their own changes". If only this one allows it, your approval satisfies the required reviewers but not the minimum number (more on what does not count).
- A team as a required reviewer. The pull request then asks the group, not you by name, so a search for pull requests with you as the reviewer misses it; here is how to find those.
- Drafts. Required reviewers are not added to a draft; publishing it adds them and evaluates the policies (Azure DevOps draft pull requests).
- Bypass permission. For someone who may bypass policies, a failing policy is only advisory: their approval lets the pull request complete.
Required reviewers in IntelliJ IDEA
Azure DevOps Pull Requests, a plugin by Lesstep for JetBrains IDEs 2024.1 or later and Android Studio, lists the pull requests of Azure DevOps Services and Azure DevOps Server in an IDE tool window. Each pull request's reviewers show who is required, and its branch policies say in words what still waits, such as required reviewers who have not approved, builds and comment resolution. From version 1.0.63, Add reviewers asks more people and teams on a pull request already open, as required or optional reviewers. The review inbox and the branch policies are free; voting, commenting, adding reviewers, completing and creating pull requests are Pro, with a 30-day trial.
Get it on JetBrains Marketplace
Azure DevOps is a trademark of Microsoft Corporation; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with or endorsed by Microsoft or JetBrains.
More: the five votes · why an approval does not count · pull requests assigned to your team · Azure DevOps draft pull requests · Azure DevOps pull request plugins for IntelliJ IDEA, compared · 日本語