SQL Server Deployment in East US 2 Region — Regional Capacity Restriction

Question

SQL Server Deployment in East US 2 Region — Regional Capacity Restriction

Jake Stratton 15

Problem description

I am unable to provision a new Azure SQL Database logical server in the East US 2 region. Both Azure CLI and ARM deployment via Bicep fail with the error indicating that the region is not accepting new SQL server creation at this time.

Environment

Azure SQL Database in the East US 2 region.

What I've already tried

I have attempted deployment using both Azure CLI and Bicep (ARM templates). The deployment fails with the error 'Location 'East US 2' is not accepting creation of new Windows Azure SQL Database servers at this time.' I also verified that other resources in the same deployment succeeded, and other Azure services in the region are working normally. The first support response indicated no available data for further diagnosis.

Current status

I am seeking clarification on whether this is a temporary capacity constraint or a subscription-level restriction. I would like guidance on how to proceed, including possible workarounds such as deploying in an alternate region or obtaining support to whitelist my subscription for SQL server provisioning in East US 2.

SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-27T16:36:26.7666667+00:00

Hi @Jake Stratton ,

Location 'East US 2' is not accepting creation of new Windows Azure SQL Database servers at this time.

this is most likely a temporary regional capacity constraint rather than an issue with your Azure CLI commands, Bicep template, or deployment configuration.

East US 2 is one of Azure's most heavily utilized regions, and during periods of high demand Microsoft may temporarily restrict the creation of new Azure SQL logical servers until additional capacity becomes available. In such cases, other resources in the deployment can continue to be provisioned successfully while SQL Server creation requests are blocked.

As potential workarounds, I recommend the following:

Retry the deployment after some time, as capacity may become available.

Deploy the Azure SQL logical server in an alternate region if your workload requirements allow.

Verify Azure Service Health for any active advisories affecting Azure SQL Database provisioning in East US 2.

If East US 2 is a required region, open a Microsoft Support request and ask the support team to review regional capacity availability and region access for your subscription.

If the issue persists, please share the following details for further investigation.

Mail Id
Complete deployment error message and please send the Private messages.

1 answer

Your answer

SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-27T16:36:26.7666667+00:00

Hi @Jake Stratton ,

Location 'East US 2' is not accepting creation of new Windows Azure SQL Database servers at this time.

this is most likely a temporary regional capacity constraint rather than an issue with your Azure CLI commands, Bicep template, or deployment configuration.

East US 2 is one of Azure's most heavily utilized regions, and during periods of high demand Microsoft may temporarily restrict the creation of new Azure SQL logical servers until additional capacity becomes available. In such cases, other resources in the deployment can continue to be provisioned successfully while SQL Server creation requests are blocked.

As potential workarounds, I recommend the following:

Retry the deployment after some time, as capacity may become available.

Deploy the Azure SQL logical server in an alternate region if your workload requirements allow.

Verify Azure Service Health for any active advisories affecting Azure SQL Database provisioning in East US 2.

If East US 2 is a required region, open a Microsoft Support request and ask the support team to review regional capacity availability and region access for your subscription.

If the issue persists, please share the following details for further investigation.

Mail Id
Complete deployment error message and please send the Private messages.

Answer 1

@Jake Stratton I hope you are doing well,

Yes it is a temporary capacity constraint I have seen this before. The East US region in Azure is one of its most heavily used locations, which can sometimes restrict the availability of specific VM sizes,SQL Severs etc... particularly in-demand options

Workaround or possible option availble follow this proceedure explained by other MS support here https://learn.microsoft.com/en-us/answers/questions/2279324/i-am-unable-to-provision-mysql-flexible-database-i

If this answer helped clarify the platform capabilities and save you troubleshooting time, please consider marking it as Accepted. This helps others in the community find similar solutions.