How to Configure Auto-Shutdown for an Azure Virtual Machine

November 21, 2026

Azure virtual machines can continue consuming compute charges when they are left running outside working hours. Auto-shutdown schedules a VM to power down at a defined time, which is useful for development, test, training, and other workloads that do not need to run continuously.

This guide covers the current Azure portal workflow, notification options, verification, and the limits that matter for production systems. Auto-shutdown is a shutdown schedule. It is not a complete start/stop automation strategy, and it does not delete the VM or its attached resources.

Before you begin

  • Know the VM, resource group, and expected operating hours.
  • Have permissions to update the VM’s settings in the Azure portal.
  • Confirm that shutting down the workload will not interrupt users, backups, patching, scheduled jobs, or monitoring.
  • Decide whether a notification should go to an email address or webhook.
  • Check the time zone you intend to use. Microsoft notes that UTC is the default, so do not assume the displayed time is local time.

Configure auto-shutdown in the Azure portal

  1. Sign in to the Azure portal.
  2. Open Virtual machines and select the VM.
  3. In the VM menu, under Operations, select Auto-shutdown.
  4. Toggle the schedule to On.
  5. Set the shutdown time.
  6. Set the time zone to match the business schedule. Treat this as a required review step rather than accepting the default blindly.
  7. If you want a warning before shutdown, set Send notification before shutdown to Yes, then provide an email address or webhook URL.
  8. Select Save.
Production warning: Do not apply a development-lab schedule to a production VM. A scheduled shutdown can disconnect users, stop services, and interrupt jobs even when the VM is healthy.

Verify the configuration

Reopen Operations > Auto-shutdown and confirm that the toggle, time, time zone, and notification details are still present. Record the setting in your infrastructure documentation or change log.

After the scheduled time passes, check the VM overview for its power state. Also confirm that the application’s dependent services behaved as expected. Do not rely only on the portal’s schedule page; verify the actual workload outcome.

Understand the cost impact

Auto-shutdown can reduce compute use during off-hours, but stopping a VM does not remove every charge. Managed disks, reserved public IP addresses, snapshots, backup services, and other attached resources can continue to incur costs. Review the resource group and Azure Cost Management after the first billing cycle.

Use the Azure Cost Analysis guide to compare the expected reduction with actual spend. If the VM is no longer needed, deletion is a separate action and requires a resource-retention decision.

Auto-shutdown is not auto-start

The basic portal procedure above schedules shutdown. It does not by itself prove that the VM will start again each morning. If users need a daily start schedule, design and test a separate start automation, such as an approved Azure automation workflow, and account for dependencies and startup time.

Common errors and limitations

The VM shuts down at the wrong local time

Review the configured time zone. Azure documentation notes that UTC is the default. Reopen the schedule after saving and compare it with the business time zone and any daylight-saving expectations.

The VM shut down while someone was using it

Auto-shutdown does not know whether a user is active. Remove or change the schedule, then add an operational owner and an exception process for workloads that must remain online.

The bill did not drop as much as expected

Check the VM power state and inspect other resources in the same resource group. Compute savings do not eliminate storage, networking, backup, or IP-related charges.

Notifications are not arriving

Recheck the email address or webhook configuration and treat notifications as advisory. The shutdown schedule should not be considered safe solely because a notification was configured.

Rollback

  1. Open the VM in the Azure portal.
  2. Go to Operations > Auto-shutdown.
  3. Toggle the schedule to Off.
  4. Select Save.
  5. Confirm the VM remains in the intended power state and update your change record.

Related Guava Insights guides

Official documentation

Topics:
Read next