Azure-NVMe-Conversion.ps1 | When attempting to convert an Azure VM to use an NVMe controller with a v6 SKU (e.g. Standard_E8s_v6), the provided conversion script fails if the VM is part of a Proximity Placement Group (PPG).

[Hybrionix]

Observed behavior:

The script proceeds with the resize without checking whether the target SKU is supported in the PPG.
Azure rejects the resize or the VM ends up in a boot failure state (INACCESSIBLE_BOOT_DEVICE).
No clear error message is provided by the script regarding PPG constraints.

Expected behavior:

The script should validate whether the requested VM size is available in the current PPG before attempting the conversion.
If the SKU is not supported, the script should fail fast with a clear, actionable error message (e.g. “Selected VM size Standard_E8s_v6 is not available in the current Proximity Placement Group. Please remove the VM from the PPG or choose a supported size.”).

[msftphleiten]

thanks for raising the issue.
We are working on identifying the windows issue, was this a trusted launch VM or a standard launch?
Which OS version?
is it an Azure marketplace image or a custom image?

On the PPG issue, I will add an error message for better understanding, but it is not possible to check if a PPG constraint exists until the VM starts.