An Azure managed PostgreSQL database service for app development and deployment.
Hi ,
Thanks for reaching out to Microsoft Q&A.
This is a known control plane lock scenario in azure db for PostgreSQL flexible server where a longrunning or failed compute/storage scaling operation leaves the server stuck in an “updating” state, blocking further actions. Since no activity logs or health events are visible and you cannot cancel or retry the operation from the portal or CLI, this is not user-recoverable. The only resolution is backend intervention by microsoft to clear the stuck operation or force-complete/rollback it. Given the duration (19+ hours), this has already exceeded normal SLA for such operations. You should immediately raise a Sev A (prod down) support ticket under your developere plan and include server name, region, subscription ID, and timestamp of the operation; request “backend unlock of stuck scaling operation.” microsoft support can manually reset the provisioning state or migrate the server if needed. In parallel, if this is critical, consider restoring to a point-in-time or creating a replica (if possible) to regain access while the issue is being fixed.
Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.