Dominic Lee hi, thx for sharing urs issue here at Q&A portal,
its so hard to tell from only the IDs, but most PostgreSQL delete failures in Azure come down to locks, dependencies, permissions, or a stuck backend operation. If this is Azure Database for PostgreSQL Flexible Server, make sure u are deleting the right resource type. It’s not ‘Azure SQL’ PostgreSQL has its own resource provider. Small naming thing, but it matters when opening support. Common blockers could be delete lock on the server/resource group, private endpoint still attached, backup/restore or scaling op in progress, replica relationship, VNet/subnet dependency, or missing permission like Microsoft.DBforPostgreSQL/flexibleServers/delete.
Check Activity Log for the failed delete first. The real reason is usually there, not in the portal pop-up.
az monitor activity-log list \
--correlation-id '<correlation-id>'
For the resource itself
az resource show \
--ids '<postgres-resource-id>' \
--query "{state:properties.state, provisioningState:properties.provisioningState}"
If there’s a lock
az lock list --resource-group '<rg>'
https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-delete-server
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources
https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-delete-resource
If Activity Log only shows generic failure and the server is stuck in Deleting or Updating, open a PostgreSQL support case w/ the Session ID, Activity ID, Correlation ID, server resource ID, region, and UTC time of the failed delete. That’s likely backend cleanup, not something u can fix from psql.
rgds,
Alex
&
If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal