Share via

Azure PostgreSQL Flexible Server stuck in "DROPPING" state

mrb777-1232 25 Reputation points
2025-05-29T06:03:58.8366667+00:00

Hello,

A couple of resource groups with a VNet and Azure PostgreSQL Flexible Server were deployed yesterday. Due to misconfigurations, a decision was made to remove the entire resource groups, including the resources.

Unfortunately, Azure is unable to delete the database and resource group. The database is stuck in a DROPPING state and does not appear in the Azure Portal. However, when attempting to deploy a resource with the same name using Bicep, the following error is encountered: Specified server name is already used by another server. Please use a different name.

User's image

What steps can be taken to remove the stuck databases? Additionally, what measures can be implemented to avoid this issue in the future? It is frustrating that database removal can lead to such complications.

Thank you in advance!

Azure Database for PostgreSQL
Accepted answer
  1. Mallaiah Sangi 1,060 Reputation points Microsoft External Staff Moderator
    2025-06-03T11:32:29.52+00:00

    Hi mrb777

    Following up on the discussion, the Azure Database for PostgreSQL Flexible Server in the Azure portal is currently stuck in the dropping state.As mentioned, we attempted to drop the server from the backend.

    I hope this has been helpful!

    Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

    If this answers your query, do click Accept Answer and Upvote for was this answer helpful.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.