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
## Set up an azure data explorer export destination
18
+
## Set up an Azure Data Explorer export destination
19
19
20
20
You can use an [Azure Data Explorer cluster](/azure/data-explorer/data-explorer-overview) or an [Azure Synapse Data Explorer pool](../../synapse-analytics/data-explorer/data-explorer-overview.md). To learn more, see [What is the difference between Azure Synapse Data Explorer and Azure Data Explorer?](../..//synapse-analytics/data-explorer/data-explorer-compare.md).
21
21
@@ -196,4 +196,4 @@ To create the Azure Data Explorer destination in IoT Central on the **Data expor
196
196
197
197
## Next steps
198
198
199
-
Now that you know how to export to azure data explorer, a suggested next step is to learn [Export to Webhook](howto-export-to-webhook.md).
199
+
Now that you know how to export to Azure Data Explorer, a suggested next step is to learn [Export to Webhook](howto-export-to-webhook.md).
IoT Central exports data once per minute, with each file containing the batch of changes since the previous export. Exported data is saved in JSON format. The default paths to the exported data in your storage account are:
@@ -41,7 +41,7 @@ This article shows how to create a managed identity in the Azure portal. You can
41
41
42
42
If you don't have an existing Azure storage account to export to, follow these steps:
43
43
44
-
1. Create a [new storage account in the Azure portal](https://portal.azure.com/#create/Microsoft.StorageAccount-ARM). You can learn more about creating new [Azure Blob storage accounts](../../storage/blobs/storage-quickstart-blobs-portal.md) or [Azure Data Lake Storage v2 storage accounts](../../storage/common/storage-account-create.md). Data export can only write data to storage accounts that support block blobs. The following list shows the known compatible storage account types:
44
+
1. Create a [new storage account in the Azure portal](https://portal.azure.com/#create/Microsoft.StorageAccount-ARM). You can learn more about creating new [Azure Blob Storage accounts](../../storage/blobs/storage-quickstart-blobs-portal.md) or [Azure Data Lake Storage v2 storage accounts](../../storage/common/storage-account-create.md). Data export can only write data to storage accounts that support block blobs. The following list shows the known compatible storage account types:
45
45
46
46
|Performance Tier|Account Type|
47
47
|-|-|
@@ -66,13 +66,14 @@ To create the Blob Storage destination in IoT Central on the **Data export** pag
66
66
67
67
1. Select **Save**.
68
68
69
+
---
69
70
# [Managed identity](#tab/managed-identity)
70
71
71
72
### Create an Azure Blob Storage destination
72
73
73
74
If you don't have an existing Azure storage account to export to, follow these steps:
74
75
75
-
1. Create a [new storage account in the Azure portal](https://portal.azure.com/#create/Microsoft.StorageAccount-ARM). You can learn more about creating new [Azure Blob storage accounts](../../storage/blobs/storage-quickstart-blobs-portal.md) or [Azure Data Lake Storage v2 storage accounts](../../storage/common/storage-account-create.md). Data export can only write data to storage accounts that support block blobs. The following list shows the known compatible storage account types:
76
+
1. Create a [new storage account in the Azure portal](https://portal.azure.com/#create/Microsoft.StorageAccount-ARM). You can learn more about creating new [Azure Blob Storage accounts](../../storage/blobs/storage-quickstart-blobs-portal.md) or [Azure Data Lake Storage v2 storage accounts](../../storage/common/storage-account-create.md). Data export can only write data to storage accounts that support block blobs. The following list shows the known compatible storage account types:
76
77
77
78
|Performance Tier|Account Type|
78
79
|-|-|
@@ -110,9 +111,10 @@ To create the Blob Storage destination in IoT Central on the **Data export** pag
IoT Central exports data in near real time. The data is in the message body and is in JSON format encoded as UTF-8.
21
21
@@ -118,4 +118,4 @@ For Event Hubs, IoT Central exports new messages data to your event hub or Servi
118
118
119
119
## Next steps
120
120
121
-
Now that you know how to export to event hubs, a suggested next step is to learn [Export to Azure Data Explorer](howto-export-to-azure-data-explorer.md).
121
+
Now that you know how to export to Event Hubs, a suggested next step is to learn [Export to Azure Data Explorer](howto-export-to-azure-data-explorer.md).
For webhook destinations, IoT Central exports data in near real time. The data in the message body is in the same format as for Event Hubs and Service Bus.
20
+
For Webhook destinations, IoT Central exports data in near real time. The data in the message body is in the same format as for Event Hubs and Service Bus.
21
21
22
-
## Create a webhook destination
22
+
## Create a Webhook destination
23
23
24
-
You can export data to a publicly available HTTP webhook endpoint. You can create a test webhook endpoint using [RequestBin](https://requestbin.net/). RequestBin throttles request when the request limit is reached:
24
+
You can export data to a publicly available HTTP Webhook endpoint. You can create a test Webhook endpoint using [RequestBin](https://requestbin.net/). RequestBin throttles request when the request limit is reached:
25
25
26
26
1. Open [RequestBin](https://requestbin.net/).
27
27
1. Create a new RequestBin and copy the **Bin URL**. You use this URL when you test your data export.
@@ -32,7 +32,7 @@ To create the Azure Data Explorer destination in IoT Central on the **Data expor
32
32
33
33
1. Select **Webhook** as the destination type.
34
34
35
-
1. Paste the callback URL for your webhook endpoint. You can optionally configure webhook authorization and add custom headers.
35
+
1. Paste the callback URL for your Webhook endpoint. You can optionally configure Webhook authorization and add custom headers.
36
36
37
37
- For **OAuth2.0**, only the client credentials flow is supported. When you save the destination, IoT Central communicates with your OAuth provider to retrieve an authorization token. This token is attached to the `Authorization` header for every message sent to this destination.
38
38
- For **Authorization token**, you can specify a token value that's directly attached to the `Authorization` header for every message sent to this destination.
0 commit comments