From 381e8cec37c6fb9c2a23f8bc27fc03e43d39dbb6 Mon Sep 17 00:00:00 2001
From: Paul Haefeli <47189020+paulhaefeli@users.noreply.github.com>
Date: Tue, 18 Mar 2025 12:09:18 -0500
Subject: [PATCH 1/2] Update how-to-restore-dropped-server.md

We are recommending they add time to the dropped time when restoring, instead of subtracting. Corrected document to suggest you subtract time from the drop time, to ensure the server is correctly restored.
---
 .../flexible-server/how-to-restore-dropped-server.md      | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/articles/postgresql/flexible-server/how-to-restore-dropped-server.md b/articles/postgresql/flexible-server/how-to-restore-dropped-server.md
index dc511714ef..62cd5b53bb 100644
--- a/articles/postgresql/flexible-server/how-to-restore-dropped-server.md
+++ b/articles/postgresql/flexible-server/how-to-restore-dropped-server.md
@@ -43,28 +43,28 @@ To restore a dropped Azure Database for PostgreSQL flexible server instance, you
 
 1. Provide the **resourceGroupName**, **serverName** (Target server name), **subscriptionId** properties, based on the resourceId attribute JSON value captured in the preceding step 3. The api-version property is prepopulated and can be left alone.
 
-1. Go to **Request Body** section and paste the following replacing the "Dropped server Location"(for example, CentralUS, EastUS etc.), "submissionTimestamp", and "resourceId". For "pointInTimeUTC", specify a value of "submissionTimestamp" plus **5 minutes** to ensure the command doesn't error out.
+1. Go to **Request Body** section and paste the following replacing the "Dropped server Location"(for example, CentralUS, EastUS etc.), "submissionTimestamp", and "resourceId". For "pointInTimeUTC", specify a value of "submissionTimestamp" minus **5 minutes** to ensure the command doesn't error out.
 
     ```json
       {
         "location": "Dropped Server Location",
         "properties":
         {
-          "pointInTimeUTC": "submissionTimestamp + 10 minutes",
+          "pointInTimeUTC": "submissionTimestamp - 10 minutes",
           "createMode": "ReviveDropped",
           "sourceServerResourceId": "resourceId"
         }
       }
     ```
     
-    For example, if the submission timestamp is 2023-06-15T15:58:02Z, we recommend adding a minimum of 10 minutes to restore point in time 2023-06-15T16:05:02Z and ensure that you're changing three parameters (location,pointInTimeUTC,sourceServerResourceId) as per your restore requirements. 
+    For example, if the submission timestamp is 2023-06-15T15:58:02Z, we recommend subtracting a minimum of 10 minutes to restore point in time 2023-06-15T15:48:02Z and ensure that you're changing three parameters (location,pointInTimeUTC,sourceServerResourceId) as per your restore requirements. 
     
       ```json
           {
           "location": "WestUS",
           "properties":
           {
-            "pointInTimeUTC": "2023-06-15T16:08:02Z",
+            "pointInTimeUTC": "2023-06-15T15:48:02Z",
             "createMode": "ReviveDropped",
             "sourceServerResourceId": "/subscriptions/ffffffff-ffff-ffff-ffff-ffffffffffff/resourceGroups/SourceResourceGroup-Name/providers/Microsoft.DBforPostgreSQL/flexibleServers/SourceServer-Name"
           }

From 6d060ceec0a5dad329ebf6611ce356803d7533c1 Mon Sep 17 00:00:00 2001
From: Paul Haefeli <47189020+paulhaefeli@users.noreply.github.com>
Date: Tue, 18 Mar 2025 16:41:42 -0500
Subject: [PATCH 2/2] Update how-to-restore-dropped-server.md

---
 .../postgresql/flexible-server/how-to-restore-dropped-server.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/postgresql/flexible-server/how-to-restore-dropped-server.md b/articles/postgresql/flexible-server/how-to-restore-dropped-server.md
index 62cd5b53bb..67b981a1da 100644
--- a/articles/postgresql/flexible-server/how-to-restore-dropped-server.md
+++ b/articles/postgresql/flexible-server/how-to-restore-dropped-server.md
@@ -43,7 +43,7 @@ To restore a dropped Azure Database for PostgreSQL flexible server instance, you
 
 1. Provide the **resourceGroupName**, **serverName** (Target server name), **subscriptionId** properties, based on the resourceId attribute JSON value captured in the preceding step 3. The api-version property is prepopulated and can be left alone.
 
-1. Go to **Request Body** section and paste the following replacing the "Dropped server Location"(for example, CentralUS, EastUS etc.), "submissionTimestamp", and "resourceId". For "pointInTimeUTC", specify a value of "submissionTimestamp" minus **5 minutes** to ensure the command doesn't error out.
+1. Go to **Request Body** section and paste the following replacing the "Dropped server Location"(for example, CentralUS, EastUS etc.), "submissionTimestamp", and "resourceId". For "pointInTimeUTC", specify a value of "submissionTimestamp" minus **10 minutes** to ensure the command doesn't error out.
 
     ```json
       {