You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
29
+
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#supported-data-stores-and-formats](copy-activity-overview.md) table.
30
30
31
31
>[!NOTE]
32
32
>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.
@@ -56,10 +56,10 @@ The Azure Data Explorer connector uses service principal authentication. Follow
56
56
- Application key
57
57
- Tenant ID
58
58
59
-
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 need to
59
+
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:
60
60
61
-
-**As source**, grant at least **Database viewer** role to your database
62
-
-**As sink**, grant at least **Database ingestor** role to your database
61
+
-**As source**, grant at least the **Database viewer** role to your database
62
+
-**As sink**, grant at least the **Database ingestor** role to your database
63
63
64
64
>[!NOTE]
65
65
>When you use the ADF 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.
@@ -71,9 +71,9 @@ The following properties are supported for the Azure Data Explorer linked servic
71
71
| type | The **type** property must be set to **AzureDataExplorer**. | Yes |
72
72
| endpoint | Endpoint URL of the Azure Data Explorer cluster, with the format as `https://<clusterName>.<regionName>.kusto.windows.net`. | Yes |
73
73
| database | Name of database. | Yes |
74
-
| tenant | Specify the tenant information (domain name or tenant ID) under which your application resides. This is generally 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 with the mouse in the upper-right corner of the Azure portal. | Yes |
74
+
| tenant | Specify the tenant information (domain name or tenant ID) under which your application resides. This is generally 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 |
75
75
| servicePrincipalId | Specify the application's client ID. This is generally known as "AAD application client ID" in [Kusto connection string](https://docs.microsoft.com/azure/kusto/api/connection-strings/kusto#application-authentication-properties). | Yes |
76
-
| servicePrincipalKey | Specify the application's key. This is generally 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 a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). | Yes |
76
+
| servicePrincipalKey | Specify the application's key. This is generally 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 |
77
77
78
78
**Linked Service Properties Example:**
79
79
@@ -98,7 +98,7 @@ The following properties are supported for the Azure Data Explorer linked servic
98
98
99
99
## Dataset properties
100
100
101
-
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.
101
+
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 provides a list of properties that are supported by the Azure Data Explorer dataset.
102
102
103
103
To copy data to Azure Data Explorer, set the type property of the dataset to **AzureDataExplorerTable**.
104
104
@@ -130,7 +130,7 @@ The following properties are supported:
130
130
131
131
## Copy activity properties
132
132
133
-
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.
133
+
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 supported by Azure Data Explorer source and sink.
134
134
135
135
### Azure Data Explorer as source
136
136
@@ -186,7 +186,7 @@ To copy data to Azure Data Explorer, set the type property in the copy activity
186
186
| Property | Description | Required |
187
187
|:--- |:--- |:--- |
188
188
| type | The **type** property of the copy activity sink must be set to: **AzureDataExplorerSink**. | Yes |
189
-
| 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), 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 |
189
+
| 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 |
190
190
191
191
**Example:**
192
192
@@ -228,4 +228,4 @@ For more information about the properties, see [Lookup activity](control-flow-lo
228
228
229
229
* 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).
230
230
231
-
* Learn more about [Copy data from Azure Data Factory to Azure Data Explorer](/azure/data-explorer/data-factory-load-data).
231
+
* Learn more about how to [copy data from Azure Data Factory to Azure Data Explorer](/azure/data-explorer/data-factory-load-data).
0 commit comments