Merge pull request #89425 from v-rihow/connector-azure-data-explorer

edit pass: connector-azure-data-explorer

Author: ShawnJackson

articles/data-factory/connector-azure-data-explorer.md

@@ -15,9 +15,9 @@ ms.date: 08/01/2019
 ms.author: orspodek
 ---
 
-# Copy data to or from Azure Data Explorer using Azure Data Factory
+# Copy data to or from Azure Data Explorer by using Azure Data Factory
 
-This article outlines how to use the Copy Activity in Azure Data Factory to copy data to or from [Azure Data Explorer](../data-explorer/data-explorer-overview.md). It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
+This article describes how to use the copy activity in Azure Data Factory to copy data to or from [Azure Data Explorer](../data-explorer/data-explorer-overview.md). It builds on the [copy activity overview](copy-activity-overview.md) article, which offers a general overview of copy activity.
 
 ## Supported capabilities
 
@@ -26,12 +26,12 @@ This Azure Data Explorer connector is supported for the following activities:
 - [Copy activity](copy-activity-overview.md) with [supported source/sink matrix](copy-activity-overview.md)
 - [Lookup activity](control-flow-lookup-activity.md)
 
-You can copy data from any supported source data store to Azure Data Explorer. You can also copy data from Azure Data Explorer to any supported sink data store. For a list of data stores that are supported as sources or sinks by the copy activity, see the [Supported data stores](copy-activity-overview.md) table.
+You can copy data from any supported source data store to Azure Data Explorer. You can also copy data from Azure Data Explorer to any supported sink data store. For a list of data stores that the copy activity supports as sources or sinks, see the [Supported data stores](copy-activity-overview.md#supported-data-stores-and-formats) table.
 
 >[!NOTE]
->Copying data to/from Azure Data Explorer from/to on premises data store using Self-hosted Integration Runtime is supported since version 3.14.
+>Copying data to or from Azure Data Explorer through an on-premises data store by using self-hosted integration runtime is supported in version 3.14 and later.
 
-The Azure Data Explorer connector allows you to do the following:
+With the Azure Data Explorer connector, you can do the following:
 
 * Copy data by using Azure Active Directory (Azure AD) application token authentication with a **service principal**.
 * As a source, retrieve data by using a KQL (Kusto) query.
@@ -40,42 +40,42 @@ The Azure Data Explorer connector allows you to do the following:
 ## Getting started
 
 >[!TIP]
->For a walkthrough of using Azure Data Explorer connector, see [Copy data to/from Azure Data Explorer using Azure Data Factory](../data-explorer/data-factory-load-data.md).
+>For a walkthrough of Azure Data Explorer connector, see [Copy data to/from Azure Data Explorer using Azure Data Factory](../data-explorer/data-factory-load-data.md).
 
 [!INCLUDE [data-factory-v2-connector-get-started](../../includes/data-factory-v2-connector-get-started.md)]
 
 The following sections provide details about properties that are used to define Data Factory entities specific to Azure Data Explorer connector.
 
 ## Linked service properties
 
-The Azure Data Explorer connector uses service principal authentication. Follow these steps to get a service principal and grant permissions:
+The Azure Data Explorer connector uses service principal authentication. Follow these steps to get a service principal and to grant permissions:
 
-1. Register an application entity in Azure Active Directory (Azure AD) by following [Register your application with an Azure AD tenant](../storage/common/storage-auth-aad-app.md#register-your-application-with-an-azure-ad-tenant). Make note of the following values, which you use to define the linked service:
+1. Register an application entity in Azure Active Directory by following the steps in [Register your application with an Azure AD tenant](../storage/common/storage-auth-aad-app.md#register-your-application-with-an-azure-ad-tenant). Make note of the following values, which you use to define the linked service:
 
     - Application ID
     - Application key
     - Tenant ID
 
-2. Grant the service principal proper permission in Azure Data Explorer. Refer to [Manage Azure Data Explorer database permissions](../data-explorer/manage-database-permissions.md) with detailed information on roles and permissions as well as walk through on managing permissions. In general, you need to
+2. Grant the service principal the correct permissions in Azure Data Explorer. See [Manage Azure Data Explorer database permissions](../data-explorer/manage-database-permissions.md) for detailed information about roles and permissions and about managing permissions. In general, you must:
 
-    - **As source**, grant at least **Database viewer** role to your database.
-    - **As sink**, grant at least **Database ingestor** role to your database.
+    - **As source**, grant at least the **Database viewer** role to your database
+    - **As sink**, grant at least the **Database ingestor** role to your database
 
 >[!NOTE]
->When using ADF UI to author, your login user account is used to list Azure Data Explorer clusters, databases and tables. Manually input the name if you don’t have permission for such operation.
+>When you use the Data Factory UI to author, your login user account is used to list Azure Data Explorer clusters, databases, and tables. Manually enter the name if you don’t have permission for these operations.
 
-The following properties are supported for Azure Data Explorer linked service:
+The following properties are supported for the Azure Data Explorer linked service:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
-| type | The **type** property must be set to **AzureDataExplorer** | Yes |
+| type | The **type** property must be set to **AzureDataExplorer**. | Yes |
 | endpoint | Endpoint URL of the Azure Data Explorer cluster, with the format as `https://<clusterName>.<regionName>.kusto.windows.net`. | Yes |
 | database | Name of database. | Yes |
-| tenant | Specify the tenant information (domain name or tenant ID) under which your application resides. This is what you normally know as "**Authority ID**" in [Kusto connection string](https://docs.microsoft.com/azure/kusto/api/connection-strings/kusto#application-authentication-properties). Retrieve it by hovering with the mouse in the top-right corner of the Azure portal. | Yes |
-| servicePrincipalId | Specify the application's client ID. This is what you normally know as "**AAD application client ID**" in [Kusto connection string](https://docs.microsoft.com/azure/kusto/api/connection-strings/kusto#application-authentication-properties). | Yes |
-| servicePrincipalKey | Specify the application's key. This is what you normally know as "**AAD application key**" in [Kusto connection string](https://docs.microsoft.com/azure/kusto/api/connection-strings/kusto#application-authentication-properties). Mark this field as a **SecureString** to store it securely in Data Factory, or [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). | Yes |
+| tenant | Specify the tenant information (domain name or tenant ID) under which your application resides. This is known as "Authority ID" in [Kusto connection string](https://docs.microsoft.com/azure/kusto/api/connection-strings/kusto#application-authentication-properties). Retrieve it by hovering the mouse pointer in the upper-right corner of the Azure portal. | Yes |
+| servicePrincipalId | Specify the application's client ID. This is known as "AAD application client ID" in [Kusto connection string](https://docs.microsoft.com/azure/kusto/api/connection-strings/kusto#application-authentication-properties). | Yes |
+| servicePrincipalKey | Specify the application's key. This is known as "AAD application key" in [Kusto connection string](https://docs.microsoft.com/azure/kusto/api/connection-strings/kusto#application-authentication-properties). Mark this field as a **SecureString** to store it securely in Data Factory, or [reference secure data stored in Azure Key Vault](store-credentials-in-key-vault.md). | Yes |
 
-**Linked Service Properties Example:**
+**Linked service properties example:**
 
 ```json
 {
@@ -98,18 +98,18 @@ The following properties are supported for Azure Data Explorer linked service:
 
 ## Dataset properties
 
-For a full list of sections and properties available for defining datasets, see the [datasets](concepts-datasets-linked-services.md) article. This section provides a list of properties that are supported by the Azure Data Explorer dataset.
+For a full list of sections and properties available for defining datasets, see [Datasets in Azure Data Factory](concepts-datasets-linked-services.md). This section lists properties that the Azure Data Explorer dataset supports.
 
 To copy data to Azure Data Explorer, set the type property of the dataset to **AzureDataExplorerTable**.
 
 The following properties are supported:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
-| type | The **type** property must be set to **AzureDataExplorerTable** | Yes |
+| type | The **type** property must be set to **AzureDataExplorerTable**. | Yes |
 | table | The name of the table that the linked service refers to. | Yes for sink; No for source |
 
-**Dataset Properties Example**
+**Dataset properties example:**
 
 ```json
 {
@@ -130,7 +130,7 @@ The following properties are supported:
 
 ## Copy activity properties
 
-For a full list of sections and properties available for defining activities, see the [Pipelines](concepts-pipelines-activities.md) article. This section provides a list of properties supported by Azure Data Explorer source and sink.
+For a full list of sections and properties available for defining activities, see [Pipelines and activities in Azure Data Factory](concepts-pipelines-activities.md). This section provides a list of properties that Azure Data Explorer sources and sinks support.
 
 ### Azure Data Explorer as source
 
@@ -141,10 +141,10 @@ To copy data from Azure Data Explorer, set the **type** property in the Copy act
 | type | The **type** property of the copy activity source must be set to: **AzureDataExplorerSource** | Yes |
 | query | A read-only request given in a [KQL format](/azure/kusto/query/). Use the custom KQL query as a reference. | Yes |
 | queryTimeout | The wait time before the query request times out. Default value is 10 min (00:10:00); allowed max value is 1 hour (01:00:00). | No |
-| noTruncation | Indicates whether to truncate the returned result set. By default, result is truncated after 500,000 records or 64 MB. Truncation is strongly recommended for a proper behavior of the activity. |No |
+| noTruncation | Indicates whether to truncate the returned result set. By default, result is truncated after 500,000 records or 64 megabytes (MB). Truncation is strongly recommended to ensure the correct behavior of the activity. |No |
 
 >[!NOTE]
->Azure Data Explorer source by default has a size limit of 500,000 records or 64 MB. To retrieve all the records without truncation, you can specify `set notruncation;` at the beginning of your query. Refer to [Query limits](https://docs.microsoft.com/azure/kusto/concepts/querylimits) on more details.
+>By default, Azure Data Explorer source has a size limit of 500,000 records or 64 MB. To retrieve all the records without truncation, you can specify `set notruncation;` at the beginning of your query. For more information, see [Query limits](https://docs.microsoft.com/azure/kusto/concepts/querylimits).
 
 **Example:**
 
@@ -185,8 +185,8 @@ To copy data to Azure Data Explorer, set the type property in the copy activity
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
-| type | The **type** property of the copy activity sink must be set to: **AzureDataExplorerSink** | Yes |
-| ingestionMappingName | Name of a pre-created **[mapping](/azure/kusto/management/mappings#csv-mapping)** on a Kusto table. To map the columns from source to Azure Data Explorer - which applies to **[all supported source stores/formats](copy-activity-overview.md#supported-data-stores-and-formats)** including CSV/JSON/Avro formats etc., you can use the Copy activity [column mapping](copy-activity-schema-and-type-mapping.md) (implicitly by name or explicitly as configured) and/or Azure Data Explorer mappings. | No |
+| type | The **type** property of the copy activity sink must be set to: **AzureDataExplorerSink**. | Yes |
+| ingestionMappingName | Name of a pre-created [mapping](/azure/kusto/management/mappings#csv-mapping) on a Kusto table. To map the columns from source to Azure Data Explorer (which applies to [all supported source stores and formats](copy-activity-overview.md#supported-data-stores-and-formats), including CSV/JSON/Avro formats), you can use the copy activity [column mapping](copy-activity-schema-and-type-mapping.md) (implicitly by name or explicitly as configured) and/or Azure Data Explorer mappings. | No |
 
 **Example:**
 
@@ -222,10 +222,10 @@ To copy data to Azure Data Explorer, set the type property in the copy activity
 
 ## Lookup activity properties
 
-To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
+For more information about the properties, see [Lookup activity](control-flow-lookup-activity.md).
 
 ## Next steps
 
-* For a list of data stores supported as sources and sinks by the copy activity in Azure Data Factory, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).
+* For a list of data stores that the copy activity in Azure Data Factory supports as sources and sinks, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).
 
-* Learn more about [Copy data from Azure Data Factory to Azure Data Explorer](/azure/data-explorer/data-factory-load-data).
+* Learn more about how to [copy data from Azure Data Factory to Azure Data Explorer](/azure/data-explorer/data-factory-load-data).