Azure PostgreSQL Flexible Server stuck with terminal provisioning state ‘Failed’ after deletion (ARM ghost resource)

Question

An Azure Database for PostgreSQL Flexible Server was deleted, however Azure continues to show failed operations related to the resource. The Azure Activity Log reports configuration updates failing with “resource operation completed with terminal provisioning state ‘Failed’.”

Attempts to clean up the resource using the Azure Portal and Azure CLI result in ResourceNotFound errors, while Azure Resource Manager still appears to retain a stale or stranded record. No further operations (delete, update, or recreate with the same name) are possible.

This appears to be a known ghost / stranded ARM resource scenario where the service plane resource is removed but ARM metadata is not fully cleaned up..

What is the recommended resolution for clearing this failed provisioning state and removing the stranded ARM record without exposing resource details? Is an ARM cache refresh or backend cleanup by Microsoft required in this case?

Answer 1

Hi Sneh Patel

The server deletion initiated and stuck in the DropInProgress state due to an internal control‑plane issue. Since the deletion could not be completed through the Azure Portal or CLI, we engaged the Azure PostgreSQL backend engineering team. The PG team performed a manual backend cleanup and successfully removed the server from the PostgreSQL service layer. The resource has now been fully dropped from the backend, and the issue is resolved.

Hope this helps, Please let us know if you have any questions and concerns.