How can we improve Microsoft Azure Lab Services?

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.

55 votes
Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)

We’ll send you updates on this idea

Krisztian shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...
  • Dave Medvitz commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

Feedback and Knowledge Base