Share via

PostgreSQL Flexible Server ReviveDropped returning 500 InternalServerError — centralus

Tim Millett 20 Reputation points
2026-03-19T05:27:44.53+00:00

We deleted two PostgreSQL Flexible Servers on 2026-03-18 and are attempting

to restore them using the ReviveDropped createMode via REST API with

api-version 2023-03-01-preview as documented. All attempts return HTTP 500

InternalServerError. Note: incident 8ZWZ-610 (ARM deployment failures) was

active during initial attempts — now resolved but still failing.

Servers:

  1. revherobots-bots-prod (centralus, revhero-central) Deleted: 2026-03-18T17:47:09Z resourceId: /subscriptions/3694e2b1-0463-41b8-856c-44e523693df4/ resourceGroups/revhero-central/providers/ Microsoft.DBforPostgreSQL/flexibleServers/revherobots-bots-prod
  2. revherobots-bots (centralus, revhero-central) Deleted: 2026-03-18T17:48:12Z resourceId: /subscriptions/3694e2b1-0463-41b8-856c-44e523693df4/ resourceGroups/revhero-central/providers/ Microsoft.DBforPostgreSQL/flexibleServers/revherobots-bots

Request used:

PUT https://management.azure.com/subscriptions/{sub}/resourceGroups/

revhero-central/providers/Microsoft.DBforPostgreSQL/flexibleServers/

{name}?api-version=2023-03-01-preview

Body:

{

"location": "centralus",

"properties": {

  "restorePointInTime": "2026-03-18T17:32:09Z",

  "createMode": "ReviveDropped",

  "sourceServerResourceId": "..."

}

}

Error tracking IDs:

0190cac1-7afa-40a1-840d-177bbb6b6667

883ec94b-c719-48ae-93c2-3f05a54b82aa

46fe51b4-e6d2-42d1-9f7a-fe03e52ec89a

Subscription: 3694e2b1-0463-41b8-856c-44e523693df4

Backups expire 2026-03-23. Urgent.

Azure Database for PostgreSQL
0 comments No comments

Answer accepted by question author
  1. Saraswathi Devadula 15,850 Reputation points Microsoft External Staff Moderator
    2026-03-19T15:18:47.45+00:00

    Hello **Tim Millett

    **When a server is deleted, database server backups may be retained within the service for up to 5 days.

    We ask that you follow the following documents to restore your server, https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-restore-dropped-server

    pgaudit extension provides detailed audit logging which is not enabled by default.

    Server logs capture (PostgreSQL standard logs) must be enabled explicitly to access logs for troubleshooting, monitoring, and audit-level details.

    Azure monitoring and PostgreSQL logging features are available independently of pgaudit but require server logs capture and diagnostic settings to be enabled.

    Thus, without enabling pgaudit and server logs capture, you cannot find the logs to check the server deletion details.

    https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/security-audit?tabs=portal

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

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