# Check the exceptions before starting self-service VM maintenance

> When should an operator avoid proactively starting an Azure planned-maintenance redeploy?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:30:45+00:00
- Modified: 2026-09-10T00:35:07+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Checklist
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

When should an operator avoid proactively starting an Azure planned-maintenance redeploy?

## Potentially affected

Operators considering self-service maintenance during an Azure VM planned-maintenance wave.

## DSE recommendation

Review the VM's lifecycle and temporary-disk dependencies before choosing Start now.

## Article

## Source facts

Microsoft says self-service maintenance is not available for every VM and directs operators to the Start now status to determine availability. It does not recommend this approach for availability-set deployments. Its contraindications include frequent shutdown or resizing, short-lived VMs due for deletion, and workloads that need to retain substantial local ephemeral-disk state. Existing Scheduled Events integration for proactive failover or graceful shutdown is another listed reason to avoid self-service maintenance. Frequent shutdown or resizing can revert maintenance status and produce additional maintenance impact. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications).

## Applicability

Consider this decision only when the VM is affected by a current planned-maintenance wave and a self-service option is offered. Identify availability-set membership, shutdown automation, resize frequency, expected retirement, local-state dependencies, and existing event-driven failover or shutdown coordination. Keep a host-scope Maintenance Configuration distinct from this proactive maintenance action.

## DSE recommendation

Review the VM’s lifecycle and temporary-disk dependencies before choosing Start now. Have the application owner approve the reason for taking control of timing and the expected recovery sequence. If a listed contraindication applies, review the documented scheduled-maintenance behavior instead of initiating redeployment just to clear a portal notice. Preserve the VM’s current maintenance state with the decision.

## Verification

For an approved self-service action, inspect its result and validate the application’s recovery before processing the next dependent machine. Record whether the state remains completed after later lifecycle changes. If the operation is deferred, retain the applicable scheduled window and the owner responsible for readiness. Treat a new maintenance notice as a fresh state to investigate, not proof that the previous operator failed to perform the action.

## Official references

[Microsoft Learn: Handling planned maintenance notifications](https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications). Source reviewed September 9, 2026.

## Primary reference

- Name: Maintenance notifications - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Check the exceptions before starting self-service VM maintenance,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.