Merge pull request #114413 from julieMSFT/20200507_adls_update

denrea · web-flow · commit eab4020bef1d · 2020-05-07T16:30:49.000-07:00
updates to naming of ADLS Gen2
diff --git a/articles/synapse-analytics/data-integration/data-integration-data-lake.md b/articles/synapse-analytics/data-integration/data-integration-data-lake.md
@@ -1,5 +1,5 @@
 ---
-title: Ingest into Azure Data Lake Storage Gen2 in Azure Synapse Analytics 
+title: Ingest into Azure Data Lake Storage Gen2
 description: Learn how to ingest data into Azure Data Lake Storage Gen2 in Azure Synapse Analytics
 services: synapse-analytics 
 author: djpmsft
diff --git a/articles/synapse-analytics/data-integration/data-integration-sql-pool.md b/articles/synapse-analytics/data-integration/data-integration-sql-pool.md
@@ -34,7 +34,7 @@ In Azure Synapse Analytics, a linked service is where you define your connection
 
 ## Create pipeline
 
-A pipeline contains the logical flow for an execution of a set of activities. In this section, you'll create a pipeline containing a copy activity that ingests data from ADLS gen 2 into a SQL pool.
+A pipeline contains the logical flow for an execution of a set of activities. In this section, you'll create a pipeline containing a copy activity that ingests data from ADLS Gen2 into a SQL pool.
 
 1. Go to the **Orchestrate** tab. Click on the plus icon 
 next to the pipelines header and select **Pipeline**.
diff --git a/articles/synapse-analytics/overview-cheat-sheet.md b/articles/synapse-analytics/overview-cheat-sheet.md
@@ -25,7 +25,7 @@ The Azure Synapse Analytics cheat sheet will guide you through the basic concept
 ## Concepts
 | Nouns and verbs                         | What it does       |
 |:---                                 |:---                 |
-| **Synapse Workspace (preview)** | A securable collaboration boundary for doing cloud-based enterprise analytics in Azure. A workspace is deployed in a specific region and has an associated ADLSg2 account and file system (for storing temporary data). A workspace is under a resource group. |
+| **Synapse Workspace (preview)** | A securable collaboration boundary for doing cloud-based enterprise analytics in Azure. A workspace is deployed in a specific region and has an associated ADLS Gen2 account and file system (for storing temporary data). A workspace is under a resource group. |
 | **SQL Analytics**   | Run analytics with pools or with on-demand capabilities.  |
 | **SQL pool**   | 0-to-N SQL provisioned resources with their corresponding databases can be deployed in a workspace. Each SQL pool has an associated database. A SQL pool can be scaled, paused and resumed manually or automatically. A SQL pool can scale from 100 DWU up to 30,000 DWU.       |
 | **SQL on-demand (preview)**   | Distributed data processing system built for large-scale data that lets you run T-SQL queries over data in data lake. It is serverless so you don't need to manage infrastructure.       |
diff --git a/articles/synapse-analytics/overview-faq.md b/articles/synapse-analytics/overview-faq.md
@@ -89,9 +89,9 @@ A: Data flow allows data engineers to develop graphical data transformation logi
 
 A: End-to-end single sign-on experience is an important authentication process in Synapse Analytics. Managing and passing the identity  through via a full AAD integration is a must.
 
-### Q: How do I get access to files and folders in the ADLSg2
+### Q: How do I get access to files and folders in the ADLS Gen2
 
-A: Access to files and folders is currently managed through ADLSg2. For more information, see [Data Lake storage access control](../storage/blobs/data-lake-storage-access-control.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json).
+A: Access to files and folders is currently managed through ADLS Gen2. For more information, see [Data Lake storage access control](../storage/blobs/data-lake-storage-access-control.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json).
 
 ### Q: Can I use third-party business intelligence tools to access Azure Synapse Analytics
 
diff --git a/articles/synapse-analytics/security/how-to-create-managed-private-endpoints.md b/articles/synapse-analytics/security/how-to-create-managed-private-endpoints.md
@@ -25,17 +25,17 @@ In Azure Synapse Studio, select the **Manage** tab from the left navigation. Sel
 
 ## Step 3: Select the data source type
 
-Select the data source type. In this case, the target data source is an ADLS gen2 account. Select **Continue**.
+Select the data source type. In this case, the target data source is an ADLS Gen2 account. Select **Continue**.
 ![Select a target data source type](./media/how-to-create-managed-private-endpoints/managed-private-endpoint-3.png)
 
 ## Step 4: Enter information about the data source
 
-In the next window, enter information about the data source. In this example, we're creating a Managed private endpoint to an ADLS gen2 account. Enter a **Name** for the Managed private endpoint. Provide an **Azure subscription** and a **Storage account name**. Select **Create**.
+In the next window, enter information about the data source. In this example, we're creating a Managed private endpoint to an ADLS Gen2 account. Enter a **Name** for the Managed private endpoint. Provide an **Azure subscription** and a **Storage account name**. Select **Create**.
 ![Enter target data source details](./media/how-to-create-managed-private-endpoints/managed-private-endpoint-4.png)
 
 ## Step 5: Verify that your Managed private endpoint was successfully created
 
