Addressing Acrolinx feedback, and adding references to TOC

Author: periclesrocha

articles/synapse-analytics/sql/tutorial-external-tables-using-managed-identity.md

@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: create external tables or ingest data from on ADLS Gen2 using a managed identity'
+title: 'Tutorial: Loading external data using a managed identity'
 description: This tutorial shows how to connect to external data for queries or ingestion using a managed identity.
 author: periclesrocha
 ms.service: azure-synapse-analytics
@@ -11,15 +11,13 @@ ms.author: periclesrocha
 ms.reviewer: WilliamDAssafMSFT 
 ---
 
-# Tutorial: create external tables or ingest data from on ADLS Gen2 using a managed identity
+# Tutorial: Loading external data using a managed identity
 
-Applies to: Azure Synapse Analytics
-
-This article explains how to create external tables or ingest data from Azure Data Lake Storage Gen2 accounts using a managed identity.
+This article explains how to create external tables or ingest data from Azure Data Lake Storage (ADLS) Gen2 accounts using a managed identity.
 
 ## Prerequisites:
 
-This tutorial requires the following resources to be in place:
+The following resources are required to complete this tutorial:
 
 * An Azure Data Lake Storage Gen2 (ADLS Gen2) account
 * An Azure Synapse Analytics workspace and a dedicated SQL Pool
@@ -30,14 +28,14 @@ Each Azure Synapse Analytics workspace automatically creates a managed identity
 
 To enable your managed identity to access data on ADLS Gen2 accounts, you need to give your identity access to the source account. To grant proper permissions, follow these steps:
 
-1. In the Azure Portal, find your storage account.
+1. In the Azure portal, find your storage account.
 2. Select **Data storage -> Containers**, and navigate to the folder where the source data the external table needs access to is.
 3. Select **Access control (IAM)**.
 4. Select **Add -> Add role assignment**.
 5. In the list of job function roles, select **Storage Blob Data Contributor** and select **Next**.
 6. In the Add role assignment page, select **+ Select members**. The Select members pane opens in the right-hand corner.
-7. Type the name of your workspace identity until it is displayed. The workspace identity is the same as your workspace name. Pick your workspace identity and chose **Select**.
-8. Back to the Add role assignment page, make sure the list of Members include your workspace identity. Once verified, select **Review + assign**.
+7. Type the name of your workspace identity. The workspace identity is the same as your workspace name. When displayed, pick your workspace identity and chose **Select**.
+8. In the **Add role assignment** page, make sure the list of Members include your desired Entra ID account. Once verified, select **Review + assign**.
 9. In the confirmation page, review the changes and select **Review + assign**.
 
 Your workspace identity is now a member of the Storage Blob Data Contributor role and has access to the source folder.
@@ -46,7 +44,7 @@ Note: these steps also apply to secure ADLS Gen2 accounts that are configured to
 
 ## Ingest data using COPY INTO
 
-The COPY INTO statement provides flexible, high-throughput data ingestion into your tables, and is the primary strategy to ingest data into your dedicated SQL Pool tables. It allows users to ingest data from external locations without having to create any of the additional database objects that are required for external tables.
+The COPY INTO statement provides flexible, high-throughput data ingestion into your tables, and is the primary strategy to ingest data into your dedicated SQL Pool tables. It allows users to ingest data from external locations without having to create any of the extra database objects that are required for external tables.
 
 To run the COPY INTO statement using a workspace managed identity for authentication, use the following command:
 
@@ -62,7 +60,7 @@ WITH
 
 Where:
 
-* \<TableName> is the name of the table you will ingest data into
+* \<TableName> is the name of the table you'll ingest data into
 * \<AccountName> is your ADLS Gen2 account name
 * \<Container> is the name of the container within your storage account where the source data is stored
 * \<Folder> is the folder (or path with subfolders) where the source data is stored within your container. You can also provide a file name if pointing directly to a single file.
@@ -86,11 +84,11 @@ External tables require the following objects to be created:
 4. An external file format that defines the format of the source files.
 5. An external table definition that is used for queries.
 
-To follow these steps, you will need to use the SQL editor in the Azure Synapse Workspace, or your preferred SQL client connected to your dedicated SQL Pool. Let’s look at these steps in detail.
+To follow these steps, you'll need to use the SQL editor in the Azure Synapse Workspace, or your preferred SQL client connected to your dedicated SQL Pool. Let’s look at these steps in detail.
 
 #### Create the database master key
 
-The database master key is a symmetric key used to protect the private keys of certificates and asymmetric keys that are present in the database and secrets in database scoped credentials. If there is already a master key in the database, you do not need to create a new one.
+The database master key is a symmetric key used to protect the private keys of certificates and asymmetric keys that are present in the database and secrets in database scoped credentials. If there's already a master key in the database, you don't need to create a new one.
 
 To create a master key, use the following command:
 
