Gather all DevTest Lab VMs into a single Resource Group
Every DTL VM is deployed to a new, dedicated Resource Group by default. Apparently this a hardcoded behavior, we don't have any options to select which resource group we want to deploy the VM into. It would be way better if we could deploy the DTL VMs into the Resource Group where the DTL is defined... or at least select the RG freely upon deployment.
We’ve planned the work to create minimum number of resource groups for lab VMs (starting from a single resource group for multiple lab VMs, and expand to another resource group if the resource quota is hit). Does it solve your problem? Providing naming convention for the lab-generated resource group and other resources is also planned.
Dave Medvitz commented
Please.... This has been hanging around for a while, and even small usage of DevTest Labs has made a mess of our management.
Rogier Dijkman (Azurekid) commented
We use resource groups in Azure to group specific roles. As an example we're deploying HA RDS farms in Azure where we split the Brokers, Gateways and sessionhosts to separate resource groups.
Within the DevTest Labs this is currently not possible
Jason van der Paal commented
I've had to custom build a deployment solution to be able to track billing the UID reference is only good while the lab exists, once it is gone I can't track charges back which makes DTL difficult to sell.
Even being able to copy tags from the lab into the RGs as it creates them would help.
Chris Hinds commented
Is there any updates to permitting VM's to be provisioned into a selected resource group? Ideally I would like to control what resource group VM's are added to when provisioned, this would allow a more control from an administrative perspective.
Douglas James Boyd commented
Agreed - gets quite messy having an RG per VM!