Separate Azure VM hibernation capability from guest readiness

Source facts

Microsoft’s troubleshooting sequence first checks whether hibernation is enabled on the VM, then checks whether the guest operating system has enabled it successfully. The guide also says hibernation immediately after boot is unsupported and recommends waiting a few minutes before retrying. Microsoft Learn

Applicability

This guide applies when an Azure VM exists but a requested hibernation operation fails, rather than when an operator is selecting a new VM size.

DSE recommendation

DSE recommends capturing the precise operation and error before changing settings. Record the VM capability flag, current power state, time since boot, and any guest-side hibernation findings as separate observations. Follow the operating-system-specific troubleshooting path if the capability is already enabled. Use a bounded retry only where the documented condition fits, and keep repeated failures assigned to an owner instead of calling the configuration healthy from the flag alone.

Verification

Repeat the check after the identified condition has been addressed and record the new operation result. Confirm the subsequent resume behavior with the workload owner before closing the case. Preserve a failed result and the relevant guest findings if hibernation still does not complete, so the next investigation starts from observed evidence.

Official references

• Microsoft: Troubleshoot hibernation in Azure – Azure Virtual Machines | Microsoft Learn