Hi David Hirst
It looks like the error you're seeing is due to a provisioning failure that left the server in a stuck or "Dropping" state. This is preventing you from either cleaning it up or trying to provision it again.
Here’s what you can do to check if the server still exists in Azure:
az postgres server list [--resource-group]
This will show all existing servers. If the problematic server is still listed, you can manually delete it using:
az resource delete [--resource-group]
[--name]
[--resource-type]
- Don’t try to re-create the resource immediately: After a failed provisioning attempt, the system might still think the resource exists. Trying again too soon can lead to more failures.
- Clear your browser cache or try a different browser: Sometimes the Azure portal behaves unpredictably due to cached data.
- Use a different name if you try again: Even if a deployment fails, the resource name might still be temporarily reserved. Choosing a new name can help avoid conflicts
- Retry creating Postgres SQL server using below Azure CLI
az postgres server create [--admin-password]
[--admin-user]
[--assign-identity]
[--auto-grow {Disabled, Enabled}]
[--backup-retention]
[--geo-redundant-backup {Disabled, Enabled}]
[--infrastructure-encryption {Disabled, Enabled}]
[--location]
[--minimal-tls-version {TLS1_0, TLS1_1, TLS1_2, TLSEnforcementDisabled}]
[--name]
[--public]
[--resource-group]
[--sku-name]
[--ssl-enforcement {Disabled, Enabled}]
[--storage-size]
[--tags]
[--version]
If the issue persists, please don't hesitate to reach out, we're here to help and will assist you further.