Merge pull request #230606 from hariramt/s2f-updates-1.1

Extensions message update

Author: prmerger-automator[bot]

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

@@ -196,9 +196,9 @@ Search for the **azure.extensions** parameter on the Server Parameters blade on
 :::image type="content" source="./media/concepts-single-to-flexible/allowlist-extensions.png" alt-text="Diagram that shows allow listing of extensions on Flexible Server." lightbox="./media/concepts-single-to-flexible/allowlist-extensions.png":::
 
 >[!NOTE]
-> If TIMESCALEDB, PG_PARTMAN or POSTGIS_TIGER_DECODER extensions are used in your single server database, please raise a support request since the Single to Flex migration tool will not handle these extensions.  
+> If TIMESCALEDB, PG_PARTMAN, POSTGRES_FDW or POSTGIS_TIGER_DECODER extensions are used in your single server database, please raise a support request since the Single to Flex migration tool will not handle these extensions.
 
-Check if the list contains any of the following extensions: 
+Check if the list contains any of the following extensions:
 * PG_CRON
 * PG_HINT_PLAN
 * PG_PARTMAN_BGW

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

@@ -37,6 +37,9 @@ To complete this tutorial, you need to:
 * Use an existing instance of Azure Database for PostgreSQL – Single Server (the source server)
 * All extensions used on the Single Server (source) must be [allow-listed on the Flexible Server (target)](./concepts-single-to-flexible.md#allow-list-required-extensions)
 
+>[!NOTE]
+> If TIMESCALEDB, PG_PARTMAN, POSTGRES_FDW or POSTGIS_TIGER_DECODER extensions are used in your single server database, please raise a support request since the Single to Flex migration tool will not handle these extensions.
+
 > [!IMPORTANT]
 > To provide the best migration experience, performing migration using a burstable instance of Flexible server is not supported. Please use a general purpose or a memory optimized instance (4 VCore or higher) as your Target Flexible server to perform the migration. Once the migration is complete, you can downscale back to a burstable instance if necessary.
 

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

@@ -80,6 +80,9 @@ After deploying the Flexible Server, follow the steps 3 to 5 under [Configure th
 
 The first tab is **Setup**. Just in case you missed it, allowlist all required extensions as shown in [Migrate from Azure Database for PostgreSQL Single Server to Flexible Server](./concepts-single-to-flexible.md#allow-list-required-extensions). It is important to allowlist the extensions before you initiate a migration using this tool.
 
+>[!NOTE]
+> If TIMESCALEDB, PG_PARTMAN, POSTGRES_FDW or POSTGIS_TIGER_DECODER extensions are used in your single server database, please raise a support request since the Single to Flex migration tool will not handle these extensions.
+
 :::image type="content" source="./media/concepts-single-to-flexible/single-to-flex-setup.png" alt-text="Screenshot of the details belonging to Set up 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 doesn't 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.