An Azure relational database service.
For Azure SQL Database, that error pattern usually maps to one of these subscription-level issues:
- The subscription is not registered with the SQL resource provider (
Microsoft.Sql) - The selected region is not enabled for SQL server creation on that subscription
- The subscription has hit a regional quota or capacity limit
Since all allowed regions were already tried, the most direct path is:
- In the Azure portal, go to All Services → Subscriptions.
- Select the affected subscription.
- Under Settings, open Resource providers.
- Search for sql.
- For Microsoft.Sql, select Register or Re-register.
If using CLI, run:
az provider register --namespace Microsoft.Sql
If using PowerShell, run:
Register-AzResourceProvider -ProviderNamespace Microsoft.Sql
After that, try creating the logical SQL server again.
If the same error continues, the documented resolution is to open a support request for region access / Service and subscription limits so the region can be enabled for the subscription. The documented errors for this include:
-
Your subscription does not have access to create a server in the selected region. -
Provisioning is restricted 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' -
Location 'region name' is not accepting creation of new Windows Azure SQL Database servers for the subscription 'subscription id' at this time
If the issue is quota-related, the documented errors include:
-
Server quota limit has been reached for this location. Please select a different location with lower server count. -
Could not perform the operation because server would exceed the allowed Database Throughput Unit quota of xx.
A similar resolved case showed deployment succeeding after region-level access was enabled for the subscription.