Keep scheduled VM maintenance readiness active while requesting postponement

Source facts

Microsoft says scheduled maintenance usually cannot be delayed; support can make a best-effort attempt to postpone it. After the self-service window is missed, the portal still shows the window in which Azure will maintain the VM. Microsoft Learn

Applicability

This guide applies when the owner of an Azure VM affected by planned maintenance cannot accommodate the published schedule and is considering a support request. It addresses the uncertainty of postponement rather than eligibility for starting self-service maintenance.

DSE recommendation

DSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan. Assign one owner to track the request and another to preserve application readiness for the published window. Record the affected VM identifiers, current scheduled window, support response and business constraint together. Continue the agreed readiness work while the request is unresolved, and avoid announcing an unconfirmed replacement schedule to dependent teams.

Verification

Before the published window, reconcile the latest portal information with the support response and the workload readiness plan. Record any confirmed schedule change explicitly and retain its source. If no change is confirmed, have the application owner state how the existing window will be handled. Close the request only after the actual maintenance outcome and application condition have been reviewed; a submitted support case alone does not establish a deferred event.

Official references

• Microsoft: Use the portal for maintenance notifications – Azure Virtual Machines | Microsoft Learn