SQL Database: Request for Enabling Zone Redundancy in East US — Provisioning Disabled Error

Question

SQL Database: Request for Enabling Zone Redundancy in East US — Provisioning Disabled Error

Stephen Abney 0

Problem description

I am attempting to enable zone redundancy on an existing Azure SQL Database using Azure CLI, but the operation fails with the error 'ProvisioningDisabled'. The request was to update the database with '--zone-redundant true', but it is not supported in my current configuration.

Environment

Azure SQL Database in East US region, standalone database on a Premium tier with no elastic pool, currently in production.

What I've already tried

I have explicitly retried the Azure CLI command to enable zone redundancy on the database, but it consistently returns the 'ProvisioningDisabled' error. I also attempted to enable zone redundancy through the Azure portal, which also failed. Additionally, I created new standalone test databases in various tiers and regions to verify if the issue is specific to my current setup; these tests confirmed that in East US, zone redundancy cannot be enabled, while it is supported in Central US.

Current status

I am seeking guidance on how to enable zone redundancy for my Azure SQL Database in East US, or understanding if there are subscription or region-specific restrictions that prevent this. I would appreciate steps to verify my configuration and options to resolve this issue.

0 comments

2 answers

Your answer

Answer 1

ProvisioningDisabled generally means Azure is not currently allowing the requested SKU/capability combination in that region or subscription. It is not normally resolved by repeating --zone-redundant true.

Zone redundancy depends on all of the following:

Region support and current regional capacity
Purchasing model and service tier
Selected service objective, compute generation and hardware family
Whether that exact configuration supports conversion of an existing database
Subscription-specific restrictions

Since the portal and CLI both fail, newly created East US test databases show the same behavior, and the equivalent deployment succeeds in Central US, the evidence points to an East US capability or provisioning restriction—not corruption of the existing database.

Recommended next steps:

Confirm the database’s exact SKU, service objective, hardware generation and purchasing model—not only the display name “Premium.”
Check the current Azure SQL Database zone-redundancy availability documentation for that exact configuration in East US.
Run the CLI operation with --debug and retain the HTTP status, request ID, correlation ID and complete service error.
Open an Azure support request asking whether zone-redundant provisioning is disabled for that SKU in East US for the subscription. Include the failed request IDs and the successful Central US comparison.If Azure confirms that the combination is unavailable in East US, there is no database-level setting that can override it. The practical alternatives are:

Change to an East US service objective that supports zone redundancy, if one is available.
Deploy a zone-redundant database in a supported region and migrate or replicate the data.
Use an active geo-replication or failover-group design where appropriate. Note that regional replicas and failover groups address regional recovery and are not substitutes for in-region zone redundancy.

Do not make an in-place production SKU change until its cost, maintenance and availability effects have been tested on a copy of the database.

References:

Answer 2

Your results (East US fails for new databases too, Central US works) suggest a subscription restriction in East US. Premium supports zone redundancy, so the tier isn’t the issue. ProvisioningDisabled can also mean a capacity limit, though.

Run the update with --debug and save the full error message and the request/correlation IDs.

Open a support request: Service and subscription limits (quotas) -> SQL Database. Ask for zone-redundant provisioning in East US for your subscription, and include the IDs and the Central US comparison.

Once it’s approved, retry the update. Test on a copy first.

If East US has no capacity, deploy a zone-redundant database in a supported region and migrate. Geo-replication covers regional DR, but it doesn't replace zone redundancy.