Merge pull request #253579 from shriram-muthukrishnan/updateregions

prmerger-automator[bot] · web-flow · commit 2ff856e0663b · 2023-10-03T12:38:43.000Z
Adding support for all regions
diff --git a/articles/postgresql/migrate/concepts-single-to-flexible.md b/articles/postgresql/migrate/concepts-single-to-flexible.md
@@ -75,7 +75,7 @@ The following table lists the different tools available for performing the migra
 The next section of the document gives an overview of the Single to Flex Migration tool, its implementation, limitations, and the experience that makes it the recommended tool to perform migrations from single to flexible server.
 
 > [!NOTE]  
-> The Single to Flex Migration tool currently supports only **Offline** migrations. Support for online migrations will be introduced later in the tool.
+> The Single to Flex Migration tool is available in all Azure regions and currently supports only **Offline** migrations. Support for online migrations will be introduced later in the tool.
 
 ## Single to Flexible Migration tool - Overview
 
@@ -113,10 +113,9 @@ Along with data migration, the tool automatically provides the following built-i
 ## Limitations
 
 - You can have only one active migration to your flexible server.
-- You can select a max of eight databases in one migration attempt. If you've more than eight databases, you must wait for the first migration to be complete before initiating another migration for the rest of the databases. Support for migration of more than eight databases in a single migration will be introduced later.
-- The source and target server must be in the same Azure region. Cross region migrations are not supported.
+- The source and target server must be in the same Azure region. Cross region migrations is enabled only for servers in China regions.
 - The tool takes care of the migration of data and schema. It doesn't migrate managed service features such as server parameters, connection security details and firewall rules.
-- The migration tool shows the number of tables copied from source to target server. You need to validate the data in target server post migration.
+- The migration tool shows the number of tables copied from source to target server. You need to manually validate the data in target server post migration.
 - The tool only migrates user databases and not system databases like template_0, template_1, azure_sys and azure_maintenance.
 
 > [!NOTE]  
diff --git a/articles/postgresql/migrate/how-to-migrate-single-to-flexible-cli.md b/articles/postgresql/migrate/how-to-migrate-single-to-flexible-cli.md
@@ -155,7 +155,7 @@ The `create` parameters that go into the json file format are as shown below:
 | `adminCredentials` | Required | This parameter lists passwords for admin users for both the Single Server source and the Flexible Server target. These passwords help to authenticate against the source and target servers.
 | `sourceServerUserName` | Required | The default value is the admin user created during the creation of single server and the password provided will be used for authentication against this user. In case you are not using the default user, this parameter is the user or role on the source server used for performing the migration. This user should have necessary privileges and ownership on the database objects involved in the migration and should be a member of **azure_pg_admin** role. |
 | `targetServerUserName` | Required | The default value is the admin user created during the creation of flexible server and the password provided will be used for authentication against this user. In case you are not using the default user, this parameter is the user or role on the target server used for performing the migration. This user should be a member of **azure_pg_admin**, **pg_read_all_settings**, **pg_read_all_stats**,**pg_stat_scan_tables** roles and should have the **Create role, Create DB** attributes. |
-| `dbsToMigrate` | Required | Specify the list of databases that you want to migrate to Flexible Server. You can include a maximum of eight database names at a time. |
+| `dbsToMigrate` | Required | Specify the list of databases that you want to migrate to Flexible Server. |
 | `overwriteDbsInTarget` | Required | When set to true, if the target server happens to have an existing database with the same name as the one you're trying to migrate, migration tool automatically overwrites the database. |
 | `SetupLogicalReplicationOnSourceDBIfNeeded` | Optional | You can enable logical replication 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 two to three minutes. |
 | `SourceDBServerFullyQualifiedDomainName` | Optional |  Use it when a custom DNS server is used for name resolution for a virtual network. Provide the FQDN of the Single Server source according to the custom DNS server for this property. |
diff --git a/articles/postgresql/migrate/how-to-migrate-single-to-flexible-portal.md b/articles/postgresql/migrate/how-to-migrate-single-to-flexible-portal.md
@@ -94,7 +94,7 @@ The **Source** tab prompts you to give details related to the Single Server that
 
 :::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-migration-source.png" alt-text="Screenshot of source database server details." lightbox="./media/concepts-single-to-flexible/single-to-flex-migration-source.png":::
 
-After you make the **Subscription** and  **Resource Group** selections, the dropdown list for server names shows Single Servers under that resource group across regions. Select the source that you want to migrate databases from. Note that you can migrate databases from a Single Server to a target Flexible Server in the same region - cross region migrations aren't supported.
+After you make the **Subscription** and  **Resource Group** selections, the dropdown list for server names shows Single Servers under that resource group across regions. Select the source that you want to migrate databases from. Note that you can migrate databases from a Single Server to a target Flexible Server in the same region - cross region migrations are supported only in China regions.
 
 After you choose the Single Server source, the **Location**, **PostgreSQL version**, and **Server admin login name** boxes are populated automatically. The server admin login name is the admin username used to create the Single Server. In the **Password** box, enter the password for that admin user. The migration tool performs the migration of single server databases as the admin user.
 
