Postgres flexible server stuck in starting

Hello Winderson Souza,

Thank you for posting your question in the Microsoft Q&A forum. 

This situation is a known but frustrating behavior within Azure's managed PostgreSQL service, where a server can become trapped in a pending state due to an underlying platform operation that has stalled or failed silently.

The error message indicates the resource management layer has logically locked the server, preventing any new administrative commands including stop, delete, or restore from being processed until the prior, hung operation is cleared by the system.

Unfortunately, there is no direct user-initiated "force stop" command available in the Azure portal, CLI, or PowerShell that can bypass this internal lock. Your only recourse is to open a support ticket with Microsoft Azure, as the support engineering team may possesses the necessary internal tools and permissions to manually intervene on the backend platform. Confirm with the support team if they can terminate the stuck orchestration task, which will release the lock and allow your server to either complete its transition or finally become responsive to your stop or delete commands. While waiting, ensure you have documented the server name, subscription ID, and the timing of the issue to expedite the support process. 

Please, let me know the response helps answer your question? If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. 🙂