Ability to perform scheduled shutdown based on day, not just time. Similar to start. We want to force shutdown all VMs on Fridays 11pm.82 votes
Thanks for your suggestion! The feature is currently in our backlog, but has to be prioritized with other ones. So we don’t have an ETA at this point of time. Please don’t hesitate to vote for it if you want to see it’s done sooner.
Having one time per day for all machines to start at is not enough. For example I have a few machines that connect to a share on the other machine at startup, so I NEED this one machine to come up slightly earlier26 votes
Thanks for submitting the idea! After the review, we’ve got this into our backlog. We don’t have an ETA at this point of time, because we need to prioritize it with other features in the backlog. For people who need the same thing, please don’t hesitate to vote for it!
Universities are start to use DevTest Lab as new platform for classroom LABs and students LABs.
The MAIN request is have a time limits on the VM assigned to students, only in this way can controll students a prices of LABs.12 votes
We have started working on a managed option for DevTest Labs that will cover this scenario.
We will update this post to inform about further updates. Thanks.
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 labs8 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.
shutdown vms when spending limit is reached in devTest-Environment6 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!
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 level6 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.
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.6 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!
Sometimes I need an instance just for Today, and tomorrow. I would like to be able to add 1 or more "one time" auto-start commands that would allow me to auto-start just for those days. eg. It's monday and I know i need an instance on Tue and Wed - so, i'd like to put in a one-time start for Tue AM/Time then another for Wed AM/time. But still have it respect that auto-shutdown policy.4 votes
Thanks for submitting the request. Are you looking at using VM only for 2 days and then after that you want to delete them or shut them down?
Enforce certain policies, but allow users to opt out of others. User working on demos with customers may want to opt out of a shutdown based on idle time (open idea currently), but we want to enforce a shutdown at 7pm on Fridays. They should not be able to override the weekly shutdown. This may vary based on DevTestLab.3 votes
Makes a lot of sense. Thanks!
Currently, we can only set daily VM shutdown. We need to shutdown a VM based on a day. Example. Start on Monday and shutdown it by Friday.2 votes
want to shutdown vm on daily basis, so please provide an option of calendar2 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.
We start deploying DevTest LAB for univerties.
We have 1 project with 150 LABs so we are about to deploy all the LABs using Powershell but we are not able to configure the subnet policy using powershell :
- Used for VM creation
- Activate shared public IP address
- Activate public IP address creation1 vote
Thanks for submitting your idea.
Can you help us understand your scenario better? This would help us better understand the underlying problem that we would like to solve.
Is there a way or a plan to add custom policies? Currently, there are 5 predefined policies , can more custom policies be added to these?1 vote
Thanks for submitting the idea! Could you please elaborate a little bit more what kind of custom policies would you like to run in the Labs?
- Don't see your idea?