@@ -169,11 +167,11 @@ Where:
 
 * \<FileFormatName> is the name you want to use for your external file format
 
-In the example above, adjust parameters such as FIELD\_TERMINATOR, STRING\_DELIMITER, FIRST\_ROW and others as needed in accordance with your source data. For more formatting options and to learn more about EXTERNAL FILE FORMAT, visit <https://learn.microsoft.com/en-us/sql/t-sql/statements/create-external-file-format-transact-sql?view=azure-sqldw-latest&tabs=delimited>.
+In this example, adjust parameters such as FIELD_TERMINATOR, STRING_DELIMITER, FIRST_ROW and others as needed in accordance with your source data. For more formatting options and to learn more about EXTERNAL FILE FORMAT, visit <https://learn.microsoft.com/en-us/sql/t-sql/statements/create-external-file-format-transact-sql?view=azure-sqldw-latest&tabs=delimited>.
 
 #### Create the external table
 
-Now that we’ve created all the necessary objects that hold the metadata to securely access external data, it is time to create the external table. To create the external table, use the following command:
+Now that all the necessary objects that hold the metadata to securely access external data are created, it's time to create the external table. To create the external table, use the following command:
 
 ```sql
 -- Adjust the table name and columns to your desired name and external table schema
@@ -199,7 +197,7 @@ Where:
 
 Make sure to adjust the table name and schema to the desired name and the schema of the data in your source files.
 
-At this point, all the metadata required to access the external table has been created. To test your external table, use a simple query such as the one below:
+At this point, all the metadata required to access the external table are created. To test your external table, use a query such as the following one to validate your work:
 
 ```sql
 SELECT TOP 10 Col1, Col2 FROM <ExternalTableName>

articles/synapse-analytics/sql/tutorial-load-data-using-entra-id.md

@@ -11,9 +11,7 @@ ms.author: periclesrocha
 ms.reviewer: WilliamDAssafMSFT 
 ---
 
-# Tutorial: load data using Entra ID
-
-Applies to: Azure Synapse Analytics
+# Tutorial: Loading external data using Entra ID
 
 This article explains how to create external tables using Entra ID passthrough.
 
@@ -41,7 +39,32 @@ To enable access to data on Azure Data Lake Storage (ADLS) Gen2 accounts, you ne
 
 The Entra ID account or group is now a member of the Storage Blob Data Reader role and has access to the source folder.
 
-# Create the required database objects
+## Ingest data using COPY INTO
+
+The COPY INTO statement provides flexible, high-throughput data ingestion into your tables, and is the primary strategy to ingest data into your dedicated SQL Pool tables. It allows users to ingest data from external locations without having to create any of the extra database objects that are required for external tables.
+
+The COPY INTO statement uses the CREDENTIAL argument to specify the authentication mechanism used to connect to the source account. However, when authenticating using Microsoft Entra ID or to a public storage account, CREDENTIAL doesn't need to be specified. Therefore, to run the COPY INTO statement using a workspace managed identity for authentication, use the following command:
+
+```sql
+COPY INTO <TableName>
+FROM 'https://<AccountName>.dfs.core.windows.net/<Container>/<Folder>/ '
+WITH
+(
+    [<CopyIntoOptions>]
+)
+```
+
+Where:
+
+* \<TableName> is the name of the table to ingest data into
+* \<AccountName> is your ADLS Gen2 account name
+* \<Container> is the name of the container within your storage account where the source data is stored
+* \<Folder> is the folder (or path with subfolders) where the source data is stored within your container. You can also provide a file name if pointing directly to a single file.
+* \<CopyIntoOptions> is the list of any other options you wish to provide to the COPY INTO statement.
+
+To learn more and explore the full syntax of COPY INTO, refer to <https://learn.microsoft.com/en-us/sql/t-sql/statements/copy-into-transact-sql?view=azure-sqldw-latest>.
+
+## Create the required database objects
 
 External tables require the following objects to be created:
 

articles/synapse-analytics/toc.yml

@@ -320,6 +320,10 @@ items:
       href: ./sql/tutorial-logical-data-warehouse.md
     - name: Power BI Desktop
       href: ./sql/tutorial-connect-power-bi-desktop.md  
+    - name: Loading external data using Entra ID
+      href: ./sql/tutorial-load-data-using-entra-id.md  
+    - name: Loading external data using a Managed Identity
+      href: ./sql/tutorial-external-tables-using-managed-identity.md  
   - name: Concepts
     items:
     - name: Back up and restore