PostgresSQL server deleted two weeks ago has not gone away

Open an Azure support request for backend removal of the PostgreSQL Flexible Server, because a deletion that remains unresolved for two weeks requires Azure engineering intervention rather than another CLI deletion attempt.^1^

1. Capture evidence of the original deletion

1. In the Azure portal, go to Monitor → Activity log.
2. Select the subscription that contained the server.
3. Add the filter:
   • Operation: Delete PostgreSQL server (Microsoft.DBforPostgreSQL/flexibleServers/delete)
4. Open the deletion event and select JSON.
5. Save:
   • resourceId
   • submissionTimestamp
   • Operation status
   • Correlation ID
   • Any error details

Microsoft documents this Activity Log filter and these JSON properties for identifying a deleted Flexible Server.^2^

Also capture screenshots of:

• The server’s current Overview or Resource Health page.
• The health event and its timestamp.
• Any Dropping, failed, or unavailable provisioning state.

Do not attempt to restore the server. The documented deleted-server recovery period is only five days, so after two weeks the health message may reflect stale or failed platform state rather than a usable recovery path.^2^

2. Identify the charges precisely

In the portal, open Cost Management + Billing → Cost Management → Cost Analysis:

1. Set the scope to the affected subscription.
2. Set the date range to include several days before deletion through today.
3. Add a Service name filter for Azure Database for PostgreSQL.
4. Add a Meter filter or group by Meter.
5. Group by Resource.
6. Record the meter name, resource ID, usage dates, quantity, and daily cost.

Grouping by meter and resource distinguishes compute charges from storage, networking, or another separately billed item.^3^ The Resource Health event alone does not establish that compute is still accruing charges; the Cost Analysis meter is the relevant evidence.

Export or screenshot the daily charges, especially entries whose usage dates are later than the Activity Log deletion timestamp. Azure recommends reviewing both invoiced Cost Analysis data and audit logs when investigating unexpected charges.^4^

3. Request backend deletion and billing correction

From the affected resource, select Support + Troubleshooting under Help. If the resource cannot be opened, use Help + support → Create a support request. Continue past self-help and select Create a support request.^5^

Submit a Technical case for Azure Database for PostgreSQL Flexible Server with wording such as:

PostgreSQL Flexible Server deletion was submitted at <UTC timestamp> but the resource remains present and continues producing Resource Health events and post-deletion charges. Cloud Shell CLI deletion has already been performed. Please inspect the backend state, complete the server deletion, confirm the effective deletion timestamp, and provide the incident/correlation details needed for billing adjustment.

Include:

• Subscription and resource IDs.
• Server name, resource group, and region.
• Activity Log deletion timestamp, status, and correlation ID.
• Exact Resource Health message and timestamps.
• Cost Analysis export showing post-deletion meter charges.
• Confirmation that deletion through Cloud Shell was already attempted.

Matching PostgreSQL Flexible Server cases stuck in Dropping required backend intervention to complete the drop.^1^

Create a separate Billing support request if the technical ticket does not include charge review, referencing the technical case number and requesting adjustment of validated usage after the effective deletion time. Azure directs unrecognized-charge cases to billing support through an Azure support request.^6^

Creating or managing the support request requires Owner, Contributor, or Support Request Contributor at subscription scope.^7^

References

1. PostgreSQL Flexible Servers stuck in 'Dropping' state - Microsoft Q&A
2. Restore a Deleted Server in Azure Database for PostgreSQL Flexible ...
3. Common cost analysis uses
4. Understand the terms in your Azure usage and charges file
5. Create an Azure support request
6. Cost Management + Billing frequently asked questions (FAQ)
7. Manage an Azure support request