Keep host maintenance deferral inside its supported resource and time limits

Source facts

Host-scope Azure Maintenance Configurations manage platform updates that do not require a restart on isolated VMs, isolated scale sets, and dedicated hosts. They permit scheduling within 35 days; afterward, updates are applied automatically. The maintenance window must be at least two hours, and rack-level maintenance is not supported. Using Maintenance Configurations also requires an appropriate Contributor-level role and subscription registration with the maintenance resource provider. Microsoft Learn.

Applicability

Confirm that the resource and intended update belong to the host scope. Keep guest package patching and scale-set OS image replacement outside this plan. Identify the workload’s interruption tolerance and the owner who can approve a host update within the available scheduling horizon.

DSE recommendation

Schedule the eligible host updates within the documented deferral limit and keep rack maintenance outside that promise. Give the maintenance calendar an explicit latest-action date and an owner for missed windows. Review the supported scope before telling an application team that all infrastructure work can be postponed. Coordinate workload preparation with the host update rather than relying on the configuration name as an availability guarantee.

Verification

Inspect the assigned resource, maintenance scope, and planned window before the approved operation. Record the observed update state and application behavior afterward. If a window is missed, compare the remaining deferral period with the recovery plan and escalate promptly. Preserve unsupported or out-of-scope maintenance events separately so the record distinguishes a failed configuration from a type of maintenance the feature does not control.

Official references

Microsoft Learn: Managing VM updates with Maintenance Configurations. Source reviewed September 9, 2026.