Incorporated Reviewer feedback

Author: hariramt

articles/postgresql/TOC.yml

@@ -17,13 +17,13 @@
       - name: Single Server to Flexible Server migration (preview)
         items:
           - name: Single to Flexible server migration (Preview) - Concepts
-            href: concepts-single-to-flexible.md
+            href: migrate/concepts-single-to-flexible.md
           - name: Single to Flexible server migration (Preview) - Migrate using portal
-            href: how-to-migrate-single-to-flex-portal.md
+            href: migrate/how-to-migrate-single-to-flexible-portal.md
           - name: Single to Flexible server migration (Preview)- Migrate using CLI
-            href: how-to-migrate-single-to-flex-cli.md
+            href: migrate/how-to-migrate-single-to-flexible-cli.md
           - name: Single to Flexible server migration (Preview) - Set up Azure AD app using portal
-            href: how-to-setup-aad-app-portal.md    
+            href: migrate/how-to-set-up-azure-ad-app-portal.md
       - name: Migrate data with pg_dump and pg_restore
         href: single-server/how-to-migrate-using-dump-and-restore.md
         displayName: pg_dump, pg_restore

articles/postgresql/migrate/concepts-single-to-flexible.md

@@ -40,7 +40,7 @@ You choose the source server and can select up to eight databases from it. This
 
 The following diagram shows the process flow for migration from Single Server to Flexible Server via the migration tool.
 
-:::image type="content" source="./media/concepts-single-to-flexible/concepts-flow-diagram.png" alt-text="Diagram that shows the migration from Single Server to Flexible Server." lightbox="./media/concepts-single-to-flexible/concepts-flow-diagram.png":::
+:::image type="content" source="./media/concepts-single-to-flexible/concepts-flow-diagram.png" alt-text="Diagram that shows the Migration from Single Server to Flexible Server." lightbox="./media/concepts-single-to-flexible/concepts-flow-diagram.png":::
 
 The steps in the process are:
 
@@ -118,17 +118,17 @@ Before you start using the migration tool:
 
 - If you are using any PostgreSQL extensions on the Single Server, it has to allow-listed on the Flexible Server before initiating the migration using the steps below:
 
-1. Use select command in the Single Server environment to list all the extensions in use.
+  1. Use select command in the Single Server environment to list all the extensions in use.
 
-    ```
-    select * from pg_extension
-    ```
+      ```
+      select * from pg_extension
+      ```
 
-The output of the above command gives the list of extensions currently active on the Single Server
+      The output of the above command gives the list of extensions currently active on the Single Server
 
-2. Enable the list of extensions obtained from step 1 in the Flexible Server. Search for the 'azure.extensions' parameter by selecting the Server Parameters tab in the side pane. Select the extensions that are to be allow-listed and click Save.
+  2. Enable the list of extensions obtained from step 1 in the Flexible Server. Search for the 'azure.extensions' parameter by selecting the Server Parameters tab in the side pane. Select the extensions that are to be allow-listed and click Save.
 
-  :::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-azure-extensions.png" alt-text="Screenshot of PG extension support in the Flexible Server Azure portal." lightbox="./media/concepts-single-to-flexible/single-to-flex-azure-extensions.png":::
+      :::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-azure-extensions.png" alt-text="Screenshot of PG extension support in the Flexible Server Azure portal." lightbox="./media/concepts-single-to-flexible/single-to-flex-azure-extensions.png":::
 
 ### Data and schema migration
 

articles/postgresql/migrate/how-to-migrate-single-to-flexible-cli.md

@@ -55,7 +55,7 @@ az postgres flexible-server migration --help
 
 That command gives you the following output:
 
-:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-cli-help.png" alt-text="Screenshot of Azure C L I help." lightbox="./media/concepts-single-to-flexible/single-to-flex-cli-help.png":::
+:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-cli-help.png" alt-text="Screenshot of Azure Command Line Interface help." lightbox="./media/concepts-single-to-flexible/single-to-flex-cli-help.png":::
 
 The output lists the supported migration commands, along with their actions. Let's look at these commands in detail.
 
@@ -92,7 +92,7 @@ az postgres flexible-server migration create [--subscription]
 For example:
 
 ```azurecli-interactive
-az postgres flexible-server migration create --subscription 5c5037e5-d3f1-4e7b-b3a9-f6bf9asd2nkh0 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1 --properties "C:\Users\Administrator\Documents\migrationBody.JSON"
+az postgres flexible-server migration create --subscription 11111111-1111-1111-1111-111111111111 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1 --properties "C:\Users\Administrator\Documents\migrationBody.JSON"
 ```
 
 The `migration-name` argument used in the `create` command will be used in other CLI commands, such as `update`, `delete`, and `show.` In all those commands, it will uniquely identify the migration attempt in the corresponding actions.
