Azure Capacity Extender disk controller swap when needed

Problem - The Azure Capacity Extender will fail to swap an AVD between SKUs when the target SKU requires a disk controller type change. Such as, a v6 SKU with NVMe disk controller type trying to change to a v5 SKU which needs SCSI disk controller type.

The commands to swap disk controller type exist and work today in both bash and powershell.

Bash, example for swapping a VM with NVMe controller to SCSI:
az vm update -g <RESOURCE GROUP> -n <VM-NAME> --set "hardwareProfile.vmSize=Standard_D4as_v5" "storageProfile.diskControllerType=SCSI"

Bash,  example for swapping a VM with SCSI controller to NVMe:
az vm update -g <RESOURCE GROUP> -n <VM-NAME> --set "hardwareProfile.vmSize=Standard_D4as_v6" "storageProfile.diskControllerType=NVMe"

Powershell, example:
Update-AzVM -ResourceGroupName <RESOURCE GROUP> -VM $vm
where $vm is: "Get-AzVM -ResourceGroupName <RESOURCE GROUP> -Name <VM-NAME>" with $vm.HardwareProfile.VmSize defined as the target SKU and $vm.StorageProfile.DiskControllerType defined as the target disk controller type.

Vision - The Azure Capacity Extender automatically swaps controller type when needed.

2

Comments (1 comment)

0
Avatar
Carl Long
Thank you for submitting your feature request—we truly value input from our community.

Next steps:
     • We will review your request and update its status as it progresses through our evaluation process.
     • If any clarification is needed, we'll follow up with you directly in the comments.

We also encourage the community to influence our decision through comments, votes, and feedback.

Please sign in to leave a comment.