Merge branch 'three-data-factory-articles' of https://github.com/itechedit/azure-docs-pr into three-data-factory-articles

itechedit · itechedit · commit 47ee7e956dcd · 2020-02-12T11:24:32.000-08:00
diff --git a/articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md b/articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md
@@ -1,5 +1,5 @@
 ---
-title: Customize setup for an Azure-SSIS Integration Runtime
+title: Customize the setup for an Azure-SSIS Integration Runtime
 description: This article describes how to use the custom setup interface for an Azure-SSIS Integration Runtime to install additional components or change settings
 services: data-factory
 documentationcenter: ""
@@ -14,11 +14,11 @@ ms.custom: seo-lt-2019
 ms.date: 02/01/2020
 ---
 
-# Customize setup for an Azure-SSIS Integration Runtime
+# Customize the setup for an Azure-SSIS Integration Runtime
 
-The custom setup interface for an Azure-SQL Server Integration Services Integration Runtime (Azure-SSIS IR) provides an interface for adding your own steps during the setup or reconfiguration of your Azure-SSIS IR. 
+The custom setup for an Azure-SQL Server Integration Services Integration Runtime (Azure-SSIS IR) provides an interface for adding your own steps during the setup or reconfiguration of your Azure-SSIS IR. 
 
-By using custom setup, you can alter the default operating configuration or environment to, for example, start additional Windows services or persist access credentials for file shares. Or you can install additional components, such as assemblies, drivers, or extensions, on each node of your Azure-SSIS IR.
+By using the custom setup, you can alter the default operating configuration or environment to, for example, start additional Windows services or persist access credentials for file shares. Or you can install additional components, such as assemblies, drivers, or extensions, on each node of your Azure-SSIS IR.
 
 You can do custom setups on your Azure-SSIS IR in either of two ways: 
 * **Express custom setup without a script**: Run some common system configurations and Windows commands or install some popular or recommended additional components without using any scripts.
@@ -33,7 +33,7 @@ You can install both free, unlicensed components and paid, licensed components w
 
 The following limitations apply only to standard custom setups:
 
-- If you want to use *gacutil.exe* in your script to install assemblies in the global assembly cache (GAC), you need to provide *gacutil.exe* as part of your custom setup. Or you can use the copy that's provided in our Public Preview container, discussed later in the "Instructions" section.
+- If you want to use *gacutil.exe* in your script to install assemblies in the global assembly cache (GAC), you need to provide *gacutil.exe* as part of your custom setup. Or you can use the copy that's provided in our *Public Preview* container, discussed later in the "Instructions" section.
 
 - If you want to reference a subfolder in your script, *msiexec.exe* doesn't support the `.\` notation to reference the root folder. Use a command such as `msiexec /i "MySubfolder\MyInstallerx64.msi" ...` instead of `msiexec /i ".\MySubfolder\MyInstallerx64.msi" ...`.
 
