An Azure managed PostgreSQL database service for app development and deployment.
Hi ,
Thanks for reaching out to Microsoft Q&A.
This typically happens when a long-running or failed internal control plane operation (start/scale/patch/backup) leaves the server in a locked state, so all subsequent actions return ServerBusyWithOtherOperation. You cannot force clear this from the customer side. First, check Activity Log for any ongoing or failed operations and wait ~15 to 30 minutes if something is still in progress. If it remains stuck, this is a backend issue and requires Microsoft intervention to clear the lock or reset the server state. Raise a critical Azure support ticket with server name, region, and timestamp, explicitly asking to “terminate/clear the stuck control plane operation.” As a temporary mitigation (if downtime is critical), consider restoring to a new server from the latest backup or enabling a read replica if already configured.
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.