Skip to content

Commit 21b77a8

Browse files
committed
fixes after review
1 parent 93293f5 commit 21b77a8

File tree

6 files changed

+48
-46
lines changed

6 files changed

+48
-46
lines changed

articles/iot-central/TOC.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -185,12 +185,12 @@
185185
href: core/howto-export-to-azure-data-explorer.md
186186
- name: Export to a webhook
187187
href: core/howto-export-to-webhook.md
188-
- name: Export data to cloud destinations (legacy)
189-
href: core/howto-export-data-legacy.md
190-
- name: Transform data internally for export
191-
href: core/howto-transform-data-internally.md
192-
- name: Troubleshoot data export
193-
href: core/troubleshoot-data-export.md
188+
- name: Export data to cloud destinations (legacy)
189+
href: core/howto-export-data-legacy.md
190+
- name: Transform data internally for export
191+
href: core/howto-transform-data-internally.md
192+
- name: Troubleshoot data export
193+
href: core/troubleshoot-data-export.md
194194
- name: Export data and visualize with Databricks
195195
href: core/howto-create-custom-analytics.md
196196
- name: Transform data internally on ingress

articles/iot-central/core/howto-export-to-azure-data-explorer.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Export data to azure data explorer IoT Central | Microsoft Docs
3-
description: How to use the new data export to export your IoT data to azure data explorer
2+
title: Export data to Azure Data Explorer IoT Central | Microsoft Docs
3+
description: How to use the new data export to export your IoT data to Azure Data Explorer
44
services: iot-central
55
author: v-krishnag
66
ms.author: v-krishnag
@@ -9,13 +9,13 @@ ms.topic: how-to
99
ms.service: iot-central
1010
---
1111

12-
# Export IoT data to azure data explorer
12+
# Export IoT data to Azure Data Explorer
1313

14-
This article describes how to configure data export to send data to the azure data explorer.
14+
This article describes how to configure data export to send data to the Azure Data Explorer.
1515

1616
[!INCLUDE [iot-central-data-export](../../../includes/iot-central-data-export.md)]
1717

18-
## Set up an azure data explorer export destination
18+
## Set up an Azure Data Explorer export destination
1919

2020
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).
2121

@@ -196,4 +196,4 @@ To create the Azure Data Explorer destination in IoT Central on the **Data expor
196196
197197
## Next steps
198198
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).

articles/iot-central/core/howto-export-to-blob-storage.md

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Export data to Blob storage IoT Central | Microsoft Docs
3-
description: How to use the new data export to export your IoT data to blob storage
2+
title: Export data to Blob Storage IoT Central | Microsoft Docs
3+
description: How to use the new data export to export your IoT data to Blob Storage
44
services: iot-central
55
author: v-krishnag
66
ms.author: v-krishnag
@@ -9,13 +9,13 @@ ms.topic: how-to
99
ms.service: iot-central
1010
---
1111

12-
# Export IoT data to blob storage
12+
# Export IoT data to Blob Storage
1313

14-
This article describes how to configure data export to send data to the blob storage service.
14+
This article describes how to configure data export to send data to the Blob Storage service.
1515

1616
[!INCLUDE [iot-central-data-export](../../../includes/iot-central-data-export.md)]
1717

18-
## Set up a blob storage export destination
18+
## Set up a Blob Storage export destination
1919

2020

2121
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
4141

4242
If you don't have an existing Azure storage account to export to, follow these steps:
4343

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:
4545

4646
|Performance Tier|Account Type|
4747
|-|-|
@@ -66,13 +66,14 @@ To create the Blob Storage destination in IoT Central on the **Data export** pag
6666

6767
1. Select **Save**.
6868

69+
---
6970
# [Managed identity](#tab/managed-identity)
7071

7172
### Create an Azure Blob Storage destination
7273

7374
If you don't have an existing Azure storage account to export to, follow these steps:
7475

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:
7677

7778
|Performance Tier|Account Type|
7879
|-|-|
@@ -110,9 +111,10 @@ To create the Blob Storage destination in IoT Central on the **Data export** pag
110111

111112
1. Select **Save**.
112113

114+
---
113115
[!INCLUDE [iot-central-data-export-setup](../../../includes/iot-central-data-export-setup.md)]
114116

115-
For Blob storage, messages are batched and exported once per minute.
117+
For Blob Storage, messages are batched and exported once per minute.
116118

117119
The following example shows an exported telemetry message:
118120

@@ -151,9 +153,9 @@ The following example shows an exported telemetry message:
151153

152154
[!INCLUDE [iot-central-data-export-message-properties](../../../includes/iot-central-data-export-message-properties.md)]
153155

154-
For Blob storage, messages are batched and exported once per minute.
156+
For Blob Storage, messages are batched and exported once per minute.
155157

156-
The following snippet shows this property in the message exported to Blob storage:
158+
The following snippet shows this property in the message exported to Blob Storage:
157159

