This video picks up where the last two DevOps videos left off. We use one Azure DevOps Pipeline and multiple jobs to build an updated image with Azure Image Builder, then deploy new Virtual Machines, Windows Virtual Desktop Session Hosts in this example, with the updated image. We also go over addressing Image Builder failures in the DevOps pipeline.
In this video, we go over using an Azure DevOps pipeline to automate building and Deploying Windows Virtual Desktop (WVD) Session Hosts. This Azure DevOps tutorial builds on previous videos and demonstrates how to use Azure ARM Templates and parameter files to deploy WVD Session Hosts. Next, the ARM template and parameter file is used in an Azure DevOps pipeline along with PowerShell and Azure Key Vault secretes to securely automate the deployment of Session Hosts based on the latest Shared Image Gallery (SIG) image.
In this video, we go over using an Azure DevOps pipeline to automate the image build process with Azure Image Builder. This Azure DevOps tutorial goes over using Azure DevOps with VS Code to manage files. We then build a YAML pipeline with Azure CLI, ARM template deployments and PowerShell to build an image.
I do not like to wait; who does? So, getting a ten-minute delay logging into
VM’s with the message “Please Wait for the Windows Modules Installer” was
frustrating. There is a way to speed
this up, and that is what this post is about.
In this post and accompanying video, I show you how to bypass this
message when creating a custom image, including with Azure Image Builder.
The playlist below is a three-part video series that takes a user through the process of using Azure Image Builder to create a custom Windows 10 multi-user image. The first video starts with an overview and configuring a subscription for Azure Image Builder. The second video demonstrates creating and deploying a template and building an image based on that template. The third video walks through the steps to add software to the image in the build pipeline.
I am finally getting around to some hands-on with Azure
Image Builder. More to come on that shortly. For now, I want to document my first issue for
anyone who may experience the same problem.
When creating the image builder template with the New-AzImageBuilderTemplate
command, I got the following error message:
Az.ImageBuilder.internal\New-AzImageBuilderTemplate @PSBo … The subscription is not registered to use namespace ‘Microsoft.VirtualMachineImages’. See https://aka.ms/rps-not-found for how to register subscriptions.
Subscription not registered
The error indicates that a required resource provider, Microsfot.VirtualMachineImages in this instance, is not registered. The provider can be registered with PowerShell or through the portal. Below are the steps for each.
From the portal, go to your Subscription, then find Resource
Providers under Settings.
Resource Provider in the Azure Portal
Search for the resource provider Microsoft.VirtualMachineImages. Notice the status is Not Registered. Click the Register button in the portal to register the resource provider.
Resource Provider Not Registered
To register a provider from PowerShell, log into Azure with
rights to register a resource provider, such as subscription admin. Next, use the Register-AzResourceProvider
command below to register the provider.