In this post, I will walk you through the step-by-step instructions for deploying an Azure DevTest Lab in the resource group of your choice, with the virtual network of your choice.
You had better get ready for resource group shock when you deploy DevTest Labs! When you create a lab, the default process will create a randomly named resource group for the lab. You can take some control over this process if you wish. Create a resource group with the name you want, in the region and subscription of your choosing.
You might even consider deploying an additional subscription in your tenant for this DevTest lab. Why would you do that? Because you will end up with lots of new, randomly named resource groups when users start to deploy virtual machines in the lab. This is a crude mechanism that allows Azure to apply unique permissions to each user’s virtual machines.
My preference is to create the DevTest Lab in the resource group that I have already created; otherwise, you have no control over the resource group name. Browse into the resource group in the Azure Portal and click + Add. Search for and click DevTest Labs and then click Create.
You will only be asked for a few bits of information:
A handy tip will be to create a tag to associate virtual machines with this lab; remember that the virtual machines will be deployed into randomly named resource groups. You’ll be able to identify the parent labs of machines using Tags in the Azure Portal or by querying tag attributes using Azure PowerShell.
It only takes a few minutes for a new lab to be created.
The new DevTest Lab is deployed with a virtual network. By default, all virtual machines in the lab will be deployed on this virtual network. You can modify this, for example, you might already have a virtual network that:
To modify the DevTest Lab virtual networking:
You now are in a position to start creating policies, adding artefacts, creating formulas, configuring lab settings, and adding users to roles.