-After submitting the request, you'll see its status. To verify the successful creation of your Managed private endpoint was created, check its *Provisioning State*. You may need to wait 1 minute and select **Refresh** to update the provisioning state. You can see that the Managed private endpoint to the ADLS gen2 account was successfully created.
+After submitting the request, you'll see its status. To verify the successful creation of your Managed private endpoint was created, check its *Provisioning State*. You may need to wait 1 minute and select **Refresh** to update the provisioning state. You can see that the Managed private endpoint to the ADLS Gen2 account was successfully created.
 
 You can also see that the *Approval State* is *Pending*. The owner of the target resource can approve or deny the private endpoint connection request. If the owner approves the private endpoint connection request, then a private link is established. If denied, then a private link isn't established.
 ![Managed private endpoint creation request status](./media/how-to-create-managed-private-endpoints/managed-private-endpoint-5.png)
diff --git a/articles/synapse-analytics/security/how-to-grant-workspace-managed-identity-permissions.md b/articles/synapse-analytics/security/how-to-grant-workspace-managed-identity-permissions.md
@@ -12,7 +12,7 @@ ms.reviewer: jrasnick
 
 # Grant permissions to workspace managed identity (preview)
 
-This article teaches you how to grant permissions to the managed identity in Azure synapse workspace. Permissions, in turn, allow access to SQL pools in the workspace and ADLS gen2 storage account through the Azure portal.
+This article teaches you how to grant permissions to the managed identity in Azure synapse workspace. Permissions, in turn, allow access to SQL pools in the workspace and ADLS Gen2 storage account through the Azure portal.
 
 >[!NOTE]
 >This workspace managed identity will be referred to as managed identity through the rest of this document.
@@ -25,47 +25,47 @@ Select **Security + networking** when you're creating your Azure Synapse workspa
 
 ![CONTROL permission on SQL pools](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-16.png)
 
-## Grant the managed identity permissions to ADLS gen2 storage account
+## Grant the managed identity permissions to ADLS Gen2 storage account
 
-An ADLS gen2 storage account is required to create an Azure Synapse workspace. To successfully launch Spark pools in Azure Synapse workspace, the Azure Synapse managed identity needs the *Storage Blob Data Contributor* role on this storage account . Pipeline orchestration in Azure Synapse also benefits from this role.
+An ADLS Gen2 storage account is required to create an Azure Synapse workspace. To successfully launch Spark pools in Azure Synapse workspace, the Azure Synapse managed identity needs the *Storage Blob Data Contributor* role on this storage account . Pipeline orchestration in Azure Synapse also benefits from this role.
 
 ### Grant permissions to managed identity during workspace creation
 
-Azure Synapse will attempt to grant the Storage Blob Data Contributor role to the managed identity after you create the Azure Synapse workspace using Azure portal. You provide the ADLS gen2 storage account details in the **Basics** tab.
+Azure Synapse will attempt to grant the Storage Blob Data Contributor role to the managed identity after you create the Azure Synapse workspace using Azure portal. You provide the ADLS Gen2 storage account details in the **Basics** tab.
 
 ![Basics tab in workspace creation flow](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-1.png)
 
-Choose the ADLS gen2 storage account and filesystem in **Account name** and **File system name**.
+Choose the ADLS Gen2 storage account and filesystem in **Account name** and **File system name**.
 
-![Providing an ADLS gen2 storage account details](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-2.png)
+![Providing an ADLS Gen2 storage account details](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-2.png)
 
-If the workspace creator is also **Owner** of the ADLS gen2 storage account, then Azure Synapse will assign the *Storage Blob Data Contributor* role to the managed identity. You'll see the following message below the storage account details that you entered.
+If the workspace creator is also **Owner** of the ADLS Gen2 storage account, then Azure Synapse will assign the *Storage Blob Data Contributor* role to the managed identity. You'll see the following message below the storage account details that you entered.
 
 ![Successful Storage Blob Data Contributor assignment](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-3.png)
 
-If the workspace creator isn't the owner of the ADLS gen2 storage account, then Azure Synapse doesn't assign the *Storage Blob Data Contributor* role to the managed identity. The message appearing below the storage account details notifies the workspace creator that they don't have sufficient permissions to grant the *Storage Blob Data Contributor* role to the managed identity.
+If the workspace creator isn't the owner of the ADLS Gen2 storage account, then Azure Synapse doesn't assign the *Storage Blob Data Contributor* role to the managed identity. The message appearing below the storage account details notifies the workspace creator that they don't have sufficient permissions to grant the *Storage Blob Data Contributor* role to the managed identity.
 
 ![Unsuccessful Storage Blob Data Contributor assignment](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-4.png)
 
 As the message states, you can't create Spark pools unless the *Storage Blob Data Contributor* is assigned to the managed identity.
 
 ### Grant permissions to managed identity after workspace creation
 
-During workspace creation, if you don't assign the *Storage Blob Data contributor* to the managed identity, then the **Owner** of the ADLS gen2 storage account manually assigns that role to the identity. The following steps will help you to accomplish manual assignment.
+During workspace creation, if you don't assign the *Storage Blob Data contributor* to the managed identity, then the **Owner** of the ADLS Gen2 storage account manually assigns that role to the identity. The following steps will help you to accomplish manual assignment.
 