@@ -45,7 +45,7 @@ The following limitations apply only to standard custom setups:
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 
-To customize your Azure-SSIS IR, you need the following things:
+To customize your Azure-SSIS IR, you need the following items:
 
 - [An Azure subscription](https://azure.microsoft.com/)
 
@@ -60,7 +60,7 @@ To customize your Azure-SSIS IR, you need the following things:
 1. Prepare your custom setup script and its associated files (for example, .bat, .cmd, .exe, .dll, .msi, or .ps1 files).
 
    * You must have a script file named *main.cmd*, which is the entry point of your custom setup.  
-   * To ensure that the script can be executed silently, we recommend that you test the script on your local machine first.  
+   * To ensure that the script can be executed silently, we recommend that you test it on your local machine first.  
    * If you want additional logs generated by other tools (for example, *msiexec.exe*) to be uploaded to your container, specify the predefined environment variable, `CUSTOM_SETUP_SCRIPT_LOG_DIR`, as the log folder in your scripts (for example, *msiexec /i xxx.msi /quiet /lv %CUSTOM_SETUP_SCRIPT_LOG_DIR%\install.log*).
 
 1. Download, install, and open [Azure Storage Explorer](https://storageexplorer.com/). To do so:
@@ -106,7 +106,7 @@ To customize your Azure-SSIS IR, you need the following things:
    
    If you want to add express custom setups, select **New** to open the **Add express custom setup** pane, and then select a type in the **Express custom setup type** drop-down list:
 
-   * If you select the **Run cmdkey command** type, you can persist access credentials for your file shares/Azure Files on Azure-SSIS IR by entering your targeted computer/domain name, account name/username, and account key/password in the **/Add**, **/User**, and **/Pass** boxes. This is similar to running the Windows [cmdkey](https://docs.microsoft.com/windows-server/administration/windows-commands/cmdkey) command on your local machine.
+   * If you select the **Run cmdkey command** type, you can persist access credentials for your file shares or Azure Files shares on Azure-SSIS IR by entering your targeted computer name or domain name, account name or username, and account key or password in the **/Add**, **/User**, and **/Pass** boxes. This is similar to running the Windows [cmdkey](https://docs.microsoft.com/windows-server/administration/windows-commands/cmdkey) command on your local machine.
    
    * If you select the **Add environment variable** type, you can add Windows environment variables to use in your packages that run on the Azure-SSIS IR by entering your environment variable name and value in the **Variable name** and **Variable value** boxes. This is similar to running the Windows [set](https://docs.microsoft.com/windows-server/administration/windows-commands/set_1) command on your local machine.
 
@@ -216,11 +216,11 @@ To customize your Azure-SSIS IR, you need the following things:
 
       * An *EXCEL* folder, which contains a custom setup script (*main.cmd*) to install C# assemblies and libraries that you can use in script tasks to dynamically read and write Excel files on each node of your Azure-SSIS IR. 
       
-        First, download [*ExcelDataReader.dll*](https://www.nuget.org/packages/ExcelDataReader/) and download [*DocumentFormat.OpenXml.dll*](https://www.nuget.org/packages/DocumentFormat.OpenXml/), and then upload them all together with *main.cmd* to your container. Alternatively, if you want to use only the standard Excel Connection Manager, Excel source, and Excel destination, the required access redistributable is already preinstalled on your Azure-SSIS IR, so you don't need any custom setup.
+        First, download [*ExcelDataReader.dll*](https://www.nuget.org/packages/ExcelDataReader/) and [*DocumentFormat.OpenXml.dll*](https://www.nuget.org/packages/DocumentFormat.OpenXml/), and then upload them all together with *main.cmd* to your container. Alternatively, if you want to use only the standard Excel Connection Manager, Excel source, and Excel destination, the required access redistributable is already preinstalled on your Azure-SSIS IR, so you don't need any custom setup.
 	  
 	  * A *MYSQL ODBC* folder, which contains a custom setup script (*main.cmd*) to install the MySQL ODBC drivers on each node of your Azure-SSIS IR. This setup lets you use the ODBC Connection Manager, source, and destination to connect to the MySQL server. 
      
-        First, download the latest 64-bit and 32-bit versions of the MySQL ODBC driver installers (for example, *mysql-connector-odbc-8.0.13-winx64.msi* and *mysql-connector-odbc-8.0.13-win32.msi*) from [MySQL](https://dev.mysql.com/downloads/connector/odbc/), and then upload them all together with *main.cmd* to your container.
+        First, [download the latest 64-bit and 32-bit versions of the MySQL ODBC driver installers](https://dev.mysql.com/downloads/connector/odbc/) (for example, *mysql-connector-odbc-8.0.13-winx64.msi* and *mysql-connector-odbc-8.0.13-win32.msi*), and then upload them all together with *main.cmd* to your container.
 
       * An *ORACLE ENTERPRISE* folder, which contains a custom setup script (*main.cmd*) and silent installation config file (*client.rsp*) to install the Oracle connectors and OCI driver on each node of your Azure-SSIS IR Enterprise Edition. This setup lets you use the Oracle Connection Manager, source, and destination to connect to the Oracle server. 
       
diff --git a/articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md b/articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md
@@ -16,9 +16,9 @@ ms.date: 02/06/2020
 
 # Configure a self-hosted IR as a proxy for an Azure-SSIS IR in Azure Data Factory
 
-This article describes how to run SQL Server Integration Services (SSIS) packages on an Azure-SSIS Integration Runtime (Azure-SSIS IR) in Azure Data Factory with a self-hosted integration runtime (self-hosted IR)configured as a proxy. 
+This article describes how to run SQL Server Integration Services (SSIS) packages on an Azure-SSIS Integration Runtime (Azure-SSIS IR) in Azure Data Factory with a self-hosted integration runtime (self-hosted IR) configured as a proxy. 
 
-With this feature, you can access data on-premises without having to [join your Azure-SSIS IR to a virtual network](https://docs.microsoft.com/azure/data-factory/join-azure-ssis-integration-runtime-virtual-network).  The feature is useful when your corporate network has a configuration too complex or a policy too restrictive for you to inject your Azure-SSIS IR into it.
+With this feature, you can access data on-premises without having to [join your Azure-SSIS IR to a virtual network](https://docs.microsoft.com/azure/data-factory/join-azure-ssis-integration-runtime-virtual-network). The feature is useful when your corporate network has a configuration too complex or a policy too restrictive for you to inject your Azure-SSIS IR into it.
 
 This feature splits packages that contain a data flow task with an on-premises data source into two staging tasks: 
 * The first task, which runs on your self-hosted IR, first moves data from the on-premises data source into a staging area in your Azure Blob storage.
@@ -28,7 +28,7 @@ Other benefits and capabilities of this feature allow you to, for example, set u
 
 ## Prepare the self-hosted IR
 
-To use this feature, you first create a data factory and set up your an Azure-SSIS IR in it. If you have not already done so, follow the instructions in [Set up an Azure-SSIS IR](https://docs.microsoft.com/azure/data-factory/tutorial-deploy-ssis-packages-azure).
+To use this feature, you first create a data factory and set up an Azure-SSIS IR in it. If you have not already done so, follow the instructions in [Set up an Azure-SSIS IR](https://docs.microsoft.com/azure/data-factory/tutorial-deploy-ssis-packages-azure).
 
 You then set up your self-hosted IR in the same data factory where your Azure-SSIS IR is set up. To do so, see [Create a self-hosted IR](https://docs.microsoft.com/azure/data-factory/create-self-hosted-integration-runtime).
 
@@ -40,28 +40,28 @@ Finally, you download and install the latest version of the self-hosted IR, as w
 
   If you use the latest version of OLEDB driver for SQL Server (MSOLEDBSQL), [download the 64-bit version](https://www.microsoft.com/download/details.aspx?id=56730).  
   
-  If you use OLEDB drivers for other database systems, such as PostgreSQL, MySQL, Oracle, and so on, you can download the 64-bit version from their respective websites.
+  If you use OLEDB drivers for other database systems, such as PostgreSQL, MySQL, Oracle, and so on, you can download the 64-bit versions from their websites.
 - If you haven't already done so, [download and install the 64-bit version of Visual C++ (VC) runtime](https://www.microsoft.com/download/details.aspx?id=40784) on the same machine where your self-hosted IR is installed.
 
 ## Prepare the Azure Blob storage-linked service for staging
 
 If you haven't already done so, create an Azure Blob storage-linked service in the same data factory where your Azure-SSIS IR is set up. To do so, see [Create an Azure data factory-linked service](https://docs.microsoft.com/azure/data-factory/quickstart-create-data-factory-portal#create-a-linked-service). Be sure to do the following:
-- For **Data Store**, select **Azure Blob Storage**.
-- For **Connect via integration runtime**, select **AutoResolveIntegrationRuntime**. 
-- For **Authentication method**, select **Account key**, **SAS URI**, or **Service Principal**. 
+- For **Data Store**, select **Azure Blob Storage**.  
+- For **Connect via integration runtime**, select **AutoResolveIntegrationRuntime**.  
+- For **Authentication method**, select **Account key**, **SAS URI**, or **Service Principal**.  
 
     >[!TIP]
-    >When **Service Principal** is selected, grant at least the *Storage Blob Data Contributor* role. For more information, refer to [Azure Blob storage connector](connector-azure-blob-storage.md#linked-service-properties).
+    >If you select **Service Principal**, grant at least the *Storage Blob Data Contributor* role. For more information, refer to [Azure Blob storage connector](connector-azure-blob-storage.md#linked-service-properties).
 
 ![Prepare the Azure Blob storage-linked service for staging](media/self-hosted-integration-runtime-proxy-ssis/shir-azure-blob-storage-linked-service.png)
 
 ## Configure an Azure-SSIS IR with your self-hosted IR as a proxy
 
-Having prepared your self-hosted IR and Azure Blob storage-linked service for staging, you can now configure your new or existing Azure-SSIS IR with the self-hosted IR as a proxy in your data factory portal or app. Before you do so, however, if your existing Azure-SSIS IR is already running, stop it and then restart it.
+Having prepared your self-hosted IR and Azure Blob storage-linked service for staging, you can now configure your new or existing Azure-SSIS IR with the self-hosted IR as a proxy in your data factory portal or app. Before you do so, though, if your existing Azure-SSIS IR is already running, stop it and then restart it.
 
-1. In the **Integration runtime setup** pane, advance past the **General Settings** and **SQL Settings** sections by selecting **Next**. 
+1. In the **Integration runtime setup** pane, skip past the **General Settings** and **SQL Settings** sections by selecting **Next**. 
 
-1. In the **Advanced settings** section:
+1. In the **Advanced settings** section, do the following:
 
    1. Select the **Set up Self-Hosted Integration Runtime as a proxy for your Azure-SSIS Integration Runtime** check box. 
 
@@ -146,7 +146,7 @@ On your self-hosted IR, you can find the runtime logs in the *C:\ProgramData\SSI
 
 If the staging tasks on your self-hosted IR require Windows authentication, [configure your SSIS packages to use the same Windows authentication](https://docs.microsoft.com/sql/integration-services/lift-shift/ssis-azure-connect-with-windows-auth?view=sql-server-ver15). 
 
-Your staging tasks will be invoked with the self-hosted IR service account (*NT SERVICE\DIAHostService*, by default), and your data stores will be accessed with the Windows authentication account. Both accounts require certain security policies to be assigned to them. Consequently, on the self-hosted IR machine, go to **Local Security Policy** > **Local Policies** > **User Rights Assignment** and do the following:
+Your staging tasks will be invoked with the self-hosted IR service account (*NT SERVICE\DIAHostService*, by default), and your data stores will be accessed with the Windows authentication account. Both accounts require certain security policies to be assigned to them. On the self-hosted IR machine, go to **Local Security Policy** > **Local Policies** > **User Rights Assignment**, and then do the following:
 
 1. Assign the *Adjust memory quotas for a process* and *Replace a process level token* policies to the self-hosted IR service account. This should occur  automatically when you install your self-hosted IR with the default service account. If you use a different service account, assign the same policies to it.
 
@@ -160,7 +160,7 @@ The second staging tasks that run on your Azure-SSIS IR are not be billed separa
 
 ## Current limitations
 
-- Only data flow tasks with Open Database Connectivity (ODBC), OLEDB, or Flat File connection managers and ODBC, OLEDB, and Flat File Sources or OLEDB Destination are currently supported. 
+- Only data flow tasks with Open Database Connectivity (ODBC), OLEDB, or Flat File connection managers and ODBC, OLEDB, and Flat File sources or OLEDB destination are currently supported. 
 - Only Azure Blob storage-linked services that are configured with *Account key*, *Shared Access Signature (SAS) URI*, or *Service Principal* authentication are currently supported.
 
 ## Next steps
diff --git a/articles/data-factory/tutorial-deploy-ssis-packages-azure-powershell.md b/articles/data-factory/tutorial-deploy-ssis-packages-azure-powershell.md
