SOLVED

Azure Dev Test Lab subscription for Auto shutdown VMs

Brass Contributor

Hi All,

 

I would like to know why Azure Dev Test lab subscription is required to enable auto shutdown feature for Azure VMs ?

3 Replies

@Sagar_Lad 

 

Hi what is the reference for this  ? 

Because in a regular subscription ( Not only Azure Dev Test Lab ) you have the feature  on the blade of each virtual machine . Also you can leverage Azure Resource Tags, Azure log Analytics and Azure Automation  to start and stop VM on schedule if autoshutdown is not suitable for your need .

More information here : Azure Policy - Auto shutdown your virtual machines - DEV Community

https://docs.microsoft.com/en-us/azure/automation/automation-solution-vm-management

best response confirmed by Sagar_Lad (Brass Contributor)
Solution

Hi @Sagar_Lad ,

 

This is not entirely correct. You don't need to create a DevTest lab resource to enable auto-shutdown for Azure VMs, but you need to provision a 'microsoft.devtestlab/schedules' resource that will enable this functionality.

 

As you can see, the schedule is coming from devtestlabs RP, so the only "dependency" is that this RP must be registered in your subscription and this service must be available in the region, where you deploy your VMs in Azure. You can then for instance extend your ARM template, like it is described in many places, for example here.

 

@Sagar_Lad  This is not applicable for Dev Test Lab subscription, you can setup an automation Auto stop/Start policy for any subscription to save computing cost.

 

 

1 best response

Accepted Solutions
best response confirmed by Sagar_Lad (Brass Contributor)
Solution

Hi @Sagar_Lad ,

 

This is not entirely correct. You don't need to create a DevTest lab resource to enable auto-shutdown for Azure VMs, but you need to provision a 'microsoft.devtestlab/schedules' resource that will enable this functionality.

 

As you can see, the schedule is coming from devtestlabs RP, so the only "dependency" is that this RP must be registered in your subscription and this service must be available in the region, where you deploy your VMs in Azure. You can then for instance extend your ARM template, like it is described in many places, for example here.

 

View solution in original post