Recover dropped database

Question

Summary:

On February 12, 2026, a Terraform apply operation destroyed and recreated a PostgreSQL Flexible Server (kc-next-app-test-db) in our subscription. The previous server instance contained a database named defaultdb with application data. The new server instance was created with the same name but without the defaultdb database, resulting in data loss. We are requesting recovery of the previous server instance's data.

1. ~16:39 — The original server instance was still active (confirmed by a configuration update event logged in Azure Activity Log: flexibleServers/configurations/require_secure_transport/write).
2. Between 16:39 and 17:02 — Terraform executed a destroy on the original server instance as part of a module restructure (git commit b0831b0 — "chore: remove next_app demo and prod environments").
3. 17:02:30 — Terraform created a new server instance with the same name kc-next-app-test-db (flexibleServers/write — Started).
4. 17:06:37 — New server creation completed (flexibleServers/write — Succeeded).
5. 17:08:08 — Earliest restore point of the new server instance (confirming it is a fresh server with no prior data).

Evidence that the server was recreated (not updated in-place):

• The new server's systemData.createdAt is 2026-02-12T17:02:45.460511+00:00, which is after the last known activity on the old server.
• The new server has no defaultdb database — only system databases (postgres, azure_maintenance, azure_sys).
• The earliest backup restore point is 2026-02-12T17:08:08, meaning no backup data exists from before 17:02 on the new instance.
• Restoring the new server to its earliest point confirmed it never contained defaultdb.

What we have already tried:

1. Searched Azure Activity Log for flexibleServers/delete events — no delete event was found (possibly because Terraform executed the delete and create in rapid succession, or the log was not retained).
2. Restored the current server to its earliest available point (kc-next-app-test-db-restored) — the restored copy does not contain defaultdb.
3. Created a second restore (kc-next-app-test-db-restored-v2) to a different point — also missing defaultdb.
4. Searched for deleted server Resource IDs via CLI and REST API — no results found via customer-facing APIs.

Request:

We are requesting Microsoft's assistance to recover the previous instance of the server kc-next-app-test-db that was deleted on February 12, 2026, between approximately 16:39 and 17:02 UTC. The server was located in Brazil South under resource group kc_next_app_resource_group. We specifically need the defaultdb database and all its data restored.

If possible, please restore the deleted server instance to a new server name such as kc-next-app-test-db-recovered in the same resource group and region.

Summary:

On February 12, 2026, a Terraform apply operation destroyed and recreated a PostgreSQL Flexible Server (kc-next-app-test-db) in our subscription. The previous server instance contained a database named defaultdb with application data. The new server instance was created with the same name but without the defaultdb database, resulting in data loss. We are requesting recovery of the previous server instance's data.

1. ~16:39 — The original server instance was still active (confirmed by a configuration update event logged in Azure Activity Log: flexibleServers/configurations/require_secure_transport/write).
2. Between 16:39 and 17:02 — Terraform executed a destroy on the original server instance as part of a module restructure (git commit b0831b0 — "chore: remove next_app demo and prod environments").
3. 17:02:30 — Terraform created a new server instance with the same name kc-next-app-test-db (flexibleServers/write — Started).
4. 17:06:37 — New server creation completed (flexibleServers/write — Succeeded).
5. 17:08:08 — Earliest restore point of the new server instance (confirming it is a fresh server with no prior data).

Evidence that the server was recreated (not updated in-place):

• The new server's systemData.createdAt is 2026-02-12T17:02:45.460511+00:00, which is after the last known activity on the old server.
• The new server has no defaultdb database — only system databases (postgres, azure_maintenance, azure_sys).
• The earliest backup restore point is 2026-02-12T17:08:08, meaning no backup data exists from before 17:02 on the new instance.
• Restoring the new server to its earliest point confirmed it never contained defaultdb.

What we have already tried:

1. Searched Azure Activity Log for flexibleServers/delete events — no delete event was found (possibly because Terraform executed the delete and create in rapid succession, or the log was not retained).
2. Restored the current server to its earliest available point (kc-next-app-test-db-restored) — the restored copy does not contain defaultdb.
3. Created a second restore (kc-next-app-test-db-restored-v2) to a different point — also missing defaultdb.
4. Searched for deleted server Resource IDs via CLI and REST API — no results found via customer-facing APIs.

Request:

We are requesting Microsoft's assistance to recover the previous instance of the server kc-next-app-test-db that was deleted on February 12, 2026, between approximately 16:39 and 17:02 UTC. The server was located in Brazil South under resource group kc_next_app_resource_group. We specifically need the defaultdb database and all its data restored.

If possible, please restore the deleted server instance to a new server name such as kc-next-app-test-db-recovered in the same resource group and region.

Answer 1

Hi Brian Stefanovich,
Thankyou for the details, Could you please go through the attached KB article.
https://learn.microsoft.com/en-us/azure/postgresql/backup-restore/how-to-restore-dropped-server

Hope this helps, Please let us know if you have any questions and concerns.