{"id":72341,"date":"2026-01-16T11:34:04","date_gmt":"2026-01-16T19:34:04","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/devops\/?p=72341"},"modified":"2026-01-16T11:38:14","modified_gmt":"2026-01-16T19:38:14","slug":"whats-new-with-azure-repos","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/whats-new-with-azure-repos\/","title":{"rendered":"What’s new with Azure Repos?"},"content":{"rendered":"

We thought it was a good time to check in and highlight some of the work happening in Azure Repos. In this post, we\u2019ve covered several recent improvements, along with a preview of features that are coming soon. To stay up to date, be sure to visit the Azure DevOps Roadmap<\/a>.<\/p>\n

These changes have either already been released or are currently rolling out. Be sure to check the sprint release notes for full details.<\/p>\n

Breaking Change: Disabling Obsolete TFVC Check-In Policies<\/h3>\n

Back in April 2025, we shared changes<\/a> to how TFVC check-in policies are stored. These updates affect TFVC projects using policies such as Build (require the last build to succeed), Work Item (require an associated work item), Changeset Comments (require users to add a comment to their check-in), and similar rules.<\/p>\n

Over the past year, we\u2019ve been guiding customers through migrating existing, obsolete policies to the new storage format and preventing the creation of new ones using the old model. With this release, any remaining check-in policies still using the obsolete format will be disabled. These policies will no longer function, and you\u2019ll need to migrate them to the new format for check-in policies to continue working.<\/p>\n

For full details and step-by-step migration guidance, be sure to review our earlier blog post<\/a>.<\/p>\n

Improved Comment Navigation from Pull Request Links<\/h3>\n

We\u2019ve made improvements to how Azure DevOps handles deep links to pull request comments. When opening a pull request from a direct comment link, focus is now handled more reliably, especially for pull requests with a large number of comments.<\/p>\n

This makes it easier to jump directly to the feedback you care about without losing context.<\/p>\n

Pull Request Notification Improvements<\/h3>\n

To help teams better focus on meaningful pull request activity, we\u2019ve updated Azure DevOps email notifications to reduce noise and improve clarity. Several low-value notifications, including draft state changes and auto-complete updates, have been removed entirely.<\/p>\n

For the notifications that remain, we\u2019ve simplified the content to highlight what actually changed, such as affected files, while removing redundant details like full reviewer and commit lists. The result is pull request emails that are easier to scan, more actionable, and better aligned with how teams collaborate during code reviews.<\/p>\n

Pull Request Templates for Multi-Level Branches<\/h3>\n

Pull request templates<\/a> now support nested folder structures that align with multi-level branch names. When you open a pull request targeting a branch like feature\/foo\/december<\/code>, Azure DevOps will look for a matching template in the following order:<\/p>\n

    \n
  1. <pull request template path>\/branches\/feature\/foo\/december.md<\/code><\/li>\n
  2. <pull request template path>\/branches\/feature\/foo.md<\/code><\/li>\n
  3. <pull request template path>\/branches\/feature.md<\/code><\/li>\n<\/ol>\n

    The most specific template available will be applied automatically. This makes it easier to tailor guidance and requirements based on branching conventions without duplicating templates.<\/p>\n

    Azure DevOps MCP Server<\/h3>\n

    If you haven\u2019t checked it out yet, the local Azure DevOps MCP Server<\/a> continues to grow with new tools for working with Azure Repos. It enables you to interact with repositories, branches, commits, and pull requests directly from tools like VS Code and GitHub Copilot.<\/p>\n

    For example, you can fetch repository metadata, list branches, inspect file contents, and explore commit history without navigating the Azure DevOps UI, making it easier to build intelligent tooling and workflows on top of Azure DevOps.<\/p>\n

    For more information, check out the Azure DevOps MCP Server<\/a> repo.<\/p>\n

    \ud83c\udf89 Coming Soon<\/h2>\n

    Improved Git Policy Configuration API<\/h3>\n

    We\u2019re working on improvements to the Git policy configuration APIs to make it easier and more efficient to retrieve all policies that apply to a specific repository. This includes policies defined at the repository level as well as those applied to individual branches or refs.<\/p>\n

    These changes reduce unnecessary API calls and improve performance for services managing policies at scale, while preserving existing policy behavior.<\/p>\n

    Learn more: Policy Configurations \u2013 Get \u2013 REST API (Azure DevOps Git) | Microsoft Learn<\/a><\/p>\n

    More Pull Request Improvements Ahead<\/h3>\n

    We have several pull request improvements planned for upcoming sprints, many of which are driven directly by feedback from the Azure DevOps Community<\/a>. We\u2019re starting with reducing notification noise, as described above, but that\u2019s just the beginning.<\/p>\n

    We\u2019re also working on improvements such as highlighting pull requests with outstanding comments, allowing authors to reset a pull request back to a \u201cready for review\u201d state, and adding the ability to filter pull requests by tags.<\/p>\n

    Together, these changes are focused on making it easier to understand what needs attention and keep reviews moving efficiently.<\/p>\n","protected":false},"excerpt":{"rendered":"

    We thought it was a good time to check in and highlight some of the work happening in Azure Repos. In this post, we\u2019ve covered several recent improvements, along with a preview of features that are coming soon. To stay up to date, be sure to visit the Azure DevOps Roadmap. These changes have either […]<\/p>\n","protected":false},"author":921,"featured_media":72346,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[224],"tags":[],"class_list":["post-72341","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure"],"acf":[],"blog_post_summary":"

    We thought it was a good time to check in and highlight some of the work happening in Azure Repos. In this post, we\u2019ve covered several recent improvements, along with a preview of features that are coming soon. To stay up to date, be sure to visit the Azure DevOps Roadmap. These changes have either […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/72341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/921"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=72341"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/72341\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/72346"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=72341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=72341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=72341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}