Thanks for your feedback! Could you please comment which DevTest policies would you like to apply for those test environments imported from a resource group into the Labs (assuming the Labs allows you to import VMs from a resource group)? We’ve added it into our backlog, but don’t have an ETA yet. For anyone who want to see this happen sooner, please don’t hesitate to vote for it.

Thanks for your feedback! We are currently working on a feature that would allow you to link an existing resource group to your lab, so that the lab will track the cost for all the VM resources in that resource group and apply auto-shutdown/start policies. If this is not what you are looking for, please don’t hesitate to let me know.

Thanks for your feedback! We are reviewing this one and prioritizing it with other features in the backlog. For anyone who want to see this happen, please don’t hesitate to vote for it.

Thanks for your idea! This idea is currently in our backlog and being prioritized this with other features. If you have any criteria in mind how you would like to define “idle” state, please share with us.

Thanks for submitting the request. We will investigate this requirement and will let you know if it made to our backlog.

Snapshot as Hyper-V is not supported in Azure yet, but we are working with the relevant teams to get something equivalent. We don’t have an ETA at this point. Please stay tuned. Thanks!

Thanks for submitting the idea! It’s current in our backlog for DevTest Labs to support multiple VM creation using the same VM base. We don’t have an ETA at this point of time, because it needs to be prioritized with all the other times in the backlog. For people who want to see it sooner, please don’t hesitate to add your votes for it. Thanks!

We will be implementing a better control for RGs in the Lab. The specifics are still being designed. Thanks for the feedback!

Thanks for submitting the request. We are planning to support PaaS components in DevTest Labs and it is in our backlog. We don’t have an ETA at this point of time though, because it has to be prioritized with all the other items in our backlog. For people who want to see the support sooner, please don’t hesitate to vote for it and share in the comments which Azure PaaS services (and how) you’d like to use in the Labs.

Thanks for submitting the idea. This is currently in our backlog now. Meanwhile, could you share with us in addition to start/stop, what else permissions you expect to give/not to give to another use? E.g. Is “transfer rights” about transferring all the permissions the original user has for the VM or a subset of it? When giving the rights, will the new user be allowed to delete VMs?

Thanks for the feedback! Integration with on-prem TFS is in our backlog, although we don’t have an ETA to share yet. Meanwhile, could you please provide more details at which point you want to publish your build artifacts to a Lab VM? There are a couple of solutions based on the scenarios. One scenario is baking the latest build into a VM template in the Lab as part of the CI pipeline. We are currently working on the cmdlets which allows you to use when authoring a post-build task. Another scenario is to access the build from within a running Lab VM. This requires the network configuration to connect the Lab with your on-prem environments. Azure has provided a couple of options including Express Route, site-to-site, and point-to-site, etc. Thanks!

Thanks for your feedback! As more further investigate, the DevTest Labs supports VSTS Git and GitHub today. I’ve added this into the backlog. Given different Git repo offers different client for Labs to use and connect to, it’d be helpful if you could share with us which one you want to support first, so that the Labs can support them one by one. Thanks!

Thanks again for the feedback! We currently have a feature in the backlog that allows you to create a VM with an attached disk at the same time. We still need to prioritize it, so there is no ETA at this point of time. If you want to see it sooner, please don’t hesitate to vote this idea!

Thanks for submitting this idea. This idea has been added into our backlog. We don’t have an ETA for it at this point of time though, because it has to be prioritized with all the other items in the backlog. For people who do want to see it sooner, please don’t hesitate to add your votes for it. Thanks!

Thanks for your idea. Could you please help us to understand why the default VNET naming pattern doesn’t work with you?

When a new DevTest Lab is created, it does create a resource group consists of a Lab resource, a storage account and a virtual network. VM creation needs to happen within the Lab though, while it also creates a separate resource group just for the VM. Is it something mentioned here that you want to create VM (as “services”) from the normal VM creation flow in Azure outside of the Lab but the Lab somehow can recognize it, or are you asking for a different thing? If it’s the former, what’s the downside in your opinion that you’d prefer to do that outside of the Lab? I appreciate any clarification. Thanks!

Thanks for submitting the idea! We’ve added this into our backlog, and it will be prioritized with all the other items. For people who want to see it sooner, please don’t hesitate to vote for it. Thanks!

Thanks for your feedback! We are thinking about adding a link that points to readme.md, but please let us know if you want something different.

Thanks for your suggestion! We’re currently looking into this.