A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
Hi System Admin,
actually it is not a configuration mistake, it simply means that VM size Standard_D2as_v5 does not have capacity available in that region right now. Even if the SKU exists in centralus Azure can temporarily block deployments when there is no available hardware capacity for that size. This is very common with popular VM families ))))))))))))).
What u can do is either choose a different VM size in the same family for example try D2s_v5 or another similar SKU or deploy in a different region where capacity exists. Sometimes selecting a specific availability zone instead of no zone also works because capacity can differ per zone.
You can check available SKUs in the region using Azure CLI with az vm list-skus --location centralus --size Standard_D2as_v5 --all and confirm restrictions. But realistically the fastest solution is to pick another similar VM size or another region.
This is a capacity issue on the platform side, not a template or AVD configuration problem.
rgds,
Alex