Overview of the Issue

I'm trying to build a new image from a 6th generation SKU Standard_E2ds_v6.

When the image (windows) is built, i'm unable to launch a VM from the image with the following error:

It seems that the disk controller is set to scsi by default, instead of honoring the parent image configuration, which I think should be nvme.

When i manually create the VM of the same spec, I can see that the disk controller is NVMe.

https://learn.microsoft.com/en-us/azure/virtual-machines/nvme-linux#212-check-controller-type-using-azure-cli

Someone else has reported an similar issue.

Reproduction Steps

I have just tried to build the packer script below, and then launch an image from the image.

I can provide the deprovision script (sysprep) script if needed, but I think its pretty standard.

Plugin and Packer version

Packer v1.13.1

/home/ashley/.config/packer/plugins/github.com/hashicorp/azure/packer-plugin-azure_v2.3.3_x5.0_linux_amd64

Simplified Packer Buildfile

packer {
  required_plugins {
    azure = {
      source  = "github.com/hashicorp/azure"
      version = "~> 2"
    }
  }
}

source "azure-arm" "windows" {
  location = "UK South"
  vm_size  = "Standard_E2ds_v6"
  subscription_id = var.subscription_id
  tenant_id       = var.tenant_id

  use_azure_cli_auth                = true
  managed_image_resource_group_name = var.resource_group
  managed_image_name                = var.image_name

  async_resourcegroup_delete         = true
  managed_image_storage_account_type = "Premium_LRS"

  os_type         = "Windows"
  image_publisher = "MicrosoftWindowsServer"
  image_offer     = "WindowsServer"
  image_version   = "26100.4652.250713"
  image_sku       = "2025-datacenter-azure-edition"

  communicator   = "winrm"
  winrm_username = "packer"
  winrm_insecure = true
  winrm_use_ssl  = true
  winrm_timeout  = "1h"

}

# sysprep
build {
  sources = ["source.azure-arm.windows"]
  provisioner "powershell" {
    scripts = [
      "./files/scripts/deprovision-image.ps1"
    ]
  }
}

Operating system and Environment details

OS, Architecture, and any other information you can provide about the environment.

Log Fragments and crash.log files

Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.

Set the env var PACKER_LOG=1 for maximum log detail.