FEEDBACK: Setup Script Pre-Check - Resources Available to be Deployed in Target Region

[AErmie]

When attempting to use the setup script to build the required prereq environment (ie. specifically the Containers Open Hack), it would be a better user experience if the script itself performed a check prior to attempting to deploy the resources.

The reason being (with the Containers Open Hack), it attempts to deploy an Azure SQL Database. However, depending on which Azure Region you select as part of the deployment command... you may encounter the following error:

Creating Azure SQL Server instance...
Deployment failed. Correlation ID: 19039868-35d5-46fe-85c6-248fad5b265b. Location 'West US' is not accepting creation of new Windows Azure SQL Database servers at this time.
Failed to create SQL Server.

The issue with this is that the script will have already deployed (successfully) some of the other resources (ie. Azure Container Registry, Azure Container Instance, Azure Virtual Machine). That means you have a partially successful and partly failed deployment; which you have to clean up first before re-attempting.

Adding a simple check for availability to create the resource(s) in the target region would make this setup far better.

[fortunkam]

Running into a similar problem with the IaC step of the DevOps v3 hack. The bicep files are failing to provision the SQL server in a subscription with the following error.

"Subscriptions are restricted from provisioning in this region. Please choose a different region. For exceptions to this rule please open a support request with Issue type of 'Service and subscription limits'. See https://docs.microsoft.com/en-us/azure/sql-database/quota-increase-request for more details."