158160
```json
159161
{
@@ -175,7 +177,7 @@ The following snippet shows this property in the message exported to Blob storag
175177

176178
[!INCLUDE [iot-central-data-export-device-connectivity](../../../includes/iot-central-data-export-device-connectivity.md)]
177179

178-
For Blob storage, messages are batched and exported once per minute.
180+
For Blob Storage, messages are batched and exported once per minute.
179181

180182
The following example shows an exported device connectivity message received in Azure Blob Storage.
181183

@@ -197,7 +199,7 @@ The following example shows an exported device connectivity message received in
197199

198200
[!INCLUDE [iot-central-data-export-device-lifecycle](../../../includes/iot-central-data-export-device-lifecycle.md)]
199201

200-
For Blob storage, messages are batched and exported once per minute.
202+
For Blob Storage, messages are batched and exported once per minute.
201203

202204
The following example shows an exported device lifecycle message received in Azure Blob Storage.
203205

@@ -218,7 +220,7 @@ The following example shows an exported device lifecycle message received in Azu
218220

219221
[!INCLUDE [iot-central-data-export-device-template](../../../includes/iot-central-data-export-device-template.md)]
220222

221-
For Blob storage, messages are batched and exported once per minute.
223+
For Blob Storage, messages are batched and exported once per minute.
222224

223225
The following example shows an exported device lifecycle message received in Azure Blob Storage.
224226

@@ -238,4 +240,4 @@ The following example shows an exported device lifecycle message received in Azu
238240

239241
## Next steps
240242

241-
Now that you know how to export to blob storage, a suggested next step is to learn [Export to Service Bus](howto-export-to-service-bus.md).
243+
Now that you know how to export to Blob Storage, a suggested next step is to learn [Export to Service Bus](howto-export-to-service-bus.md).

articles/iot-central/core/howto-export-to-event-hubs.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Export data to event hubs IoT Central | Microsoft Docs
3-
description: How to use the new data export to export your IoT data to event hubs
2+
title: Export data to Event Hubs IoT Central | Microsoft Docs
3+
description: How to use the new data export to export your IoT data to Event Hubs
44
services: iot-central
55
author: v-krishnag
66
ms.author: v-krishnag
@@ -9,13 +9,13 @@ ms.topic: how-to
99
ms.service: iot-central
1010
---
1111

12-
# Export IoT data to event hubs
12+
# Export IoT data to Event Hubs
1313

14-
This article describes how to configure data export to send data to the event hubs.
14+
This article describes how to configure data export to send data to the Event Hubs.
1515

1616
[!INCLUDE [iot-central-data-export](../../../includes/iot-central-data-export.md)]
1717

18-
## Set up an event hubs export destination
18+
## Set up an Event Hubs export destination
1919

2020
IoT Central exports data in near real time. The data is in the message body and is in JSON format encoded as UTF-8.
2121

@@ -118,4 +118,4 @@ For Event Hubs, IoT Central exports new messages data to your event hub or Servi
118118

119119
## Next steps
120120

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).

articles/iot-central/core/howto-export-to-service-bus.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Export data to service bus IoT Central | Microsoft Docs
3-
description: How to use the new data export to export your IoT data to service bus
2+
title: Export data to Service Bus IoT Central | Microsoft Docs
3+
description: How to use the new data export to export your IoT data to Service Bus
44
services: iot-central
55
author: v-krishnag
66
ms.author: v-krishnag
@@ -9,13 +9,13 @@ ms.topic: how-to
99
ms.service: iot-central
1010
---
1111

12-
# Export IoT data to service bus
12+
# Export IoT data to Service Bus
1313

14-
This article describes how to configure data export to send data to the service bus.
14+
This article describes how to configure data export to send data to the Service Bus.
1515

1616
[!INCLUDE [iot-central-data-export](../../../includes/iot-central-data-export.md)]
1717

18-
## Set up an service bus export destination
18+
## Set up an Service Bus export destination
1919

2020
Both queues and topics are supported for Azure Service Bus destinations.
2121

@@ -122,4 +122,4 @@ For Service Bus, IoT Central exports new messages data to your event hub or Serv
122122

123123
## Next steps
124124

125-
Now that you know how to export to service bus, a suggested next step is to learn [Export to Event Hubs](howto-export-to-event-hubs.md).
125+
Now that you know how to export to Service Bus, a suggested next step is to learn [Export to Event Hubs](howto-export-to-event-hubs.md).

articles/iot-central/core/howto-export-to-webhook.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Export data to webhook IoT Central | Microsoft Docs
3-
description: How to use the new data export to export your IoT data to webhook
2+
title: Export data to Webhook IoT Central | Microsoft Docs
3+
description: How to use the new data export to export your IoT data to Webhook
44
services: iot-central
55
author: v-krishnag
66
ms.author: v-krishnag
@@ -11,17 +11,17 @@ ms.service: iot-central
1111

1212
# Export IoT data to Webhook
1313

14-
This article describes how to configure data export to send data to the webhook.
14+
This article describes how to configure data export to send data to the Webhook.
1515

1616
[!INCLUDE [iot-central-data-export](../../../includes/iot-central-data-export.md)]
1717

18-
## Set up an webhook export destination
18+
## Set up an Webhook export destination
1919

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.
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.
2121

22-
## Create a webhook destination
22+
## Create a Webhook destination
2323

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:
2525

2626
1. Open [RequestBin](https://requestbin.net/).
2727
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
3232

3333
1. Select **Webhook** as the destination type.
3434

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.
3636

3737
- 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.
3838
- 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

Comments
 (0)