---
title: Azure agents
description: "With the capacity to run an **extra**Azure-hosted build we get another agent to run a pipeline and can run multiple pipelines at the same time. But it **still won’t be parallel pipelines**, because we only get one VM-less agent. This…"
url: "https://ariste.info/dynamics365almguide/azure-agents/"
updated: "2024-08-25"
category: "Legacy Guide / Azure hosted build for Dynamics 365 Finance & SCM"
---

# Azure agents

With the capacity to run an **extra**Azure-hosted build we get another agent to run a pipeline and can run multiple pipelines at the same time. But it **still won’t be parallel pipelines**, because we only get one VM-less agent. This means **we can run a self-hosted and azure hosted pipeline at the same time, but we cannot run two of the same type in parallel**. If we want that we need to [purchase extra agents](https://docs.microsoft.com/en-us/azure/devops/organizations/billing/buy-more-build-vs?view=azure-devops&WT.mc_id=DOP-MVP-5003976#microsoft-hosted-cicd).

With a private Azure DevOps project we get 2GB of Artifacts space (we’ll see that later) and one self-hosted and one Microsoft hosted agent with 1800 free minutes:

![08CEA665 618A 4F15 B9EC F86A405FA7D8](https://i1.wp.com/ariste.info/wp-content/uploads/2020/04/08CEA665-618A-4F15-B9EC-F86A405FA7D8.jpeg?fit=909%2C1024&ssl=1)
Azure hosted build: Azure DevOps project pricing

**We’ll still keep the build VM**, so it’s difficult to tell a customer we need to pay extra money without getting rid of its cost. Plus we’ve been doing everything with one agent until now and it’s been fine, right? So **take this like extra capacity**, we can divide the build between both agents and leave the MS hosted one for short builds to squeeze the 1800 free minutes as much as possible.

#### Subscribe!

Receive an email when a new post is published