CI Runnerscirunners.org
Alternatives

Microsoft-hosted agents alternatives

Answer in brief

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.

By the CI Runners editors · Updated

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.

  • 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

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
Microsoft-hosted agentsAzure PipelinesLinux, macOS, Windows, x64Platform-hostedFresh VM$40/month per parallel job2 vCPU / 7 GBNot documentedNot documentedNoUnited States
AWS CodeBuild-hosted runnersGitHub Actions, GitLab CI, BuildkiteLinux, Windows, x64, arm64Your cloud accountFresh build environment$0.005/min72 vCPU / 144 GBYesYesNoUnited States
Buildkite hosted agentsBuildkiteLinux, macOS, Windows, x64, arm64Platform-hostedEphemeral virtualized environment$0.008/min64 vCPU / 256 GBYesNot documentedNoNot documented
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
GitLab-hosted runnersGitLab CILinux, macOS, Windows, x64, arm64Platform-hostedEphemeral VM$10 per 1,000 compute minutes32 vCPU / 128 GBNot documentedYesNoNot documented
Managed DevOps PoolsAzure PipelinesLinux, Windows, x64Platform-hostedAzure VM$15/month per parallel job + Azure VM costNot documentedNot documentedNot documentedNoUnited 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?
AWS CodeBuild-hosted runners, Buildkite hosted agents, GitHub-hosted runners, GitLab-hosted runners, Managed DevOps Pools. Which one fits depends on your pipeline; each entry above says whom it suits.
Is there an open-source alternative to Microsoft-hosted agents?
None of the alternatives listed here is recorded as open source; see open-source and self-hosted runners.

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/