Flexible Server stuck in Dropping – RP returns 404 on delete, backend purge required

Question

My PostgreSQL Flexible Server has been stuck in Dropping state for over 48 hours.

A GET on api-version=2024-08-01 still returns properties.state = Dropping with a valid FQDN. Any management operation (Delete / Start / Stop) shows as Started then immediately fails with 404 Not Found.

Delete correlation IDs: 752c955d-0b52-4a57-a2a8-f88616c99ffb, 1ede57db-0a83-4bd7-81c1-1fec001ef883, c7ca6187-3bd0-4522-9d02-2eb762fd5324, b6c951f7-902e-4124-b3a6-a3f332af074f

I've confirmed the RP is registered, there are no locks, and I've tried deleting via Portal, CLI, and ARM REST. I also deleted the parent Resource Group — it succeeded, but the flexible server remains. This looks like a control-plane inconsistency where ARM still surfaces the resource but the RP backend has already lost track of it.

Requesting backend intervention to either clear the stuck operation or force-purge the record from the RP. This is a developer subscription so I can't open a paid support ticket.

Answer 1

Hi Brosowski, Dmitri

The PostgreSQL Flexible Server became stuck in Dropping state due to a control-plane synchronization issue between Azure Resource Manager (ARM) and the PostgreSQL service backend. The backend had already removed the server record, but ARM did not receive the final completion signal and continued showing the resource as existing.

Because of this state mismatch, all management operations returned 404 Not Found, and the resource could not be removed through standard methods.

The PG team resolved the issue by manually clearing the orphaned backend metadata, restoring consistency across the platform.

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