Merge pull request #153078 from Clare-Zheng82/0402updateUI_SSIS_IR

Update Screenshots and Text in "Provision the Azure-SSIS integration runtime" doc

Author: v-ccolin

articles/data-factory/media/tutorial-create-azure-ssis-runtime-portal/configure-ssis-integration-runtime-tile.png

@@ -4,7 +4,7 @@ description: Learn how to provision the Azure-SSIS integration runtime in Azure
 ms.service: data-factory
 ms.topic: tutorial
 ms.custom: seo-lt-2019
-ms.date: 02/22/2021
+ms.date: 04/02/2021
 author: swinarko
 ms.author: sawinark
 ---
@@ -65,23 +65,23 @@ After your data factory is created, open its overview page in the Azure portal.
 
 ### From the Data Factory overview
 
-1. On the **Let's get started** page, select the **Configure SSIS Integration Runtime** tile. 
+1. On the **Let's get started** page, select the **Configure SSIS Integration** tile. 
 
    !["Configure SSIS Integration Runtime" tile](./media/tutorial-create-azure-ssis-runtime-portal/configure-ssis-integration-runtime-tile.png)
 
 1. For the remaining steps to set up an Azure-SSIS IR, see the [Provision an Azure-SSIS integration runtime](#provision-an-azure-ssis-integration-runtime) section. 
 
 ### From the authoring UI
 
-1. In the Azure Data Factory UI, switch to the **Edit** tab and select **Connections**. Then switch to the **Integration Runtimes** tab to view existing integration runtimes in your data factory. 
+1. In the Azure Data Factory UI, switch to the **Manage** tab, and then switch to the **Integration runtimes** tab to view existing integration runtimes in your data factory. 
 
    ![Selections for viewing existing IRs](./media/tutorial-create-azure-ssis-runtime-portal/view-azure-ssis-integration-runtimes.png)
 
 1. Select **New** to create an Azure-SSIS IR and open the **Integration runtime setup** pane. 
 
    ![Integration runtime via menu](./media/tutorial-create-azure-ssis-runtime-portal/edit-connections-new-integration-runtime-button.png)
 
-1. In the **Integration runtime setup** pane, select the **Lift-and-shift existing SSIS packages to execute in Azure** tile, and then select **Next**.
+1. In the **Integration runtime setup** pane, select the **Lift-and-shift existing SSIS packages to execute in Azure** tile, and then select **Continue**.
 
    ![Specify the type of integration runtime](./media/tutorial-create-azure-ssis-runtime-portal/integration-runtime-setup-options.png)
 
@@ -111,7 +111,7 @@ On the **General settings** page of **Integration runtime setup** pane, complete
 
    1. For **Save Money**, select the Azure Hybrid Benefit option for your integration runtime: **Yes** or **No**. Select **Yes** if you want to bring your own SQL Server license with Software Assurance to benefit from cost savings with hybrid use. 
 
-   1. Select **Next**. 
+   1. Select **Continue**. 
 
 ### Deployment settings page
 
@@ -153,7 +153,7 @@ If you select the check box, complete the following steps to bring your own data
 
    1. For **Catalog Database Service Tier**, select the service tier for your database server to host SSISDB. Select the Basic, Standard, or Premium tier, or select an elastic pool name.
 
-Select **Test connection** when applicable and if it's successful, select **Next**.
+Select **Test connection** when applicable and if it's successful, select **Continue**.
 
 #### Creating Azure-SSIS IR package stores
 
@@ -172,7 +172,7 @@ On the **Add package store** pane, complete the following steps.
    1. For **Package store linked service**, select your existing linked service that stores the access information for file system/Azure Files/Azure SQL Managed Instance where your packages are deployed or create a new one by selecting **New**. On the **New linked service** pane, complete the following steps. 
 
       > [!NOTE]
-      > You can use either **Azure File Storage** or **File System** linked services to access Azure Files. If you use **Azure File Storage** linked service, Azure-SSIS IR package store supports only **Basic** (not **Account key** nor **SAS URI**) authentication method for now. To use **Basic** authentication on **Azure File Storage** linked service, you can append `?feature.upgradeAzureFileStorage=false` to the ADF portal URL in your browser. Alternatively, you can use **File System** linked service to access Azure Files instead. 
+      > You can use either **Azure File Storage** or **File System** linked services to access Azure Files. If you use **Azure File Storage** linked service, Azure-SSIS IR package store supports only **Basic** (not **Account key** nor **SAS URI**) authentication method for now. 
 
       ![Deployment settings for linked services](./media/tutorial-create-azure-ssis-runtime-portal/deployment-settings-linked-service.png)
 
@@ -183,8 +183,8 @@ On the **Add package store** pane, complete the following steps.
       1. For **Type**, select **Azure File Storage**, **Azure SQL Managed Instance**, or **File System**.
 
       1. You can ignore **Connect via integration runtime**, since we always use your Azure-SSIS IR to fetch the access information for package stores.
-
-      1. If you select **Azure File Storage**, complete the following steps. 
+      
+      1. If you select **Azure File Storage**,  for **Authentication method**, select **Basic**, and then complete the following steps. 
 
          1. For **Account selection method**, select **From Azure subscription** or **Enter manually**.
 
@@ -194,29 +194,29 @@ On the **Add package store** pane, complete the following steps.
 
       1. If you select **Azure SQL Managed Instance**, complete the following steps. 
 
-         1. Select **Connection string** to enter it manually or your **Azure Key Vault** where it's stored as a secret.
+         1. Select **Connection string** or your **Azure Key Vault** where it's stored as a secret.
 
          1. If you select **Connection string**, complete the following steps. 
+             1. For **Account selection method**, if you choose **From Azure subscription**, select the relevant **Azure subscription**, **Server name**, **Endpoint type** and **Database name**. If you choose **Enter manually**, complete the following steps. 
+                1.  For **Fully qualified domain name**, enter `<server name>.<dns prefix>.database.windows.net` or `<server name>.public.<dns prefix>.database.windows.net,3342` as the private or public endpoint of your Azure SQL Managed Instance, respectively. If you enter the private endpoint, **Test connection** isn't applicable, since ADF UI can't reach it.
 
-            1. For **Fully qualified domain name**, enter `<server name>.<dns prefix>.database.windows.net` or `<server name>.public.<dns prefix>.database.windows.net,3342` as the private or public endpoint of your Azure SQL Managed Instance, respectively. If you enter the private endpoint, **Test connection** isn't applicable, since ADF UI can't reach it.
-
-            1. For **Database name**, enter `msdb`.
+                1. For **Database name**, enter `msdb`.
 
             1. For **Authentication type**, select **SQL Authentication**, **Managed Identity**, or **Service Principal**.
 
-            1. If you select **SQL Authentication**, enter the relevant **Username** and **Password** or select your **Azure Key Vault** where it's stored as a secret.
+                - If you select **SQL Authentication**, enter the relevant **Username** and **Password** or select your **Azure Key Vault** where it's stored as a secret.
 
-            1. If you select **Managed Identity**, grant your ADF managed identity access to your Azure SQL Managed Instance.
+                -  If you select **Managed Identity**, grant your ADF managed identity access to your Azure SQL Managed Instance.
 
-            1. If you select **Service Principal**, enter the relevant **Service principal ID** and **Service principal key** or select your **Azure Key Vault** where it's stored as a secret.
+                - If you select **Service Principal**, enter the relevant **Service principal ID** and **Service principal key** or select your **Azure Key Vault** where it's stored as a secret.
 
       1. If you select **File system**, enter the UNC path of folder where your packages are deployed for **Host**, as well as the relevant **Username** and **Password** or select your **Azure Key Vault** where it's stored as a secret.
 
       1. Select **Test connection** when applicable and if it's successful, select **Create**.
 
    1. Your added package stores will appear on the **Deployment settings** page. To remove them, select their check boxes, and then select **Delete**.
 
-Select **Test connection** when applicable and if it's successful, select **Next**.
+Select **Test connection** when applicable and if it's successful, select **Continue**.
 
 ### Advanced settings page
 
@@ -236,7 +236,7 @@ On the **Advanced settings** page of **Integration runtime setup** pane, complet
 
    1. Select **Continue**. 
 
-On the **Summary** page of **Integration runtime setup** pane, review all provisioning settings, bookmark the recommended documentation links, and select **Finish** to start the creation of your integration runtime. 
+On the **Summary** page of **Integration runtime setup** pane, review all provisioning settings, bookmark the recommended documentation links, and select **Create** to start the creation of your integration runtime. 
 
    > [!NOTE]
    > Excluding any custom setup time, this process should finish within 5 minutes.