You plan to deploy a new Azure Virtual Desktop host pool but cannot complete the deployment. What should you do to enable the deployment?

If you cannot complete a new Azure Virtual Desktop host pool deployment, it often indicates you've hit a subscription limit or a regional resource quota. Azure subscriptions have default limits on resources like CPU cores, virtual machines, and specific services. A new deployment might exceed these limits, preventing successful provisioning. Submitting a support request allows Microsoft to review your usage and increase these limits if your subscription and region support it. Adding a lock to an existing host pool prevents deletion or modification but doesn't resolve deployment issues for a new host pool. Stopping and deallocating a VM might free up some resources but usually won't resolve a hard subscription limit for a new deployment. Changing the VM size might be necessary if the chosen size is unavailable, but it doesn't address general deployment failures due to subscription-wide limits.