-#### Step 1: Navigate to the ADLS gen2 storage account in Azure portal
+#### Step 1: Navigate to the ADLS Gen2 storage account in Azure portal
 
-In Azure portal, open the ADLS gen2 storage account and select **Overview** from the left navigation. You'll only need to assign The *Storage Blob Data Contributor* role at the container or filesystem level. Select **Containers**.  
-![ADLS gen2 storage account overview](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-5.png)
+In Azure portal, open the ADLS Gen2 storage account and select **Overview** from the left navigation. You'll only need to assign The *Storage Blob Data Contributor* role at the container or filesystem level. Select **Containers**.  
+![ADLS Gen2 storage account overview](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-5.png)
 
 #### Step 2: Select the container
 
 The managed identity should have data access to the container (file system) that was provided when the workspace was created. You can find this container or file system in Azure portal. Open the Azure Synapse workspace in Azure portal and select the **Overview** tab from the left navigation.
-![ADLS gen2 storage account container](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-7.png)
+![ADLS Gen2 storage account container](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-7.png)
 
 
 Select that same container or file system to grant the *Storage Blob Data Contributor* role to the managed identity.
-![ADLS gen2 storage account container selection](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-6.png)
+![ADLS Gen2 storage account container selection](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-6.png)
 
 #### Step 3: Navigate to Access control
 
@@ -110,7 +110,7 @@ Select **Access Control(IAM)** and then select **Role assignments**.
 ![Verify role assignment](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-14.png)
 
 You should see your managed identity listed under the **Storage Blob Data Contributor** section with the *Storage Blob Data Contributor* role assigned to it. 
-![ADLS gen2 storage account container selection](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-15.png)
+![ADLS Gen2 storage account container selection](./media/how-to-grant-workspace-managed-identity-permissions/configure-workspace-managed-identity-15.png)
 
 ## Next steps
 
diff --git a/articles/synapse-analytics/security/how-to-set-up-access-control.md b/articles/synapse-analytics/security/how-to-set-up-access-control.md
@@ -139,7 +139,7 @@ Synapse Studio will behave differently based on user roles. Some items may be hi
 | Open Synapse Studio | YES | YES | YES |
 | View Home hub | YES | YES | YES |
 | View Data Hub | YES | YES | YES |
-| Data Hub / See linked ADLSGen2 accounts and containers | YES [1] | YES[1] | YES[1] |
+| Data Hub / See linked ADLS Gen2 accounts and containers | YES [1] | YES[1] | YES[1] |
 | Data Hub / See Databases | YES | YES | YES |
 | Data Hub / See objects in databases | YES | YES | YES |
 | Data Hub / Access data in SQL pool databases | YES   | NO   | YES   |
@@ -173,8 +173,8 @@ Synapse Studio will behave differently based on user roles. Some items may be hi
 
 
 > [!NOTE]
-> [1] Access to data in containers depends on the access control in ADLSGen2. </br>
-> [2] SQL OD tables and Spark tables store their data in ADLSGen2 and access requires the appropriate permissions on ADLSGen2.
+> [1] Access to data in containers depends on the access control in ADLS Gen2. </br>
+> [2] SQL OD tables and Spark tables store their data in ADLS Gen2 and access requires the appropriate permissions on ADLS Gen2.
 
 ## Next steps
 
diff --git a/articles/synapse-analytics/spark/intellij-tool-synapse.md b/articles/synapse-analytics/spark/intellij-tool-synapse.md
@@ -138,7 +138,7 @@ After creating a Scala application, you can remotely run it.
     |Main class name|The default value is the main class from the selected file. You can change the class by selecting the ellipsis(**...**) and choosing another class.|
     |Job configurations|You can change the default key and values. For more information, see [Apache Livy REST API](https://livy.incubator.apache.org./docs/latest/rest-api.html).|
     |Command line arguments|You can enter arguments separated by space for the main class if needed.|
-    |Referenced Jars and Referenced Files|You can enter the paths for the referenced Jars and files if any. You can also browse files in the Azure virtual file system, which currently only supports ADLS Gen 2 cluster. For more information: [Apache Spark Configuration](https://spark.apache.org/docs/latest/configuration.html#runtime-environment) and [How to upload resources to cluster](../../storage/blobs/storage-quickstart-blobs-storage-explorer.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json).|
+    |Referenced Jars and Referenced Files|You can enter the paths for the referenced Jars and files if any. You can also browse files in the Azure virtual file system, which currently only supports ADLS Gen2 cluster. For more information: [Apache Spark Configuration](https://spark.apache.org/docs/latest/configuration.html#runtime-environment) and [How to upload resources to cluster](../../storage/blobs/storage-quickstart-blobs-storage-explorer.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json).|
     |Job Upload Storage|Expand to reveal additional options.|
     |Storage Type|Select **Use Azure Blob to upload** from the drop-down list.|
     |Storage Account|Enter your storage account.|
