An Azure managed PostgreSQL database service for app development and deployment.
Stop submitting updates to this server and request Microsoft backend recovery, because the persistent Updating/ServerIsBusy state cannot be cleared through a documented customer-facing PostgreSQL Flexible Server cancellation operation.
Recover the stuck server
Similar Flexible Server scale operations that remained in Updating were recovered only after Microsoft restarted unhealthy backend components or containers.^1^^2^ That is a close symptom match, but only Microsoft can determine whether the same backend fault affects this server.
- Do not retry the scale, restart, stop, or another write operation.
The second request already returnedServerIsBusy; additional writes will not supersede the accepted operation. - Check the server’s Resource Health page:
- Azure portal → PostgreSQL flexible server → Resource health.
- If it shows Unavailable due to a platform event, select the support option from that page. Microsoft states that an unavailable resource affected by a platform event can open a support request without a support agreement.^3^
- If it shows Available, select Report incorrect health status and provide the start time, operation, and correlation ID. This submits the health signal for reassessment; it does not guarantee that a technical support case will be created.
- Check Azure portal → Service Health → Service issues and Health advisories.
Service Health is subscription-specific and can expose incidents too narrow to appear on the public Azure status page.^4^ If an applicable incident exists, follow it there; a free recovery ticket can be raised for up to 72 hours after a service disruption is mitigated.^5^ - If Resource Health remains Available and no incident applies, the official remaining paths are:
- Post a sanitized Microsoft Q&A case and request moderator/product-team escalation. Include the UTC timeline, region/zone, old and requested SKUs,
Updatingstate,ServerIsBusy, and correlation ID. Do not post the subscription ID or resource ID publicly. - Ask the subscription owner or tenant administrator whether the organization has an Azure support agreement that can be linked to the subscription.
- If neither route is available, obtain an eligible paid support plan for guaranteed technical case handling. The support request should ask Microsoft to complete or roll back the existing operation and return provisioning state to
Ready, not initiate another scale request.
- Post a sanitized Microsoft Q&A case and request moderator/product-team escalation. Include the UTC timeline, region/zone, old and requested SKUs,
Burstable availability in East US 2
The current published Azure Database for PostgreSQL Flexible Server regional table marks Burstable as unsupported in East US 2.^6^ Therefore, no East US 2 availability zone can presently be recommended for Standard_B1ms from public documentation.
az postgres flexible-server list-skus showing B1ms in zones 2–4 does not prove that PostgreSQL can allocate that SKU at the moment. Microsoft documents that SKU availability can differ by region and can also be temporarily unavailable; for SkuNotAvailable, the supported response is to select another SKU type.^7^
Only Microsoft can confirm live, subscription-specific, zone-level capacity. Given both the November 15 SkuNotAvailable result and the regional support table, keep the server on a supported General Purpose SKU after recovery rather than retrying B1ms. The existing VNet requirement constrains the region, but it does not establish that Burstable capacity exists in any East US 2 zone.
Cancellation and Terraform state
No supported customer-facing cancellation mechanism is documented for a PostgreSQL Flexible Server compute-scaling operation. The documented command starts a scale operation but provides no corresponding compute-scale cancel command.^8^ Migration cancellation commands apply only to PostgreSQL migration workflows and must not be used for compute scaling.
Terraform’s timeout stopped waiting locally; it did not cancel the Azure operation. Leave the configured SKU unchanged until Azure returns the server to Ready. After Microsoft recovery:
- Run
az postgres flexible-server showand confirmstateisReady. - Confirm which SKU Azure retained.
- Refresh Terraform state.
- Set
sku_nameto that recovered SKU before the next plan, preventing Terraform from immediately retrying B1ms.
Compute scaling normally provisions replacement compute, attaches the existing storage, and restarts the database before accepting connections.^9^ The application continuing to run suggests the original General Purpose data plane remains active, but it does not mean the control-plane operation has completed.
References
- Azure PostgreSQL server is stuck in 'updating' state - Microsoft Q&A
- PostgreSQL Flexible Server stuck on change Compute and Storage tier operation - Microsoft Q&A
- Azure Resource Health FAQ
- What is Azure Service Health?
- What to do during an Azure service disruption
- What is Azure Database for PostgreSQL flexible server?
- Resolve capacity errors for Azure Database for PostgreSQL flexible server
- Scale compute in Azure Database for PostgreSQL flexible server
- Overview of business continuity in Azure Database for PostgreSQL flexible server