Managed DevOps Pools
Azure service that runs autoscaled Azure Pipelines agents on VM sizes and images you choose, billed at standard Azure rates. Microsoft’s managed alternative to scale-set agents for Azure Pipelines, suited to teams that need custom sizes, images and private networking at Azure compute rates.
Overview
Managed DevOps Pools is an Azure service that creates and scales agent pools for Azure Pipelines. Microsoft describes it as an evolution of Virtual Machine Scale Sets agent pools. You create a pool as an Azure resource, choose VM sizes, images (Azure Pipelines images, marketplace images or your own from Azure Compute Gallery) and a maximum agent count, and the service provisions agents on demand or keeps standby agents ready on a schedule.
The agent VMs run in a subscription owned by Microsoft rather than your own, while charges for compute, storage and egress are billed at standard Azure rates. A pool can use a Microsoft-provided network or a subnet you delegate from your own virtual network to reach private resources. Pools are stateless by default, giving each job a new agent, or stateful, reusing agents for up to seven days.
Notable
- Microsoft’s features timeline lists the general-availability feature set, including more Azure regions and Key Vault integration, under November 2024
- Support for public static IP addresses was added in November 2025
- Generation 2 versions of the Azure Pipelines images were added in April 2026
- Instance Mix, allowing up to five VM sizes per pool, was added in September 2026
Managed DevOps Pools specifications
| Attribute | Details |
|---|---|
| CI systems | Azure Pipelines |
| Operating systems | Linux, Windows |
| Architectures | x64 |
| Deployment | First-party hosted runners |
| Where it can run | Azure |
| Isolation | Agents are Azure VMs in a Microsoft-owned subscription, with each pool isolated in a dedicated virtual network; stateless pools give every job a new agent, stateful pools reuse agents for up to seven days |
| Fresh environment per job | Not documented |
| Hardware | Azure virtual machine sizes that you select for the pool, up to five sizes per pool with Instance Mix, with an optional attached data disk |
| Performance (vendor claim) | Not documented |
| Runner sizes | Azure VM sizes of your choice, subject to Managed DevOps Pools quota for the VM family |
| Caching | Stateful pools keep agent state for up to seven days so later jobs can reuse packages and files from earlier runs. Standby agents can be kept online on a manual or automatic schedule. |
| Docker layer caching | Not documented |
| GPU | Not documented |
| Concurrency | Limited by the pool’s Maximum agents setting, the Managed DevOps Pools quota for the VM family, and the number of self-hosted parallel jobs in the Azure DevOps organization |
| Job limits | Individual jobs can run for a maximum of two days |
| Static IPs | Yes |
| SSH into running jobs | No |
| Observability | Predefined metrics charts, an Agents pane showing provisioning status, and optional log export to Azure Log Analytics. |
| Setup | Register the Microsoft.DevOpsInfrastructure resource provider, create a pool with a Dev Center project in the Azure portal, ARM, Bicep or Azure CLI, then reference the pool by name in your pipelines. |
| Example label | pool: name: fabrikam-managed-pool |
| Pricing | No per-minute price. You pay standard Azure rates for the compute, storage and data egress the pool uses, plus Azure DevOps self-hosted parallel jobs: one is free and each extra one costs $15 per month. Azure Hybrid Benefit cannot be used. |
| Free tier | One free self-hosted parallel job with unlimited minutes per Azure DevOps organization; Azure compute is still charged |
| Compliance | Not documented |
| Regions | Azure public cloud regions listed for the Microsoft.DevOpsInfrastructure resource provider in your subscription |
| Open source | No |
| Company headquarters | Redmond, Washington, United States · More from the United States |
Facts from Managed DevOps Pools’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You need Azure Pipelines agents more powerful than Microsoft-hosted agents
- You want agents attached to your own virtual network to reach private resources
- You want to use your own VM images or the same images as Microsoft-hosted agents
- You need jobs that run longer than six hours, up to two days
- You want agents that keep state between jobs for up to seven days
Trade-offs
- Agent VMs run in a Microsoft-owned subscription and cannot currently be accessed directly
- Azure Hybrid Benefit cannot be used with Managed DevOps Pools
- Without standby agents, a pipeline might wait up to 15 minutes for an agent to be provisioned
- Supported only with Azure DevOps Services in the Azure public cloud
Good fit for: Azure DevOps teams that need bigger or custom-image agents and private network access without operating scale sets.
Use cases Managed DevOps Pools fits
- Faster builds: You can select larger Azure VM sizes and keep agent state for up to seven days for cache hits.
- Windows builds: Windows Server 2022 and 2025 Azure Pipelines images are provided.
- Your own cloud: Pools are Azure resources billed through your subscription and can attach agents to a subnet of your own virtual network, although the VMs run in a Microsoft-owned subscription.
- Security and compliance: Stateless pools give every job a new agent, and Microsoft recommends them as a defense against supply chain attacks.
How Managed DevOps Pools compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| Managed DevOps Pools | Azure Pipelines | Linux, Windows, x64 | Platform-hosted | Azure VM | $15/month per parallel job + Azure VM cost | Not documented | Not documented | Not documented | No | United States |
| Microsoft-hosted agents | Azure Pipelines | Linux, macOS, Windows, x64 | Platform-hosted | Fresh VM | $40/month per parallel job | 2 vCPU / 7 GB | Not documented | Not documented | No | United States |
| AWS CodeBuild-hosted runners | GitHub Actions, GitLab CI, Buildkite | Linux, Windows, x64, arm64 | Your cloud account | Fresh build environment | $0.005/min | 72 vCPU / 144 GB | Yes | Yes | No | United States |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
| GitLab-hosted runners | GitLab CI | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Ephemeral VM | $10 per 1,000 compute minutes | 32 vCPU / 128 GB | Not documented | Yes | No | Not documented |
| Elastic CI Stack for AWS | Buildkite | Linux, Windows, x64, arm64 | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Australia |
Head-to-head: AWS CodeBuild-hosted runners vs Managed DevOps Pools · Managed DevOps Pools vs Microsoft-hosted agents · enomem vs Managed DevOps Pools
Frequently asked questions
What is Managed DevOps Pools?
Which CI systems does Managed DevOps Pools work with?
How does Managed DevOps Pools isolate jobs?
Is Managed DevOps Pools open source?
How much does Managed DevOps Pools cost?
How do you set up Managed DevOps Pools?
pool: name: fabrikam-managed-pool.Does Managed DevOps Pools have a free tier?
How many jobs can run at once on Managed DevOps Pools?
Where do Managed DevOps Pools runners run?
Where is Microsoft Corporation based?
What are the alternatives to Managed DevOps Pools?
Sources
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/overview?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/architecture-overview?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/pricing?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/features-timeline?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/configure-scaling?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/configure-images?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/configure-pool-settings?view=azure-devops
- learn.microsoft.com/en-us/azure/devops/managed-devops-pools/configure-networking?view=azure-devops
- azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services/
- microsoft.com/en-us/privacy/privacystatement
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). Managed DevOps Pools. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/azure-managed-devops-pools/