Understanding Microsoft-hosted vs. Self-hosted Agents in Azure DevOps

 When working with Azure DevOps Pipelines, the concept of agents is fundamental. These agents are responsible for running your builds, tests, and deployments. Azure DevOps provides two main options:

  • Microsoft-hosted agents

  • Self-hosted agents

Let’s explore both options in detail, compare them, and see when to use which.

1. What is an Agent in Azure DevOps?

An agent is essentially a machine (VM or physical) that runs pipeline jobs. It checks out code, installs dependencies, runs scripts, and performs deployments.

2. Microsoft-hosted Agents

These are virtual machines maintained by Microsoft, automatically spun up on demand.

Key Features:

  • No setup required – Just define the vmImage in your pipeline.

  • Pre-installed tools like .NET, Node.js, Python, Java, Azure CLI, Docker, and more.

  • Clean environment – Every run gets a fresh VM.

  • Auto-scaled – No need to worry about parallelism or load balancing.

  • Billing – Free tier available with limited minutes; beyond that, usage is billed.

Example Usage:

yaml
pool:
  vmImage: 'windows-latest'

Microsoft will allocate a VM with the latest Windows OS and tools for your pipeline run.

3. Self-hosted Agents

Self-hosted agents are machines (on-premises or cloud VMs) that you configure and manage yourself.

Key Features:

  • Full control over installed software, environments, and network access.

  • Persistent tools and cache, improving build performance.

  • No auto-scaling – you’re responsible for provisioning and maintaining agents.

  • Ideal for:

    • Working behind firewalls or in isolated environments.

    • Projects requiring non-standard tools.

    • Reducing costs with long-running build agents.

Example Usage:

yaml

  name: 'SelfHostedAgentPool'

You must register your machine to the SelfHostedAgentPool and install the Azure Pipelines agent manually.



4. Comparison Table

FeatureMicrosoft-hosted AgentSelf-hosted Agent
MaintenanceMicrosoftYou manage it
EnvironmentFresh VM per jobPersistent machine
Custom SoftwareLimitedFull control
Tool AvailabilityPre-installedYou install manually
CostFree/minutes billedNo per-minute billing
PerformanceSlower (due to setup time)Faster (cached dependencies, tools)
Best ForSimplicity, quick setupsCustom, high-performance, secure jobs

5. Which Should You Choose?

  • Go with Microsoft-hosted agents if:

    • You want minimal setup.

    • Your builds use common tools.

    • You’re OK with a clean VM every time.

  • Choose Self-hosted agents if:

    • You need special software or networking.

    • You want faster builds with persistent caching.

    • You want to reduce pipeline execution costs in the long run.

Conclusion

Both agent types offer value depending on your needs. Microsoft-hosted agents are perfect for convenience and general workloads, while self-hosted agents shine in performance, customization, and cost-effectiveness for complex or large-scale builds.

Whether you’re building a microservice, deploying to Kubernetes, or just running some tests, choosing the right agent model is key to optimizing your CI/CD workflows

Comments

Post a Comment

Popular posts from this blog

🤖 Copilot vs Microsoft Copilot vs Copilot Studio: What’s the Difference?

Microsoft’s AI-powered tools are transforming the way we work, create, and collaborate. But with all the buzz around “Copilot,” “Microsoft Copilot,” and “Copilot Studio,” it’s easy to get confused. Let’s break down what each of these really means—and when to use them. 🚀 What Is “Copilot”? “ Copilot ” is Microsoft’s umbrella term for AI assistants built into its tools. Whether you’re in Word, Excel, or Teams, Copilot helps you do things faster —like generating text, summarizing information, analyzing data, or writing emails. Think of it like an intelligent assistant sitting next to you, helping with routine and creative tasks. 🔍 Example Copilots: Copilot in Word – Drafts documents, rewrites text, summarizes long reports. Copilot in Excel – Generates formulas, explains complex data, creates dashboards. Copilot in Teams – Summarizes meetings, drafts responses, manages tasks. 👉 It’s not a separate product—it’s a built-in experience across Microsoft tools. 🧠 What Is Micro...
Read more

Understanding Auto-Numbering in a Multi-Transaction System

Image
  Introduction Auto-numbering is a common requirement in business applications, ensuring each record (such as an invoice, order, or customer ID) gets a unique number. However, when multiple users or processes try to generate numbers at the same time, conflicts can arise. This blog explains how a system ensures safe and sequential auto-numbering when multiple transactions happen simultaneously. What Does the Diagram Represent? The diagram below illustrates how two different transactions (Event Pipeline 1 & Event Pipeline 2) interact with the Auto-Number Table to generate unique numbers while maintaining data consistency. Each process follows a structured approach: Initiate Transaction – A request is made to create a new account with an auto-number. Lock the Auto-Number Table – The system temporarily prevents other processes from modifying the number. Read the Latest Number – The system retrieves the most recent number (e.g., 7). Increment the Number – It updates the table...
Read more

Integrating Dynamics 365 CRM with MuleSoft Using a Synchronous C# Plugin

  🔗 🚀 Step 1: Set Up Your C# Plugin in Dynamics 365 CRM 1️⃣ Create a New C# Plugin Project in Visual Studio Open Visual Studio → Create a Class Library (.NET Framework) Project Install the Microsoft.CrmSdk.CoreAssemblies NuGet package Add a new class called LeadCreatePlugin.cs 🚀 Step 2: Write the Synchronous C# Plugin Code 🔹 Plugin Code to Capture New Leads & Send Data to MuleSoft using System; using System.ServiceModel; using Microsoft.Xrm.Sdk; using System.Net.Http; using System.Text; public class LeadCreatePlugin : IPlugin { public void Execute ( IServiceProvider serviceProvider ) { // Get the execution context IPluginExecutionContext context = (IPluginExecutionContext)serviceProvider.GetService( typeof (IPluginExecutionContext)); // Run the plugin only when a lead is created if (context.MessageName.ToLower() != "create" ) return ; // Retrieve the Lead entity data if (context.InputParamet...
Read more