@@ -200,7 +200,7 @@ az postgres flexible-server migration list [--subscription]
 
 The `migration_name` parameter is the name assigned to the migration during the `create` command. Here's a snapshot of the sample response from the CLI command for showing details:
 
-:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-cli-migration-name.png" alt-text="Screenshot of C L I migration name." lightbox="./media/concepts-single-to-flexible/single-to-flex-cli-migration-name.png":::
+:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-cli-migration-name.png" alt-text="Screenshot of Command Line Interface migration name." lightbox="./media/concepts-single-to-flexible/single-to-flex-cli-migration-name.png":::
 
 Note these important points for the command response:
 
@@ -240,7 +240,7 @@ az postgres flexible-server migration update [--subscription]
 To set logical replication on your source server, pass the value `true` to the `initiate-data-migration` property. For example:
 
 ```azurecli-interactive
-az postgres flexible-server migration update --subscription 5c5037e5-d3f1-4e7b-b3a9-f6bf9asd2nkh0 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1 --initiate-data-migration true"
+az postgres flexible-server migration update --subscription 11111111-1111-1111-1111-111111111111 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1 --initiate-data-migration true"
 ```
 
 If you enable it manually, *you still need to issue the preceding `update` command* for the migration to move out of the `WaitingForUserAction` state. The server doesn't need to restart again because that already happened via the portal action.
@@ -260,7 +260,7 @@ az postgres flexible-server migration update [--subscription]
 To give the migration permissions to overwrite any existing data in the target server, you need to pass the value `true` to the `overwrite-dbs` property. For example:
 
 ```azurecli-interactive
-az postgres flexible-server migration update --subscription 5c5037e5-d3f1-4e7b-b3a9-f6bf9asd2nkh0 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1 --overwrite-dbs true"
+az postgres flexible-server migration update --subscription 11111111-1111-1111-1111-111111111111 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1 --overwrite-dbs true"
 ```
 
 #### WaitingForCutoverTrigger
@@ -282,7 +282,7 @@ az postgres flexible-server migration update [--subscription]
 For example:
 
 ```azurecli-interactive
-az postgres flexible-server migration update --subscription 5c5037e5-d3f1-4e7b-b3a9-f6bf9asd2nkh0 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1 --cutover"
+az postgres flexible-server migration update --subscription 11111111-1111-1111-1111-111111111111 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1 --cutover"
 ```
 
 After you use the preceding command, use the command for showing details to monitor if the cutover has finished successfully. Upon successful cutover, migration will move to a `Succeeded` state. Update your application to point to the new Flexible Server target.
@@ -307,7 +307,7 @@ az postgres flexible-server migration delete [--subscription]
 For example:
 
 ```azurecli-interactive
-az postgres flexible-server migration delete --subscription 5c5037e5-d3f1-4e7b-b3a9-f6bf9asd2nkh0 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1"
+az postgres flexible-server migration delete --subscription 11111111-1111-1111-1111-111111111111 --resource-group my-learning-rg --name myflexibleserver --migration-name migration1"
 ```
 
 For more information about this command, use the `help` parameter:

articles/postgresql/migrate/how-to-migrate-single-to-flexible-portal.md

@@ -43,7 +43,7 @@ The migration tool comes with a simple, wizard-based experience on the Azure por
 
 3. In the **Overview** tab of the Flexible Server, on the left menu, scroll down to **Migration (preview)** and select it.
 
-    :::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-preview.png" alt-text="Screenshot of Migration tab details." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-preview.png":::
+    :::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-preview.png" alt-text="Screenshot of the details belonging to Migration tab." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-preview.png":::
 
 4. Select the **Migrate from Single Server** button to start a migration from Single Server to Flexible Server. If this is the first time you're using the migration tool, an empty grid appears with a prompt to begin your first migration.
 
@@ -71,7 +71,7 @@ Alternatively, you can initiate the migration process from the Azure Database fo
 
 5. Once the Flexible Server is deployed, select to open the Flexible Server menu. On the left panel, scroll down to **Migration (preview)** and select it.
 
-    :::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-preview.png" alt-text="Screenshot of Migration tab details." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-preview.png":::
+    :::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-preview.png" alt-text="Screenshot of the details related to Migration tab." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-preview.png":::
 
 6. Select the **Migrate from Single Server** button to start a migration from Single Server to Flexible Server. If this is the first time you're using the migration tool, an empty grid appears with a prompt to begin your first migration.
 
@@ -85,7 +85,7 @@ Alternatively, you can initiate the migration process from the Azure Database fo
 
 The first tab is **Setup**. It has basic information about the migration and the list of prerequisites for getting started with migrations. These prerequisites are the same as the ones listed in the [Migrate from Azure Database for PostgreSQL Single Server to Flexible Server](./concepts-single-to-flexible.md) article. 
 
-:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-setup.png" alt-text="Screenshot of Setup tab details." lightbox="./media/concepts-single-to-flexible/single-to-flex-setup.png":::
+:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-setup.png" alt-text="Screenshot of the details belonging to Setup tab." lightbox="./media/concepts-single-to-flexible/single-to-flex-setup.png":::
 
 **Migration name** is the unique identifier for each migration to this Flexible Server target. This field accepts only alphanumeric characters and does not accept any special characters except a hyphen (-). The name can't start with a hyphen and should be unique for a target server. No two migrations to the same Flexible Server target can have the same name.
 
@@ -155,7 +155,7 @@ After you choose a subnet, select the **Next** button.
 
 The **Review + create** tab summarizes all the details for creating the migration. Review the details and select the **Create** button to start the migration.
 
-:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-review.png" alt-text="Screenshot of migration review." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-review.png":::
+:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-review.png" alt-text="Screenshot of details to review for the migration." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-review.png":::
 
 ## Monitor migrations
 
@@ -165,15 +165,15 @@ After you select the **Create** button, a notification appears in a few seconds
 
 You should automatically be redirected to the **Migration (Preview)** page of Flexible Server. That page has a new entry for the recently created migration.
 
-:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-review-tab.png" alt-text="Screenshot of migration details." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-review-tab.png":::
+:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-review-tab.png" alt-text="Screenshot of recently created migration details." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-review-tab.png":::
 
 The grid that displays the migrations has these columns: **Name**, **Status**,  **Source DB server**, **Resource group**, **Region**, **Version**, **Databases**, and **Start time**. By default, the grid shows the list of migrations in descending order of migration start times. In other words, recent migrations appear on top of the grid.
 
 You can use the refresh button to refresh the status of the migrations.
 
 You can also select the migration name in the grid to see the details of that migration.
 
-:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-grid.png" alt-text="Screenshot of the migration grid." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-grid.png":::
+:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-grid.png" alt-text="Screenshot of the the migration grid containing all migrations." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-grid.png":::
 
 As soon as the migration is created, the migration moves to the **InProgress** state and **PerformingPreRequisiteSteps** substate. It takes up to 10 minutes for the migration workflow to move out of this substate. The reason is that it takes time to create and deploy Database Migration Service, add the IP address on the firewall list of source and target servers, and perform maintenance tasks.
 
@@ -185,7 +185,7 @@ For offline mode, the migration moves to the **Succeeded** state as soon as the
 
 For online mode, the migration moves to the **WaitingForUserAction** state and the **WaitingForCutOver** substate after the **Migrating Data** substate finishes successfully.
 
-:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-status-wait.png" alt-text="Screenshot of migration status." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-status-wait.png":::
+:::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-status-wait.png" alt-text="Screenshot of migration status after clicking on the migration." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-status-wait.png":::
 
 Select the migration name to open the migration details page. There, you should see the substate of **WaitingForCutover**.
 

articles/postgresql/migrate/how-to-setup-azure-ad-app-portal.md renamed to articles/postgresql/migrate/how-to-set-up-azure-ad-app-portal.md

@@ -46,7 +46,7 @@ An Azure AD app helps with role-based access control (RBAC). The migration infra
 
 9. In the **Value** column, copy the Azure AD app secret. You can copy the secret only during creation. If you miss this step, you'll need to delete the secret and create another one for future tries.
 
-    :::image type="content" source="./media/how-to-setup-azure-ad-app-portal/azure-ad-client-secret-value.png" alt-text="Screenshot of copying a client secret." lightbox="./media/how-to-setup-azure-ad-app-portal/azure-ad-client-secret-value.png":::
+    :::image type="content" source="./media/how-to-setup-azure-ad-app-portal/azure-ad-client-secret-value.png" alt-text="Screenshot that displays copying of a client secret." lightbox="./media/how-to-setup-azure-ad-app-portal/azure-ad-client-secret-value.png":::
 
 ## Add contributor privileges to an Azure resource
 
@@ -78,7 +78,7 @@ The following steps add contributor privileges to a Flexible Server target. Repe
 
 4.  On the **Members** tab, keep the default option of **User, group, or service principal** for **Assign access to**. Click **Select Members**, search for your Azure AD app, and then click **Select**.
 
-    :::image type="content" source="./media/how-to-setup-azure-ad-app-portal/azure-ad-review-and-assign.png" alt-text="Screenshot of the Members tab." lightbox="./media/how-to-setup-azure-ad-app-portal/azure-ad-review-and-assign.png":::
+    :::image type="content" source="./media/how-to-setup-azure-ad-app-portal/azure-ad-review-and-assign.png" alt-text="Screenshot of the Members tab to be added as Contributor." lightbox="./media/how-to-setup-azure-ad-app-portal/azure-ad-review-and-assign.png":::
 
 
 ## Next steps