Single to Flexible migration docs-8

Author: sr-msft

articles/postgresql/TOC.yml

@@ -14,15 +14,15 @@
   items:
   - name: Migration
     items:
-      - name: Single Server to Flexible Server migration (Preview)
+      - name: Single Server to Flexible Server migration (preview)
         items:
           - name: Single to Flexible - Concepts
             href: concepts-single-to-flexible.md
-          - name: Single to Flexible - migrate using Portal
+          - name: Single to Flexible - Migrate using portal
             href: how-to-migrate-single-to-flex-portal.md
-          - name: Single to Flexible - migrate using CLI
+          - name: Single to Flexible - Migrate using CLI
             href: how-to-migrate-single-to-flex-cli.md
-          - name: Single to Flexible - Setup AAP App using Portal
+          - name: Single to Flexible - Set up Azure AD app using portal
             href: how-to-setup-aad-app-portal.md
       - name: Migrate data with pg_dump and pg_restore
         href: howto-migrate-using-dump-and-restore.md

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

@@ -7,20 +7,19 @@ ms.author: shriramm
 ms.service: postgresql
 ms.topic: conceptual
 ms.date: 05/11/2022
+ms.custom: "mvc, references_regions"
 ---
 
 # Migrate from Azure Database for PostgreSQL Single Server to Flexible Server (Preview)
 
-## Overview
-
 >[!NOTE]
 > Single Server to Flexible Server migration feature is in public preview.
 
 Azure Database for PostgreSQL Flexible Server provides zone redundant high availability, control over price, and control over maintenance window.  Single to Flexible Server Migration feature enables customers to migrate their databases from Single server to Flexible. See this [documentation](./flexible-server/concepts-compare-single-server-flexible-server.md) to understand the differences between Single and Flexible servers. Customers can initiate migrations for multiple servers and databases in a repeatable fashion using this migration feature. This feature automates most of the steps needed to do the migration and thus making the migration journey across Azure platforms as seamless as possible. The feature is provided free of cost for customers.
 
 Single to Flexible server migration is enabled in **Preview** in  Australia Southeast, Canada Central, Canada East, East Asia, North Central US, South Central US, Switzerland North, UAE North, UK South, UK West, West US, and Central US.
 
-## How does the migration feature work?
+## Overview
 
 Single to Flexible server migration feature provides an inline experience to migrate databases from Single Server (source) to Flexible Server (target).
 
@@ -100,18 +99,18 @@ Follow the steps provided in this section before you get started with the single
 
 - **Source Server pre-requisites** - You must [enable logical replication](./concepts-logical.md) on the source server.
 
-    :::image type="content" source="./media/concepts-single-to-flex/logical-replication-support.png" alt-text="Logical replication from Azure Portal" lightbox="./media/concepts-single-to-flex/logical-replication-support.png":::
+    :::image type="content" source="./media/concepts-single-to-flex/logical-replication-support.png" alt-text="Logical replication from Azure portal" lightbox="./media/concepts-single-to-flex/logical-replication-support.png":::
 
 >[!NOTE]
 > Enabling logical replication will require a server reboot for the change to take effect.
 
-- **Azure Active Directory App set up** - It is a critical component of the migration feature. AAD App helps with role-based access control as the migration feature needs access to both the source and target servers. See [How to setup and configure AAD App](./how-to-setup-aad-app-portal.md) for step-by-step process.
+- **Azure Active Directory App set up** - It is a critical component of the migration feature. Azure AD App helps with role-based access control as the migration feature needs access to both the source and target servers. See [How to setup and configure Azure AD App](./how-to-setup-aad-app-portal.md) for step-by-step process.
 
 ### Data and schema migration
 
-Once all these pre-requisites are taken care of, you can do the migration. This automated step involves schema and data migration using Azure Portal or Azure CLI.
+Once all these pre-requisites are taken care of, you can do the migration. This automated step involves schema and data migration using Azure portal or Azure CLI.
 
-- [Migrate using Azure Portal](./how-to-migrate-single-to-flex-portal.md)
+- [Migrate using Azure portal](./how-to-migrate-single-to-flex-portal.md)
 - [Migrate using Azure CLI](./how-to-migrate-single-to-flex-cli.md)
 
 ### Post migration
@@ -130,19 +129,19 @@ Once all these pre-requisites are taken care of, you can do the migration. This
 
 ## Limitations
 
