Be able to implement multiple auto-shutdown times for each VMs through the portal.11 votes
Thanks for your feedback. We prioritize features based on the number of votes on the same. For those who would like to see this feature sooner, please vote for it.
Allow for greater variety of auto-shutdown schedules
- multiple times per day;
- various days in the week;
- recurring dates;
- one-time; etc.11 votes
Thanks for the feedback. We have this in our backlog and needs to be prioritized with other features. for those who would like to see this sooner, please vote for it.
I love the feature, but sometimes, I want to run a calculation that might last for a few days. I'd love to be able to configure something like "turn off autoshutdown for 48 hours"
As opposed to turning it off, then putting a few calendar events in my phone to remind me to go turn it back on again.11 votes
We are reviewing the request now. For those who would like to see this feature sooner, please don’t hesitate to vote for it. Thanks.
My labs users requested that they have a DTL template that installs a set of certificates to the "My" store and enables them to leverage them when the virtual machine is created. When I trigger the "base" creation using my custom ARM template via VSTS git, I encounter an error with the 'Microsoft.KeyVault/vaults/deploy/action' permission. It appears that DTL uses a deployment role that does not inherit my permissions to the KeyVault and therefore fails. Is it possible to create an AAD role/service principal for DTL activities so I can whitelist in KeyVault?11 votes
Thanks for submitting the idea! The feature that supports this scenario has been in our backlog without an ETA yet. For people who want to see the support sooner, please don’t hesitate to vote for it!
Setting VM expiration is helpful. Can you please provide the ability to define this as the policy at lab level along with VM level, similar to VM startup-shutdown policies? This will help us defining how long user can use a particular VM. It would be great if you can provide below options in policy:
VM Expiration after particular duration: Example, VMs will be deleted after 30 days from its creation.
Allow Opt-out at VM level11 votes
Thanks for submitting the idea! The support of this is current in our backlog and will be prioritized with other features. So we don’t have an ETA at this point of time. For anyone who wants to see it sooner, please don’t hesitate to add your votes.
should have a way to clear the microsoft.devtestlab/schedules from the resource page when auto-shutdown of VM is disabled or no longer in use.11 votes
Thanks for your suggestion. Could you please share with us why it’s important to delete the shutdown resource? Does it help if there’s some way to hide this kind of resources from the portal?
Could you please add support for custom images brought from on-premises to take part in the Hybrid Use Benefit (HUB) program?
Thank you!11 votes
Thanks for submitting the idea, Jack! We have a user story about it in our backlog. It needs to be prioritized with other user stories, so there’s no ETA yet.
For anyone who wants to get this done sooner, please keep submitting your votes!
Once you deploy a lab there is no way to change the name of the lab under "My Labs" at https://labs.azure.com. You can drill into the lab and change the title but not this name.10 votes
The template VM should be accessible like a regular VM via the Azure Portal. I got into a situation after configuring the firewall where the RDP port was blocked and could no longer access it. Support could not resolve it either. This would alleviate that by allowing normal Azure recovery methods.10 votes
There is a need for artifacts to provide links to documentation to simplify artifact use.
Several artifacts require you to input information that might not be immediately known at first glance, such as what exact string is required for software packages, or the formatting of a certain field.
If the artifact creator could provide a link to where the user can find additional information on how to use the artifact then it would lower the learning threshold and speed up first time use of DevTest Labs.10 votes
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.
The UI does not auto refresh itself to update the status of resources that are being created, so the only way to check if the status a resource has changed is to manually refresh the browser. Please can the view be automatically updated.9 votes
We have lots of lab machines with multiple terabytes of storage. These machines run 12 hours a day. While they are off (deallocated) can we switch the disk to standard instead of premium?
These would significantly reduce our costs for the machines that are on schedule. Premium disk on an off machine does not provide much value.
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/convert-disk-storage implies that we should be able to convert between disk types.9 votes
Auto Shut Down Notification Should go the user logged in to the server, it would be good to add Pop before couple of minutes in azure portal to notify the user.9 votes
Thanks for your suggestion! It’s currently in our backlog and needs to be prioritized with other features. So we don’t have an ETA at this point of time. If anyone wants to see this sooner, please don’t hesitate to vote for it.
Integrate DevTest Labs with ServiceNow to facilitate requesting a lab and lab resources without exposing the Azure Portal to end users. Currently all features are exposed on the Azure Portal instead of only the features available for the lab user. Prefer to not expose the Azure Portal to end users.9 votes
Thanks for the feedback Jeff! You mentioned that you’d rather not expose the portal to end users – can you expand on some of the reasons you want this behavior? Also, can you share who your end users are (developers, students, etc)?
shutdown vms when spending limit is reached in devTest-Environment9 votes
Thanks for submitting the idea! We’ve added this into our backlog, and will prioritize with other features. We don’t have an ETA at this point of time. For anyone who wants to see it sooner, please don’t hesitate to vote for it!
I would like to schedule shutdown and start-up multiple times a day. Ideally I want a shutdown at 12:01 PM, 5:00 PM, 10:00 PM, 12:00 AM, 2:00 AM, and 4:00 AM. I don't want the servers running unless it is being used.9 votes
Thanks for submitting the idea! Could you please help us to understand why you need auto-shutdown to be triggered so many times during a day? If someone needs to use the VM after the scheduled auto-shutdown time, DevTest Labs today allows you to set auto-shutdown notification, which allows users to delay the shutdown for an hour or two (and if so, then they will get another notification with options to delay). Does it work in your case?
Create a policy to shutdown a VM due to inactivity. This needs to be based on keyboard / mouse inactivity. The ability to execute the shutdown based on minutes inactive. Ability to change the minutes on different devtest labs9 votes
Thanks for submitting the idea! It’s currently in our backlog and prioritized with all the other features, so we don’t have an ETA at this point of time. For people who want to see this supported sooner, please don’t hesitate to give it a vote.
Currently it appears that the policies are universal - they apply regardless of the user type. It would be helpful to be able to tailor the policies to specific user types - eg Setting the max number of VM's per user for admins to be a higher threshold than max number of VMs per user for regular lab users.9 votes
Thanks for your feedback, John! Providing more fine-grained policies including this one is currently in our backlog. It’s been prioritized with other user stories in the backlog, so we don’t have an ETA yet.
For anyone who want to see it sooner, please keep submitting your votes!
At present VMs are created within the DevTest lab section of the portal. When a new DevTest Lab is created it could just create a Resource Group. Services could then be added via the rest of the portal, outside of DevTest Labs in the usual way. This avoids reinventing the wheel inside DevTest Labs and also provides a higher level of customisation for features such as Virtual Networks.9 votes
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!
When deploying a resource in a DevTest lab, the permissions applied to the resource groups and resources should be inherited from the DevTest lab (as well as from the subscription).
The permission inheritance flow/hierarchy should be Subscription, then DevTest lab.8 votes
- Don't see your idea?