VS402984: Pipeline fails when referencing missing agent pool

For pipelines that execute only a few times per month, the most cost-effective strategy is typically Microsoft-hosted parallel jobs, provided the usage stays within the free tier or low-minute consumption. The VS402984 error ("The requested resource does not exist") is a configuration failure indicating your YAML references a pool that is either deleted or incorrectly named; it is not a cost-related error.

Microsoft-Hosted vs. Self-Hosted B-Series VMs

While a self-hosted agent on an Azure B-series VM can eliminate per-minute charges, the math often fails for infrequent runs:

n
• Microsoft-hosted: Zero maintenance, no idle cost beyond execution minutes, and no patching/hardening required.
• Self-hosted (B-series): Incurs hourly VM costs regardless of use (unless automated to stop), requires manual effort for patching, monitoring, and agent maintenance.

The break-even point where a self-hosted VM becomes cheaper usually requires the pipeline to run frequently enough to exceed the free monthly hosted minutes, or for the VM to be used for other tasks to justify its uptime cost.

The Impact of Pipeline Caching

Whether pipeline caching provides a net cost saving for fewer than five runs per month depends on your dependency size:

• Time Savings: Caching reduces execution time by skipping dependency downloads (e.g., node_modules, NuGet packages). If a build takes 10 minutes without cache and 2 minutes with cache, you save 8 minutes per run.
• Storage Costs: Azure DevOps cache storage is generally not billed per GB within standard limits, but for infrequent runs, the "warm-start" latency (downloading the cache) can sometimes offset the time saved by not building.

Resolving Error VS402984

To fix the pipeline failure, ensure the agent pool reference is valid:

1. Navigate to Organization Settings > Agent pools.
2. Verify the exact name of the pool you are using.
3. Update your YAML configuration to match the name:

pool:
  name: 'Your-Valid-Pool-Name'

n

Assumption: This analysis assumes you are using the standard tier. If you are on a private project with zero free parallel jobs, the cost implications of self-hosted agents change significantly.