<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Azure DevOps on Erwin Staal</title>
    <link>https://staal-it.nl/categories/azure-devops/</link>
    <description>Recent content in Azure DevOps on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Sun, 25 Jul 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/categories/azure-devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automatically renew the image used in an Azure DevOps private agent</title>
      <link>https://staal-it.nl/posts/automatically-renew-private-agent-images/</link>
      <pubDate>Sun, 25 Jul 2021 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/automatically-renew-private-agent-images/</guid>
      <description>&lt;p&gt;In a previous post, I wrote about creating your own hosted Build and Release agents in Azure DevOps. That process could be improved by regenerating the VM image, for example, every month. By doing that, you stay up-to-date with both the latest versions of all the tools installed as well as with security patches. This post will describe how to do that using an Azure DevOps pipeline which will be triggered monthly.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Manual approval in an Azure DevOps YAML-pipeline</title>
      <link>https://staal-it.nl/posts/manual-approval-in-an-azure-devops-yaml-pipeline/</link>
      <pubDate>Sun, 31 Jan 2021 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/manual-approval-in-an-azure-devops-yaml-pipeline/</guid>
      <description>&lt;p&gt;Last week I was creating a YAML-pipeline in Azure DevOps to deploy some ARM Templates. Before deploying those changes to my production environment, I wanted to have a manual approval in place. Here&amp;rsquo;s how I did that.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Using an Azure Virtual Machine Scale set as Azure DevOps agents</title>
      <link>https://staal-it.nl/posts/using-vm-scale-sets-as-azure-devops-agents/</link>
      <pubDate>Fri, 02 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/using-vm-scale-sets-as-azure-devops-agents/</guid>
      <description>Over the past few weeks, I&amp;rsquo;ve been implementing a few new networking features in Azure for a client. We did that to make our infrastructure more secure. I&amp;rsquo;ve been playing around with VNET&amp;rsquo;s, Private Links, Services Endpoints and Access Restrictions on Azure Web App, SQL databases, Storage and KeyVault. One of the issues I stumbled upon quite quickly was the fact that when you restrict access to a resource, Azure DevOps can&amp;rsquo;t reach that anymore as well.</description>
    </item>
    
  </channel>
</rss>
