Windows Virtual Desktop provides a turnkey VDI solution for Microsoft Azure. The infrastructure components such as RD Broker or RD Web Access are “hidden.” In Microsoft Azure Portal, you can only see the RD Host Session (for pooled sessions) or Windows 10 VMs (for personal sessions). Because these Azure VMs are running, they use Azure credit. To reduce the amount of your invoice, you can shut down the Azure VMs during off-hours such as nights or weekends. Then, the VMs are started again to be available during working hours.

You can implement that by using an Azure Automation account and an automatic startup/shutdown solution. In this topic, we will see how to accomplish that.

Requirements

To follow this topic, you need the following:

  • A working Windows Virtual Desktop solution
  • A working Log Analytics workspace
  • A working Azure Automation account

How to implement the solution

Navigate to your Azure Automation account and click on Start/Stop VMs. Then select Manage the solution.

Azure Automation account

Next click on Create solution.

Azure Automation account - Create solution

In the marketplace, type start/stop and select Start/Stop VMs during Off-Hours.

Start/Stop VMs during Off-Hours

Next click on Create.

Start/Stop VMs during Off-Hours - create

In the configuration wizard, select your log analytics workspace and your Azure Automation account. Then, in the parameters section, set the following settings:

  • Name of the target resource group. Specify the resource group where the Windows Virtual Desktop VMs are located. Be careful, all VMs in this resource group will be scheduled to shut down.
  • VM Exclude. Specify the VMs you don’t want in this scheduling.
  • Schedule. Specify when you want to shutdown and restart your VMs.
  • E-mail functionality. If you choose Yes, specify an E-mail to create an alert (in Azure Monitor) and send a notification when the VMs are stopped and started.

Azure Automation account - parameters

Check the result

After I created the solution, I left Azure for one day. Next day, I checked the monitoring counter in the Azure VMs, and I saw that between 6:00pm and 9:00am no resources were consumed.

Check the result

In the solution, I saw several recent jobs showing that VMs were stopped and started.

 VMs were stopped and started

Parameters

Finally, I received an E-mail to notify me that VMs were started.

VMs were started

VSAN from StarWind eliminates any need for physical shared storage just by mirroring internal flash and storage resources between hypervisor servers. Furthermore, the solution can be run on the off-the-shelf hardware. Such design allows VSAN from StarWind to not only achieve high performance and efficient hardware utilization but also reduce operational and capital expenses.

Learn more about ➡ VSAN from StarWind

Change the scheduling

If you need to change the schedule of the solution, you can navigate to ScheduledStartStop_Parent. Then, open the Schedules tab. There, you can change the scheduling of your jobs.

ScheduledStartStop_Parent

Views All Time
42
Views Today
81
Appreciate how useful this article was to you?
No Ratings Yet
Loading...
Back to blog
The following two tabs change content below.
Romain Serre
Romain Serre
Senior consultant at Exakis
Romain Serre works in Lyon as a Senior Consultant. He is focused on Microsoft Technology, especially on Hyper-V, System Center, Storage, networking and Cloud OS technology as Microsoft Azure or Azure Stack. He is a MVP and he is certified Microsoft Certified Solution Expert (MCSE Server Infrastructure & Private Cloud), on Hyper-V and on Microsoft Azure (Implementing a Microsoft Azure Solution).