Azure DevOps

About Azure DevOps

Azure DevOps is Microsoft's cloud-based software development platform for teams that want planning, source control, continuous integration and delivery, testing, package feeds and project collaboration in one service. Its core services are Azure Boards, Azure Repos, Azure Pipelines, Azure Test Plans and Azure Artifacts. It can support software delivered to Azure, other clouds or on-premises environments, so the main buyer question is not whether it works with Azure, but whether its integrated workflow, authentication model and licensing fit the team's existing Git, CI/CD and project-management choices. Pricing, security and migration guidance on this page was checked against Microsoft sources on September 5, 2026.

What is included in Azure DevOps?

Azure DevOps combines several services that teams can adopt together or use selectively. Azure Boards handles work items, backlogs, sprint planning and Kanban-style tracking. Azure Repos provides private Git repositories and Team Foundation Version Control for organizations that still require it. Azure Pipelines provides continuous integration and deployment. Azure Test Plans adds manual and exploratory testing capabilities, while Azure Artifacts hosts packages and supports upstream sources.

The platform also includes dashboards, wikis, service hooks, notifications, auditing and reporting capabilities that connect planning, code and delivery activity. That traceability can be useful for teams that want work items, commits, pull requests, builds, releases and tests linked inside one system rather than spread across unrelated tools.

How does Azure DevOps pricing work in 2026?

Microsoft currently gives each Azure DevOps organization five Basic users at no charge. Additional Basic users are listed at $6 per user per month, while Basic + Test Plans is listed at $52 per user per month. Visual Studio subscribers and eligible GitHub Enterprise users can receive Azure DevOps access under Microsoft's current licensing rules without consuming the five free Basic-user slots.

Azure Pipelines includes one free Microsoft-hosted parallel job with 1,800 minutes per month and one free self-hosted parallel job with unlimited minutes. Extra Microsoft-hosted parallel jobs are currently listed at $40 per month and extra self-hosted parallel jobs at $15 per month. Azure Artifacts includes 2 GiB per organization before usage-based storage charges apply. Microsoft also currently lists GitHub Code Security for Azure DevOps at $30 per committer per month and Secret Protection at $19 per committer per month. Buyers should still check the live pricing page before purchase because currency, agreement type and billing program can affect the final amount.

What are Azure Boards, Repos and Pipelines best for?

Azure Boards is strongest when engineering teams want backlog, sprint, bug and task tracking tied directly to code and delivery data. It supports customizable work items, boards, backlogs and planning views. Azure Repos is useful for organizations that want Microsoft-hosted private Git repositories with branch policies, pull requests and enterprise permissions, or that still need Team Foundation Version Control.

Azure Pipelines can build and deploy applications across Windows, Linux and macOS agents and can target Azure, other public clouds and on-premises environments. Teams can define pipelines with YAML and use approvals, environments and release controls. This makes Azure DevOps relevant even when the runtime is not hosted on Azure.

What changed for large Azure Repos in 2026?

Microsoft removed the previous hard limit of 100 million Git objects per Azure Repos repository in the Sprint 273 update. That change matters for long-lived monorepos and very large codebases because repository growth is no longer constrained by that specific object-count ceiling.

Removing the hard object-count limit does not mean every repository operation is unlimited or equally fast. Large repositories still need practical Git hygiene, branch and history management, and appropriate client and pipeline design. The change is best read as a scalability improvement rather than a promise that repository size no longer affects performance.

What authentication changes matter before December 2026?

Microsoft is retiring Global Personal Access Tokens in Azure DevOps Services because one global PAT can grant access across every Azure DevOps organization a user can reach. Microsoft now recommends organization-scoped PATs where PATs are still required, or Microsoft Entra based authentication for stronger governance.

Microsoft's current retirement schedule says existing global PATs stop working on December 1, 2026. Microsoft had previously planned to block creation and regeneration on March 15, 2026, but that step was cancelled, so organizations can still create global PATs until the final December 1 retirement. Teams should inventory scripts, local tools and integrations that depend on global PATs before that date and migrate them rather than assuming an old token will continue working.

What is changing for workload identity federation service connections?

Azure DevOps is also moving workload identity federation service connections away from the older Azure DevOps issuer that uses the https://vstoken.dev.azure.com prefix. Microsoft deprecated that issuer on July 1, 2026 for affected public-cloud service connections and has used the Microsoft Entra issuer by default for new service connections since November 2025.

Existing affected service connections can continue during the transition period, but Microsoft plans to retire the Azure DevOps issuer on July 1, 2027. The deprecation applies to Azure public cloud service connections that use single-tenant Microsoft Entra applications or managed identities. Microsoft explicitly excludes service connections targeting non-public clouds and those using multi-tenant applications from this specific retirement announcement. Teams should use warnings in the service connection UI and pipeline runs to identify connections that need migration.

Does Azure DevOps support MCP and AI agents?

Microsoft made the Remote Azure DevOps MCP Server generally available on August 5, 2026. It provides a hosted MCP endpoint so supported AI assistants can securely access selected Azure DevOps capabilities without teams having to operate a local MCP server.

