Make Update Manager pre-check failure trigger an explicit cancellation decision

Source facts

Microsoft says a pre-event’s cancellation API call must occur at least ten minutes before the scheduled maintenance starts. Update Manager does not monitor the customer’s pre-check and automatically cancel for it; without cancellation, scheduled installation proceeds.

The documentation separately describes system cancellation when an internal error prevents delivery of the pre-event. That delivery-failure behavior should not be confused with cancellation after a customer’s readiness check fails. Microsoft Learn.

Applicability

Identify the maintenance configuration, pre-event endpoint, run identity, readiness criteria and cancellation owner. Review the full event-handling procedure and timing before using a business readiness check to control a production patch window.

DSE recommendation

DSE recommends an explicit branch from failed readiness to the documented cancellation action, with evidence that the correct run was targeted. Define what operators should do if the decision or cancellation occurs too late. Make the failure visible outside the script’s own log and require an owner to resolve an uncertain cancellation result.

Verification

In an approved test schedule, exercise successful readiness, failed readiness with timely cancellation, and a missed cancellation deadline. Compare handler evidence with the maintenance run’s actual status and machine results. Do not accept a failed script job as proof the patch run stopped. Preserve the run identity, decision time, cancellation response and observed outcome as separate evidence.

Official references

Microsoft Learn: Manage the pre and post maintenance configuration events in Azure Update Manager. Source retrieved September 9, 2026.