Azure Database for PostgreSQL: Deployment Failure in West Europe — Subscription Restriction Issue

Question

Problem description

I am trying to provision two private Azure Database for PostgreSQL flexible servers in the West Europe region under my Sponsorship subscription, but both creation attempts are failing. The provisioning process through Azure CLI does not complete successfully, blocking my production deployment. The failure appears to be related to regional restrictions or subscription limitations, but I have not received a specific error message or code that clarifies the issue.

Environment

Service: Azure Database for PostgreSQL flexible server; Region: West Europe; Deployment method: Azure CLI; Subscription type: Sponsorship; No specific server configuration details provided.

What I've already tried

I have not tried any troubleshooting steps; the case details only describe the initial provisioning failure and the impact on deployment.

Current status

I am seeking assistance to understand the cause of the provisioning failure and to determine whether regional restrictions can be lifted or if additional configuration is required to enable PostgreSQL flexible server provisioning in West Europe under my Sponsorship subscription.

Answer 1

..........

Answer 2

Hi @mo@info

1. Resource Provider Not Registered Shell az provider register --namespace Microsoft.DBforPostgreSQL
2. Regional Capacity Restrictions Some VM sizes or service SKUs may not be available in West Europe at the time of deployment.
3. Subscription Quotas or Policy Restrictions Sponsorship subscriptions can have quota limits or Azure Policy restrictions that prevent certain PostgreSQL SKUs, networking options, or HA configurations.
4. Networking Configuration Issues Deployments using private access, delegated subnets, or private DNS zones frequently fail if prerequisite networking resources are not configured correctly.
5. Unsupported SKU/Tier Selection Certain compute tiers or availability features may not be available for the selected region or subscription.

To diagnose further, run:

az postgres flexible-server list \
 --output table

or, if deployment failed, check the deployment operation details:

az deployment group list \
 --resource-group <resource-group-name> \
 --output table

and retrieve the detailed error:

az monitor activity-log list \
 --max-events 20 \
 --output table
``

The most useful next step is the exact Azure CLI command you executed and the full error message returned. With that, I can help identify the specific cause and provide the fix.

Thanks.