Intro

In this blog post, I want to get my Bicep modules under source control. They are already in this repository, but it would be nice to use them in other scenarios as well, without copying them each time. Suppose I copy and paste my modules between repositories. In that case, I also have to update them everywhere, so in this post, I will move my modules out of the repository and into an Azure Container Registry. When I move them there, I can update each module individually and then reference the version I need for each scenario.

Intro

In this short post, I will make the change I promised in the last part of the series, allowing the use of images from the Compute Gallery. The change is minor, but it is essential when working with AVD, since most AVD environments use custom images with multisession host pools.

Prerequisites

You will need to be up to date with the environment created in the previous parts of this series. The code is still part of the repository; build it now if you haven’t already.

Intro

I will create the session hosts in this part of my blog series about Azure Virtual Desktop (AVD) and Bicep. The session hosts are the workers in an AVD environment, and therefore, also one of the places we spent most of our time on optimizations and management. For this article, I will focus on the standard image from the Microsoft marketplace, but I expect to do more articles on how to manage an AVD image. I made a blog post last year about how to get started with Packer for Azure images, which works well for AVD.

Intro

In the first two blog posts (here) and (here), I wrote the most basic Bicep code for deploying a host pool, application groups, and a workspace. In this post, I want to go through some of the resources I usually designate as shared resources, meaning the workspace and the storage account. I already had the workspace in the last two articles, but this time, I am moving those resources into a shared resource group since multiple host pools often use the workspace.

Intro

In the first blog post (here), I wrote the most basic Bicep code for deploying a host pool, application groups, and a workspace. The result will be the same resources in this part, but the code will be a bit more advanced, allowing us to customize the deployment. I will keep the code simple, and the goal is to make the part we change for each deployment as simple as possible, while the Bicep modules contain the more advanced code.

Intro

Azure Virtual Desktop (AVD) is a managed service that runs virtual desktops and applications in Azure. Some components are deployed and configured to fit your company’s needs, even with a managed solution. In this blog post, I will walk you through the necessary steps before any end-user can log in to the virtualized desktop. I will use Bicep code and PowerShell in this blog post, but there are more options if you prefer other languages. This blog post also starts the topic of AVD on my blog, and I intend to add more during the next weeks and months. My main focus is on automation, but there will also be a few on optimization in AVD.