Microsoft says the remote MCP server can expose Azure DevOps work items, repositories, pipelines and other supported project context to AI-assisted workflows. Teams should still apply normal Azure DevOps identity, permission and auditing controls rather than treating an agent connection as a trusted administrative shortcut.

What AI features are available for Azure Repos?

Microsoft announced GitHub Copilot Code Review for Azure Repos as a public preview on August 26, 2026. Azure DevOps customers using the service can enable the preview for supported repositories and use Copilot-assisted pull request review. Because it is still a preview, organizations that have strict production, compliance or support requirements should evaluate the preview terms before making it part of a required review gate.

On August 27, 2026 Microsoft also released an Azure DevOps plugin for the GitHub Copilot app. The initial release can show assigned work items and pull requests, open and edit work items and pull requests, and complete pull requests from the Copilot app. Microsoft describes the extension as early-stage and currently limited, so buyers should treat it as an integration convenience rather than a replacement for the full Azure DevOps web experience.

How can enterprises migrate Azure Repos to GitHub?

Microsoft expanded Enterprise Live Migrations to public preview on August 31, 2026 for organizations moving Azure Repos repositories to GitHub Enterprise Cloud with data residency. The migration starts while the Azure DevOps repository remains available, continuously synchronizes changes in the background, and then performs a final cutover. Microsoft says the final downtime is typically less than 30 minutes for most repositories.

Enterprise Live Migrations currently supports repositories, commit history, branches, tags, pull request metadata, comments, user history and conversion of branch policies to GitHub rulesets. It does not currently migrate Azure Boards work items, pipeline definitions, releases, wikis, test artifacts or Azure Artifacts. Microsoft also states that this preview currently targets GitHub Enterprise Cloud with data residency on ghe.com, not standard GitHub Enterprise Cloud on github.com.

This creates a practical hybrid path. Teams can move source control to GitHub while continuing to use Azure Boards, Azure Pipelines and other Azure DevOps services. Buyers considering a platform change should therefore compare complete workflow migration with a phased repository-first approach rather than assuming all Azure DevOps services must move together.

How do testing and package management work?

Azure Test Plans is the paid testing component for teams that need managed manual test cases, test plans, exploratory testing and centralized test reporting. Basic access includes some test execution capabilities, but the full Test Plans experience requires the higher access level. Teams should confirm which testers need the paid license instead of assigning it broadly.

Azure Artifacts provides feeds for package formats including NuGet, npm, Maven and Python packages. It can connect to upstream public sources and can be used from Azure Pipelines or other build systems. Storage beyond the included allowance is billed separately, so organizations with large package histories should use retention policies and monitor feed growth.

How does Azure DevOps compare with GitHub?

Azure DevOps and GitHub overlap in source control, automation and developer collaboration, but their center of gravity differs. Azure DevOps has mature integrated work tracking through Boards, enterprise testing through Test Plans and a long history with Microsoft enterprise development workflows. GitHub centers development around GitHub repositories, pull requests, Actions and a broader AI-assisted developer ecosystem.

Microsoft is actively making hybrid use easier. Teams can keep Azure Boards and Azure Pipelines while moving repositories to GitHub, and current migration tooling reflects that direction. Organizations should avoid running duplicate repositories, pipelines and work tracking without a clear ownership model because overlapping systems can increase governance and administrative effort.

What should enterprises know about administration and security?

Azure DevOps organizations use Microsoft Entra ID integration, project and organization permissions, access levels and service connections to control who can see and change development resources. Administrators should design permissions around least privilege and pay particular attention to pipeline identities, service connections, secrets, protected branches, PAT policies and production approvals.

Microsoft has continued moving Azure DevOps toward Microsoft Entra based authentication. The 2026 PAT and workload identity changes are part of that direction. Administrators should prefer short-lived and narrowly scoped credentials, review audit events, remove stale integrations and avoid broad build or service identities when a narrowly permissioned service principal or managed identity can do the job.

What are the main limitations and tradeoffs?

Azure DevOps can feel broad for teams that only need Git hosting or a simple CI service. Its organization, project, team, permission, agent and service-connection concepts add administration that small teams may not need. Pricing is also spread across users, test access, parallel pipeline jobs, artifact storage and optional security capabilities rather than one simple platform fee.

Authentication changes can create migration work for older automation. Global PAT retirement, legacy OAuth changes and workload identity issuer migration all require administrators to find dependencies before deadlines. New AI and migration capabilities also include previews, so production teams should separate generally available features from preview functions when setting support or compliance expectations.

Who should choose something else?

A small team that mainly needs source control and lightweight automation may prefer GitHub or another Git platform with fewer administrative layers. Teams whose project management already lives successfully in Jira or another dedicated planning system should compare the value of Azure Boards against the disruption of moving work tracking. Organizations that require highly specialized continuous-delivery workflows should also compare dedicated CI/CD platforms rather than assuming Azure Pipelines is automatically the best fit.

Azure DevOps is a stronger choice when a development organization values integrated work tracking, private repositories, CI/CD, testing and package management, especially when Microsoft Entra ID, Visual Studio and Azure are already important parts of the engineering environment. Organizations prioritizing GitHub's newest AI and agentic development experience should also evaluate a hybrid or phased migration model rather than assuming Azure Repos must remain the long-term source-control layer.