Region Issue on Azure

The deployment error code, subscription offer type, and product-specific region-access request will determine and resolve whether this subscription can provision PostgreSQL Flexible Server or Azure SQL Database in South India.

1. Confirm the restriction from the failed deployment

Because Microsoft.DBforPostgreSQL is already registered and no subscription policy blocks the deployment, do not repeat those checks.

1. In the Azure portal, open Resource groups and select the resource group used for the failed deployment.
2. Open Activity log, filter for the failed create operation, and select it to view its error code and message.
3. Alternatively, open Settings → Deployments → failed deployment → Error details. Azure exposes the underlying deployment error there.^1^
4. Save the complete error message, timestamp, and correlation ID for the access request.

These messages indicate a region-access restriction rather than an ordinary resource quota:

• Your subscription does not have access to create a server in the selected region.
• Provisioning is restricted in this region.
• Location 'South India' is not accepting creation ... for the subscription ...
• ProvisionNotSupportedForRegion

For PostgreSQL, Microsoft directs these cases to a request that enables the specific region.^2^ Azure SQL documents the same distinction between Region access and an exceeded compute quota.^3^

South India supports PostgreSQL Flexible Server, so general product availability and access for this particular subscription are separate questions.^4^ Existing App Service and VNet resources in South India therefore do not establish database-service access.

2. Check whether the subscription offer is restricted

In the portal, open Subscriptions → your subscription → Overview/Properties and inspect the Offer or subscription type. An Azure offer is the commercial/program type associated with the subscription.^5^

Azure Pass, Azure for Students, Visual Studio/MSDN, Microsoft for Startups/Sponsorship, and several other Azure Program offers have access to a limited set of regions. South India is explicitly listed among the affected regions for both PostgreSQL Flexible Server and Azure SQL.^2^^3^

If the subscription belongs to one of those programs, request access or use an alternate region. Approval remains subject to review and regional capacity.

3. Request PostgreSQL Flexible Server access

Submit a dedicated PostgreSQL request:

1. Go to Azure portal → Help + support → Create a support request.
2. Enter:
   • Issue type: Service and subscription limits (quotas)
   • Subscription: the affected subscription
   • Quota type: Azure Database for PostgreSQL flexible server
3. Under Additional details, select Enter details.
4. Choose the relevant Region access quota type.
5. Set Location to South India and specify the required compute series and vCores.
6. Include the exact deployment error, correlation ID, workload purpose, expected deployment date, and whether high availability or a particular availability zone is required.
7. Complete the contact details and select Review + Create → Create.

The PostgreSQL team reviews and approves or denies the request; the documented processing target for quota requests is 24–48 hours.^6^

If the error names only an unavailable availability zone or SKU, first try another zone or supported SKU; those are different from subscription-level region access.^2^

4. Request Azure SQL Database access separately

Azure SQL uses Microsoft.Sql, not Microsoft.DBforPostgreSQL. If its deployment fails, first check Subscriptions → your subscription → Resource providers → Microsoft.Sql; registration is required for Azure SQL deployments.^3^

Then submit a separate request:

1. Open Help + support → Create a support request and search for quota.
2. Select None of the above → Service and subscription limits (quotas).
3. Select the subscription, then choose SQL Database as the problem type.
4. Create the support request and open Enter details.
5. In Quota details, select:
   • Quota type: Region access
   • Location: South India
   • Expected Consumption: expected vCores
6. Save, add the deployment evidence and contact information, and create the request.

Region access is per subscription and region. For DTU-based planning, Microsoft uses approximately 1 vCore = 100–125 DTU when entering expected consumption.^7^

Do not select vCores per subscription unless the error explicitly says the existing compute/DTU quota would be exceeded. Region access is the correct request for “subscription does not have access” or “provisioning is restricted” errors.

References

1. Find error codes
2. Resolve capacity errors for Azure Database for PostgreSQL
3. Resolve capacity errors with Azure SQL Database or Azure SQL Managed Instance
4. What is Azure Database for PostgreSQL flexible server?
5. Change your Azure subscription to a different offer
6. Request quota increases for Azure Database for PostgreSQL flexible server
7. Request quota increases for Azure SQL Database and SQL Managed Instance