Quick Notes222 words

Agent and runner infrastructure — quick notes

Agents and runners — quick notes

FactDetail
Microsoft-hosted availabilityAzure DevOps Services only — not Azure DevOps Server
Microsoft-hosted billingCurrent paid plan: parallel-job concurrency. Free hosted job: minute limits. Legacy per-minute plans exist
GitHub-hosted for PipelinesPreview, region-dependent, per-minute PAYG, no free tier
Microsoft-hosted stateFresh VM for every job; filesystem discarded afterward
Cross-run pipeline cacheCache@2 restores server-backed files such as dependencies
Self-hosted advantageCaches + configuration persist run to run
Self-hosted reasonsMachine-bound tooling · direct private connectivity · machine-local state
Elastic self-hostedVM Scale Set agents; Managed DevOps Pools now recommended
Managed/VMSS cost in ServicesAzure resources + self-hosted parallel-job capacity
Self-hosted maintenanceOwn OS/tools, workspace hygiene, least-privilege security; required agent updates can be automatic

Traps

  1. "Use Microsoft-hosted with Azure DevOps Server" — impossible; hosted is Services-only.
  2. "A fresh hosted job cannot reuse dependencies" — false; Cache@2 restores a pipeline cache.
  3. "Microsoft-hosted is never minute-limited" — false; distinguish paid current-plan concurrency from free and legacy minute limits.

Primary sources

Ready to study Designing and Implementing Microsoft DevOps Solutions (AZ-400)?

Practice tests, flashcards, and all study notes — free, no sign-up needed.

Start Studying — Free