1. Azure DevOps Agents as Container Instances

    The Microsoft provided hosted build agents for Azure DevOps might not suite all requirements. E.g. the Az PowerShell modules on the images provided by Microsoft are lagging behind. To compensate, in general, pipelines spend a lot of time installing dependencies to complete the job at hand. Having a custom build agent can resolves these issues as the dependencies are installed at image creation and available from there on, thus these images beter suite your needs (build for purpose). You can host build agents on any compute platform. For this solution we build docker images and host them on Azure Container Instances as it is relatively easy to create container images containing all the requirements compared to VMs. It is also far easier creating new versions as the creation of the image is fully automated. …


  2. Azure ARM Linked Templates and Complete mode

    Just a small blog post on Azure ARM Linked Template deployment and Complete mode since I couldn’t find a satisfying answer quickly enough via my favorite search engine.

    TL;DR: Linked Template resources together with the master template resources are deployed / kept / updated. Resources out of the cumulative result of master + linked templates are deleted.


  3. DSC Pull Server reloaded. Part 5: Containers!

    With Windows Server 2016, container support was introduced. Now that the Pull Server supports SQL, it felt naturally to me to try and see if the Pull Server could be containerized. A containerized Pull Server allows us to run a Pull Server anywhere where Windows Server Containers are supported (also on Windows 10!). Let’s investigate a prototype!

    On PSConfAsia and PSConfEU I demoed the Pull Server running in containers. Please see the video section for the session recordings.


  4. New Terraform Azure Automation Resources

    Some time ago I contributed 3 new Terraform resources to the AzureRM Resource Provider:

    This was my first ever contribution to a Go project so I’m very proud this got merged! These 3 resources where the missing pin (for me at least) to have an end-2-end scenario enabled where pre-compiled DSC mof files and DSC resource modules could be send to an Azure Automation Account. This enables Terraform VM deployments including Guest state configuration assignment handled through Azure Automation. In this blog post I’ll demonstrate the use of these resources. I won’t go into detail on how to get started with Terraform and such as there is plenty of info available already. …


  5. DSC Pull Server reloaded. Part 4: Migrate EDB or MDB to SQL

    In the last post, we have seen how to use pre-create the Pull Server Database as an Azure SQL Database. It’s always nice to be able to start fresh but a lot of you already deployed Pull Servers based on WMF5+ backed by an EDB or MDB database and you want to move forward right? Now it’s time to figure out how to “migrate” your existing Pull Servers to a new SQL backed Pull Server. The key here is to again use DSCPullServerAdmin to make your life easy! If you haven’t already:

    Install-Module DSCPullServerAdmin -Verbose -Force -Scope CurrentUser