Fit scale-set shutdown work inside the already-issued termination deadline

Source facts

Scale-set termination notifications cover deletion, including autoscale scale-in, but not restart, reimage, redeploy, or stop/deallocate operations. They cannot be enabled for Spot instances. The configured delay is between five and fifteen minutes, and instances must receive the updated model. Once an event exists, its timeout cannot be extended: expiry permits the pending deletion to proceed. A completed workload may approve earlier, although other pending deletes can delay that early execution. Microsoft Learn.

Applicability

Use this decision for non-Spot instances whose notification configuration and Scheduled Events polling are already established. Identify the actual delete event and its deadline before starting shutdown work. Do not interpret an unrelated maintenance notification as this configurable termination-delay contract.

DSE recommendation

Measure graceful shutdown against the configured delay before enabling the workflow, and treat an issued event’s deadline as fixed. Ask the application owner to prioritize the minimum work needed to preserve an acceptable outcome. Define what to do if that work cannot finish in time. Do not rely on editing the scale-set model after notification as an extension of the current event.

Verification

Rehearse an approved deletion on a disposable instance and record notification receipt, shutdown completion, acknowledgement if used, and actual termination. Compare elapsed work with the configured deadline. Include a test where the application does not acknowledge early, so expiry behavior is understood. Retain unfinished shutdown work as a design failure requiring a different recovery approach, not as evidence that the platform promised more time.

Official references

Microsoft Learn: Scale-set termination notifications. Source reviewed September 9, 2026.