-### Size Limitations
+### Size limitations
 
 - Databases of sizes up to 1TB can be migrated using this feature. To migrate larger databases or heavy write workloads, reach out to your account team or reach us @ [email protected].
 
 - In one migration attempt, you can migrate up to eight user databases from a single server to flexible server. In case you have more databases to migrate, you can create multiple migrations between the same single and flexible servers.
 
-### Performance Limitations
+### Performance limitations
 
 - The migration infrastructure is deployed on a 4 vCore VM which may limit the migration performance. 
 
 - The deployment of migration infrastructure takes ~10-15 minutes before the actual data migration starts - irrespective of the size of data or the migration mode (online or offline).
 
-### Replication Limitations
+### Replication limitations
 
 - Single to Flexible Server migration feature uses logical decoding feature of PostgreSQL to perform the online migration and it comes with the following limitations. See PostgreSQL documentation for [logical replication limitations](https://www.postgresql.org/docs/10/logical-replication-restrictions.html).
   - **DDL commands** are not replicated.
@@ -153,7 +152,7 @@ Once all these pre-requisites are taken care of, you can do the migration. This
 
 - Logical decoding will use resources in the source single server. Consider reducing the workload or plan to scale CPU/memory resources at the Source Single Server during the migration.
 
-### Other Limitations
+### Other limitations
 
 - The migration feature migrates only data and schema of the single server databases to flexible server. It does not migrate other features such as server parameters, connection security details, firewall rules, users, roles and permissions. In other words, everything except data and schema must be manually configured in the target flexible server.
 
@@ -165,7 +164,7 @@ Once all these pre-requisites are taken care of, you can do the migration. This
 
 - The migration feature does not include assessment of your single server. 
 
-## Best Practices
+## Best practices
 
 - As part of discovery and assessment, take the server SKU,  CPU usage, storage, database sizes, and extensions usage as some of the critical data to help with migrations.
 - Plan the mode of migration for each database. For less complex migrations and smaller databases, consider offline mode of migrations.

articles/postgresql/flexible-server/overview.md

@@ -130,7 +130,7 @@ $ New Zone-redundant high availability deployments are temporarily blocked in th
 
 $$ New server deployments are temporarily blocked in these regions. Already provisioned servers are fully supported.
 
-** Zone-redundant high availability can now be deployed when you provision new servers in these regions. Pre-existing servers deployed in AZ with *no preference* (which you can check on the Azure Portal), the standby will be provisioned in the same AZ. To configure zone-redundant high availability, perform a point-in-time restore of the server and enable HA on the restored server.
+** Zone-redundant high availability can now be deployed when you provision new servers in these regions. Pre-existing servers deployed in AZ with *no preference* (which you can check on the Azure portal), the standby will be provisioned in the same AZ. To configure zone-redundant high availability, perform a point-in-time restore of the server and enable HA on the restored server.
 
 <!-- We continue to add more regions for flexible server. -->
 > [!NOTE]

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

@@ -18,14 +18,14 @@ This quick start article shows you how to use Single to Flexible Server migratio
 
 ## Before you begin
 
-1. If you are new to Microsoft Azure, [create an account](https://azure.microsoft.com/free/) to evaluate our offerings. New customers get $200 in free credits to run, test and deploy workloads.
+1. If you are new to Microsoft Azure, [create an account](https://azure.microsoft.com/free/) to evaluate our offerings. 
 2. Register your subscription for Azure Database Migration Service (DMS). If you have already done it, you can skip this step. Go to Azure portal homepage and navigate to your subscription as shown below.
 
-  :::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-dms.png" alt-text="CLI DMS" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-dms.png":::
+  :::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-dms.png" alt-text="Screenshot of C L I DMS" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-dms.png":::
 
 3. In your subscription, navigate to **Resource Providers** from the left navigation menu. Search for "**Microsoft.DataMigration**"; as shown below and click on **Register**.
 
-  :::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-dms-register.png" alt-text="CLI DMS Register" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-dms-register.png":::
+  :::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-dms-register.png" alt-text="Screenshot of C L I DMS register" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-dms-register.png":::
 
 ## Pre-requisites
 
@@ -35,9 +35,9 @@ This quick start article shows you how to use Single to Flexible Server migratio
 2. In case Azure CLI is already installed, check the version by issuing **az version** command. The version should be **2.28.0 or above** to use the migration CLI commands. If not, update your Azure CLI using this [link](/cli/azure/update-azure-cli.md).
 3. Once you have the right Azure CLI version, run the **az login** command. A browser page is opened with Azure sign-in page to authenticate. Provide your Azure credentials to do a successful authentication. For other ways to sign with Azure CLI, visit this [link](/cli/azure/authenticate-azure-cli.md).
 
-```bash
-az login
-```
+  ```bash
+  az login
+  ```
 1. Take care of the pre-requisites listed in this [**document**](./concepts-single-to-flexible.md#pre-requisites) which are necessary to get started with the Single to Flexible migration feature.
 
 ## Migration CLI commands
@@ -50,7 +50,7 @@ az postgres flexible-server migration --help
 
   gives you the following output.
 
-  :::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-help.png" alt-text="CLI help" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-help.png":::
+  :::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-help.png" alt-text="Screenshot of C L I help" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-help.png":::
 
 It lists the set of migration commands that are supported along with their actions. Let us look into these commands in detail.
 
@@ -64,7 +64,7 @@ az postgres flexible-server migration create -- help
 
 gives the following result
 
-:::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-create.png" alt-text="CLI create" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-create.png":::
+:::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-create.png" alt-text="Screenshot of C L I create" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-create.png":::
 
 It calls out the expected arguments and has an example syntax that needs to be used to create a successful migration from the source to target server. The CLI command to create a migration is given below
 
@@ -148,7 +148,7 @@ Create migration parameters:
 | **SourceDBServerResourceId** | Required |  Resource ID of the single server and is mandatory. |
 | **SourceDBServerFullyQualifiedDomainName** | optional |  Used when a custom DNS server is used for name resolution for a virtual network. The FQDN of the single server as per the custom DNS server should be provided for this property. |
 | **TargetDBServerFullyQualifiedDomainName** | optional |  Used when a custom DNS server is used for name resolution inside a virtual network. The FQDN of the flexible server as per the custom DNS server should be provided for this property. <br> **_SourceDBServerFullyQualifiedDomainName_**, **_TargetDBServerFullyQualifiedDomainName_** should be included as a part of the JSON only in the rare scenario of a custom DNS server being used for name resolution instead of Azure provided DNS. Otherwise, these parameters should not be included as a part of the JSON file. |
-| **SecretParameters** | Required | Passwords for admin user for both single server and flexible server along with the AAD app credentials. They help to authenticate against the source and target servers and help in checking proper authorization access to the resources.
+| **SecretParameters** | Required | Passwords for admin user for both single server and flexible server along with the Azure AD app credentials. They help to authenticate against the source and target servers and help in checking proper authorization access to the resources.
 | **MigrationResourceGroup** | optional | This section consists of two properties. <br> **ResourceID (optional)** : The migration infrastructure and other network infrastructure components are created to migrate data and schema from the source to target. By default, all the components created by this feature are provisioned under the resource group of the target server. If you wish to deploy them under a different resource group, then you can assign the resource ID of that resource group to this property. <br> **SubnetResourceID (optional)** : In case if your source has public access turned OFF or if your target server is deployed inside a VNet, then specify a subnet under which migration infrastructure needs to be created so that it can connect to both source and target servers. |
 | **DBsToMigrate** | Required | Specify the list of databases you want to migrate to the flexible server. You can include a maximum of 8 database names at a time. |
 | **SetupLogicalReplicationOnSourceDBIfNeeded** | Optional | Logical replication can be enabled on the source server automatically by setting this property to **true**. This change in the server settings requires a server restart with a downtime of few minutes (~ 2-3 mins). |
@@ -195,7 +195,7 @@ az postgres flexible-server migration list [--subscription]
 
 The **migration_name** is the name assigned to the migration during the **create migration** command. Here is a snapshot of the sample response from the **Show Details** CLI command.
 
-:::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-migration-name.png" alt-text="CLI migration name" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-migration-name.png":::
+:::image type="content" source="./media/concepts-single-to-flex/single-to-flex-cli-migration-name.png" alt-text="Screenshot of C L I migration name" lightbox="./media/concepts-single-to-flex/single-to-flex-cli-migration-name.png":::
 
 Some important points to note on the command response:
 
@@ -336,3 +336,7 @@ Navigate to your Virtual network where you deployed your source or the target se
 ## Post Migration Steps
 
 Make sure the post migration steps listed [here](./concepts-single-to-flexible.md) are followed for a successful end to end migration.
+
+## Next steps
+
+- [Single Server to Flexible migration concepts](./concepts-single-to-flexible.md)