Scheduling the start and shutdown of Azure VMs
allows saving money on Azure costs. A VM that has been shut down and deallocated does not incur any Azure charges (except for space it occupies in blob storage). Shutting down VMs is usually beneficial for DEV/QA and other non-production environments, CI/build servers, or for production environments where access to VMs is required only during specific times.
In this case study, we’ll discuss how to shutdown cloud-based Microsoft Azure Virtual Machines on a schedule via CloudMonix.
The process takes just a few minutes and is easily replicable to any and all VMs in your Azure subscription. It works for both Windows and Linux VMs and does not rely on somewhat complex and hard to maintain PowerShell scripts or Azure Automation runbooks. Also, if any errors occur during either VM start or shutdown, you will get an immediate notification.