# Azure Repos

Repository collaboration with branch policies inside an existing Azure DevOps workflow.

ID: azure-repos
Language: en
Revision: 1
Translation source revision: 1
Canonical: https://kickoff.jujin.dev/en/catalog/azure-repos/

## Why: the goal or problem

A facilities app lets employees reserve meeting rooms. Its team already uses Azure DevOps and wants room-conflict fixes reviewed before entering main. Keeping that project’s permissions and checks together favors its repository service.

## How: work toward a solution

Push a Git branch and open a pull request. In this example, main requires reviewer approval and build validation. A failed booking test holds up completion; after a fix, required checks and review permit merging.

## What: the concept

Azure Repos provides repositories in Azure DevOps. These are configured Git branch policies, not automatic guarantees. Bypass permissions matter. Azure Repos also supports TFVC; hosting code here does not require running the app on Azure.

[Source](https://learn.microsoft.com/en-us/azure/devops/repos/get-started/what-is-repos?view=azure-devops)

---

# Go further

Optional reading · separate from the overview

## Selection & comparison

Choose Azure Repos when existing Azure DevOps projects, permissions and review practices reduce coordination work. Bitbucket may fit an established Jira workflow; other hosts also offer protected-branch checks. Compare operator, integrations, plan constraints and migration needs rather than assuming repository hosting determines runtime hosting.

## Applications

The facilities team configures a minimum reviewer count and required build validation for main. The example PR waits while a room-conflict test fails. After a fix, the reviewer checks the new result before completing the PR. This walkthrough uses Git, not the separate TFVC model.

## Implementation & cautions

Inspect which policies are required, how approvals reset after changes and who can bypass checks. A passing build does not prove every booking rule. Azure Repos also offers centralized TFVC for existing workflows; do not apply the Git diagram to it. Recheck current access and service limits, and rehearse migration of reviews and policies separately from Git history.

## Evidence

- [Microsoft: What is Azure Repos?](https://learn.microsoft.com/en-us/azure/devops/repos/get-started/what-is-repos?view=azure-devops) — Azure Repos supports Git and TFVC; Git repositories support PRs. (Checked: 2026-09-27)
- [Microsoft: Branch policies](https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops) — Configured branch policies can require reviewers and build validation; bypass permissions matter. (Checked: 2026-09-27)