Microsoft-hosted agents alternatives
The 5 alternatives below are grouped by kind of runner, and each says whom it suits. Start from the requirement that matters most to you: price per minute, operating systems, caching, isolation or where the runners have to run.
Microsoft-hosted agents trade-offs to weigh
The built-in agents for Azure Pipelines, suited to Azure DevOps teams whose jobs fit a fixed 2-core machine and who prefer per-parallel-job pricing.
- Disk space and processing power cannot be increased on Microsoft-hosted agents
- No ability to connect remotely to an agent
- Private connections such as ExpressRoute or VPN cannot be used; traffic goes over the public network
- Hosted images do not conform to CIS hardening benchmarks
Microsoft-hosted agents alternatives, by kind
Runners from your CI platform or cloud
The first-party hosted runners of GitHub, GitLab, Buildkite and Azure, plus cloud-native runner services.
AWS CodeBuild-hosted runners
AWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job.
- Fresh build environment
- Ephemeral
- arm64
- Windows
- Docker layer cache
- GPU
- BYOC
Whom it suits: Teams on AWS that want GitHub Actions, GitLab or Buildkite jobs to run inside their own account with IAM and VPC access. AWS’s managed way to run GitHub Actions, GitLab and Buildkite jobs on single-use CodeBuild compute in your own account, suited to teams already on AWS.
Full profile →AWS CodeBuild-hosted runners alternativesWebsite ↗
Buildkite hosted agents
Buildkite’s managed agents: a single-use virtualized environment per job on Linux, macOS and Windows, billed per vCPU minute.
- Ephemeral virtualized environment
- Ephemeral
- arm64
- macOS
- Windows
- Docker layer cache
Whom it suits: Teams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machines. Buildkite’s own managed agents, suited to Buildkite Pipelines users who want hosted Linux, macOS and Windows capacity billed by vCPU minute.
GitHub-hosted runners
GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute.
- Fresh VM
- Ephemeral
- arm64
- macOS
- Windows
- GPU
Whom it suits: Teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners. The default runners for GitHub Actions, suited to teams that prefer zero setup and to public repositories, with larger sizes available per minute on paid plans.
GitLab-hosted runners
GitLab.com’s built-in runners: each job gets a single-use VM, metered in compute minutes with a cost factor per machine size.
- Ephemeral VM
- Ephemeral
- arm64
- macOS
- Windows
- GPU
Whom it suits: Teams on GitLab.com that want CI jobs to run with no runner setup and can work within the included compute minutes. The built-in runners for GitLab.com, suited to teams that want no runner administration and whose usage fits the compute-minute quota of their tier.
Managed DevOps Pools
Azure service that runs autoscaled Azure Pipelines agents on VM sizes and images you choose, billed at standard Azure rates.
- Azure VM
- Windows
Whom it suits: Azure DevOps teams that need bigger or custom-image agents and private network access without operating scale sets. 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.
Microsoft-hosted agents vs alternatives
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
| Buildkite hosted agents | Buildkite | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Ephemeral virtualized environment | $0.008/min | 64 vCPU / 256 GB | Yes | Not documented | No | Not documented |
| 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 |
| 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 |
Head-to-head: Buildkite hosted agents vs Microsoft-hosted agents · GitLab-hosted runners vs Microsoft-hosted agents · Managed DevOps Pools vs Microsoft-hosted agents
Frequently asked questions
What are the main alternatives to Microsoft-hosted agents?
Is there an open-source alternative to Microsoft-hosted agents?
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). Microsoft-hosted agents alternatives. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/alternatives/azure-pipelines-agents/