PostgresSQL database stays in Provisioning state for extended period for almost 2 hours then timeout cause a failure.

Question

PostgresSQL database stays in Provisioning state for extended period for almost 2 hours then timeout cause a failure.

Lakshan 0

I am trying to create PostgreSQL Flexible Server. It has been in provisioning state for more than 2 hours and then fails with a timeout error. What could be the reason.

Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-06-08T05:47:04.04+00:00
Hi @Lakshan
Thankyou for reaching microsoft Q&A!

If an Azure Database for PostgreSQL Flexible Server remains in the Provisioning state for an extended period and eventually fails with a timeout, the cause is typically related to one of the following:

Networking configuration issues, especially when deploying with Private Access (VNet Integration). Verify that the delegated subnet, NSGs, route tables, and DNS settings meet the deployment requirements.

Regional capacity or transient platform issues in the selected Azure region. Subscription quotas, Azure Policies, or RBAC restrictions that may be blocking resource creation. Temporary backend deployment failures within the Azure platform.

To troubleshoot, please check:

The Deployment details in the Resource Group and review the exact error message from the failed operation. The Activity Log for any deployment-related errors or correlation IDs. Whether the server is being deployed using Public Access or Private Access (VNet Integration). If using Private Access, confirm that the subnet is properly delegated to PostgreSQL Flexible Server and that all networking prerequisites are met. Try deploying the server in a different Azure region to determine whether the issue is region-specific.

Could you share the following details?

Use different region

Public Access or Private Access deployment Deployment method (Portal, ARM/Bicep, Terraform, CLI, etc.) Complete error message from the failed deployment

This information will help identify whether the issue is related to networking, capacity, subscription restrictions, or a platform-side deployment problem.
Lakshan 0 Reputation points

2026-06-11T03:06:25.71+00:00

This issue has now been resolved. May be its a temporary capacity issue.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-06-12T03:05:58.25+00:00

Thank you for the update. This issue appears to have occurred due to a capacity constraint. Please let us know if you have any questions.

1 answer

Your answer

Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-06-08T05:47:04.04+00:00

Hi @Lakshan
Thankyou for reaching microsoft Q&A!

If an Azure Database for PostgreSQL Flexible Server remains in the Provisioning state for an extended period and eventually fails with a timeout, the cause is typically related to one of the following:

Networking configuration issues, especially when deploying with Private Access (VNet Integration). Verify that the delegated subnet, NSGs, route tables, and DNS settings meet the deployment requirements.

Regional capacity or transient platform issues in the selected Azure region. Subscription quotas, Azure Policies, or RBAC restrictions that may be blocking resource creation. Temporary backend deployment failures within the Azure platform.

To troubleshoot, please check:

The Deployment details in the Resource Group and review the exact error message from the failed operation. The Activity Log for any deployment-related errors or correlation IDs. Whether the server is being deployed using Public Access or Private Access (VNet Integration). If using Private Access, confirm that the subnet is properly delegated to PostgreSQL Flexible Server and that all networking prerequisites are met. Try deploying the server in a different Azure region to determine whether the issue is region-specific.

Could you share the following details?

Use different region

Public Access or Private Access deployment Deployment method (Portal, ARM/Bicep, Terraform, CLI, etc.) Complete error message from the failed deployment

This information will help identify whether the issue is related to networking, capacity, subscription restrictions, or a platform-side deployment problem.
Lakshan 0 Reputation points

2026-06-11T03:06:25.71+00:00

This issue has now been resolved. May be its a temporary capacity issue.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-06-12T03:05:58.25+00:00

Thank you for the update. This issue appears to have occurred due to a capacity constraint. Please let us know if you have any questions.

Answer 1

The most common reasons for a PostgreSQL Flexible Server staying in Provisioning for a long time and then timing out are:

Quota (vCore) limits exceeded
If the deployment would exceed the approved vCore quota for the subscription/region, provisioning can fail after an extended attempt. In such cases, a quota-related error similar to the following is raised:

Operation could not be completed as it results in exceeding approved {0} Cores quota.
To fix this, submit a request to increase the quota for Azure Database for PostgreSQL flexible server and specify the vCores required.
Subscription not registered or restricted in the region
If the subscription is not properly registered with the PostgreSQL resource provider or is restricted from creating PostgreSQL Flexible Servers in the chosen region, provisioning can remain stuck and then fail. Typical errors 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."
- "Location region name is not accepting creation of new Azure Database for PostgreSQL Flexible servers for the subscription subscription id at this time"
  In this case, register the subscription with the PostgreSQL resource provider and/or open a support request under Service and subscription limits.
Region access not enabled for the subscription
Some subscriptions (for example Azure Pass, Azure for Students, MSDN/Visual Studio, sponsorships) have access only to a limited set of regions. If trying to deploy in a region that is not enabled for that subscription, provisioning can fail. Errors include:
- "Subscription name are not allowed to provision in region name."
- "Subscriptions are restricted from provisioning in this region. Please choose a different region."
  To resolve this, either:
- File a request to access a region for Azure Database for PostgreSQL flexible server and specify the vCores to use, or
- Deploy the server in an alternate region that is allowed for the subscription.
Other provisioning or capacity issues in the target region
If capacity or other backend provisioning issues exist in the selected region, the deployment may stay in Provisioning and eventually time out. When this happens repeatedly even after checking quota and region access, open a Region access or capacity-related support request under the Azure PostgreSQL flexible server support topic and specify the vCores and region.

If the server repeatedly fails to provision in the same region, recommended next steps are:

Check for any quota error messages and request a quota increase if needed.
Verify that the subscription is allowed to create PostgreSQL Flexible Servers in that region and request region access if required.
Try deploying to another supported region.
If the issue persists, open an Azure support request for Azure Database for PostgreSQL flexible server with details of the region, vCores, and error messages.

References:

Resolve capacity errors for Azure Database for PostgreSQL