Cost optimising your Yaml Azure DevOps pipeline

In one of my pipelines, I’ve got some .NET Framework code that I’ve wrapped in a Container. One thing about Windows Containers that gets a little annoying is that you need to match the Container base image to the Windows OS that you’re building and running it on.
My image is based on which necessitates me self hosting a Windows VM Azure DevOps build agent.

The Problem

Naturally i try and keep my Azure subscription costs low, so i have a Shutdown policy set for the VM so it deallocates at 7pm each night. This does leave me with the problem of builds queuing up during the day until i remember to turn the VM on. What i need is a smart way of the Pipeline starting the VM first.


I started exploring a solution using an Azure DevOps Agentless job (in order to achieve maximum savings).
It would call out to an existing piece of code i have in Azure Functions which starts a VM based on values in the Request Body, Managed Identity and the right RBAC roles being set up.

The issue was that the Agentless Azure Functions task and the REST API task have a hard timeout of 20 seconds, which causes problems when you’re waiting for code to run that starts a VM.
The complex answer to this problem is to use a Callbacks, or to use a different codebase that facilitates not waiting on a response from the Azure RM API.
The much simpler answer is to use a hosted agent to run some Azure Powershell.

After the PowerShell runs, you can then use your specific Agent Pool to build and deploy the container.

My Azure Devops project code this code is open, if you’re wanting a look at the resulting Pipeline. It’s done using the new Multi-Stge YAML feature, although it started life as a Classic build pipeline.

visual pipeline tasks

Leave a Reply

Your email address will not be published. Required fields are marked *