This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 27%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGW%3C/text%3E%3C/svg%3E)
We have an Azure Database for PostgreSQL - Flexible Server instance stuck in a dropping state after a failed replica creation and need Azure assistance in removing the server from the backend.
An Azure managed PostgreSQL database service for app development and deployment.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 36%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESH%3C/text%3E%3C/svg%3E)
Hi @Galen Wenger
“Dropping” state hang after the replica failure – I know that can be frustrating. Flexible Server can sometimes get stuck in a Dropping state if there’s a lock or leftover resources from the replica creation.
Verify the server’s exact state
In the portal, go to your PostgreSQL flexible server → Overview and note the Status.
Via Azure CLI:
az postgres flexible-server show \ --resource-group \ --name \ --query "properties.userVisibleState" -o tsv
Trigger an ARM sync on that resource Sometimes ARM metadata gets out of sync and prevents the delete from completing. You can force a sync by running:
az resource invoke-action \ --action "sync" \ --ids "/subscriptions//resourceGroups//providers/Microsoft.DBforPostgreSQL/flexibleServers/"
Attempt a force delete via CLI If the sync doesn’t help, try deleting with no‐wait:
az postgres flexible-server delete \ --resource-group \ --name \ --yes \ --no-wait
Check for lingering dependencies Make sure there are no private endpoints, VNet firewalls or replica resources still attached in that RG. Sometimes a leftover private DNS zone or endpoint blocks the delete. Remove any related DNS records or endpoints first.
Hope that helps get it unblocked! If any of those steps error out or you need deeper digging, let me know the details.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 95%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
Hi @Galen Wenger
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Hi Saraswathi,
Thank you for your replies. When I checked our Azure portal this morning (approximately a day and a half after my post here), the server that had been stuck in a Dropping state for several days is no longer listed. It appears that the issue resolved itself.
Thank you for your help and instructions. I'll add these steps to our internal documentation.
I am glad that your issue is resolved @Galen Wenger
Hi @Galen Wenger
I request you to please try to redeploy the failed replica creation which was failed and let me know if the dropping state gets released or not.
Also, please share the details requested in the private message for further troubleshooting to drop the server.