Create a new Microsoft SQL database

Request Region access for Azure SQL Database in West Europe; because Microsoft.Sql is already registered and deployment works elsewhere, repeating resource-provider registration is unnecessary. This exact error is handled through a region-access request for the affected subscription.^1^

Submit the request

1. In the Azure portal, open Help + support and select Create a support request.
2. Search for quota.
3. Under Which service are you having an issue with?, select None of the above.
4. For Service, select Service and subscription limits (quotas)—not Technical.
5. Select the affected subscription and continue.
6. Set Problem type to SQL Database, then select Create a support request.
7. Under Provide details for this request, select Enter details.
8. On Quota details, choose:
   • Quota type: Region access
   • Location: West Europe
   • Expected Consumption: the expected SQL Database capacity in vCores
9. Select Save and continue, provide the contact details, and submit the request.

Microsoft documents Region access specifically for subscriptions receiving “Your subscription does not have access to create a server in the selected region.” Requests use expected vCore consumption even when the database will use the DTU purchasing model; the documented estimate is 1 vCore ≈ 100–125 DTUs.^2^

After approval, retry creating the logical SQL server and database in West Europe. If West Europe is not mandatory, creating them in a currently permitted region remains the immediate alternative. Ensure dependent resources and application connectivity are designed for that selected region.

A standard vCore quota increase is only appropriate if the portal instead reports an explicit server, DTU, or vCore quota-limit error. For the message shown here, select Region access, not vCores per subscription.^1^

References

1. Resolve capacity errors with Azure SQL Database or Azure SQL Managed Instance
2. Request quota increases for Azure SQL Database and SQL Managed Instance