When attempting to import a virtual machine (VM) to Spot, the process may fail with an error indicating that the id parameter is required and cannot be null. This issue often occurs when the VM uses an unsupported disk type.

1. Review the error message received during the import process:

   Status code [400] differ from SC_OK, Body:[{"request":{"id":"...","url":"/azure/compute/resourceGroup/.../virtualMachine/.../details?...","method":"GET","timestamp":"..."}, "response":{"status":{"code":400,"message":"Bad Request"},"errors":[{"code":"GENERAL_ERROR","message":"Parameter 'id' is required and cannot be null."}],"count":1}}]

2. Verify the VM disk type in Azure:

   • This error is typically caused by the use of unmanaged disks, which are not supported by Spot.

   • Azure has deprecated unmanaged disks, and new unmanaged disks cannot be created as of September 30, 2023. For more details, refer to Microsoft’s official documentation:

     Unmanaged disks deprecation

3. Migrate the VM from an unmanaged disk to a managed disk:

   • Use the Microsoft guide for this process:

     Migrate to managed disks

   • Important: This process is irreversible. Ensure that this action aligns with your use case and organizational requirements before proceeding.

4. After the disk migration is complete, re-import the VM to Spot.

Outcome

Following these steps ensures compatibility with Spot services by using Azure managed disks, enabling a successful VM import.