Azure VM resize: PowerShell lists Dv5 sizes, but Azure Portal only offers Dv4

You are seeing a real inconsistency: the VM-specific PowerShell query lists Dv5 resize targets, while the portal exposes only Das_v4 after deallocation. Get-AzVMSize with a VM name is intended to return sizes available for that VM on its current hardware cluster, so those results are not merely every regional SKU. Capacity and cluster placement are the most likely variables; generation, SCSI, and ordinary managed disk tiers do not by themselves explain all three Dv5 omissions. Re-run Get-AzVMSize immediately after confirming the VM is fully deallocated, then check the desired SKU’s regional restrictions with Get-AzComputeResourceSku. If Dads_v5 still appears, test the resize on a nonproduction clone or during a rollback-ready maintenance window, rather than forcing production first. Staying on Das_v4 is reasonable while it meets performance and support requirements. Move to Dads_v5 only for a measured benefit, and open an Azure support case if portal and API results continue to disagree.