-
Hello toxic,
Thank you for pointing this out.
To clarify, Azure enforces vCPU quotas during VM creation by validating that the requested VM does not exceed either the Total Regional vCPU quota or the VM size family quota. While the documentation notes that quota usage reporting can include both allocated and deallocated cores, stopped (deallocated) virtual machines do not block new VM deployments, as they do not consume vCPUs required for VM creation.
Each VM request is evaluated sequentially in the order defined in the scenario. In this case, VM4 and VM5 fit within the remaining quotas in the North Central US region, while VM6 cannot be created because its vCPU requirement would exceed the remaining regional quota after the earlier deployments. This behavior aligns with Azure’s documented VM quota enforcement model.
Cheers,
Irene @ Tutorials Dojo
