Skip to content

Commit b8edd0d

Browse files
committed
changes for json
1 parent af1401b commit b8edd0d

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

articles/event-grid/event-schema-iot-hub.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ For **Device Telemetry** IoT Hub event, the data object contains the device-to-c
176176
| -------- | ---- | ----------- |
177177
| body | string | The content of the message from the device. |
178178
| properties | string | Application properties are user-defined strings that can be added to the message. These fields are optional. |
179-
| system properties | string | [System properties](../iot-hub/iot-hub-devguide-routing-query-syntax.md#system-properties) help identify contents and source of the messages. |
179+
| system properties | string | [System properties](../iot-hub/iot-hub-devguide-routing-query-syntax.md#system-properties) help identify contents and source of the messages. Device telemetry message must be in a valid JSON format with the contentType set to JSON and contentEncoding set to UTF-8 in the message system properties. If this is not set, then IoT Hub will write the messages in base 64 encoded format. |
180180

181181
For **Device Created** and **Device Deleted** IoT Hub events, the data object contains the following properties:
182182

articles/iot-hub/iot-hub-devguide-messages-d2c.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ You can use standard [Event Hubs integration and SDKs](iot-hub-devguide-messages
3434

3535
### Azure Blob Storage
3636

37-
IoT Hub supports writing data to Azure Blob Storage in the [Apache Avro](https://avro.apache.org/) format as well as in JSON format. The capability to encode JSON format is generally available in all regions in which IoT Hub is available. The default is AVRO. The encoding format can be only set when the blob storage endpoint is configured. The format cannot be edited for an existing endpoint. When using JSON encoding, you must set the contentType to JSON and contentEncoding to UTF-8 in the message [system properties](iot-hub-devguide-routing-query-syntax.md#system-properties). You can select the encoding format using the IoT Hub Create or Update REST API, specifically the [RoutingStorageContainerProperties](https://docs.microsoft.com/rest/api/iothub/iothubresource/createorupdate#routingstoragecontainerproperties), the Azure portal, [Azure CLI](https://docs.microsoft.com/cli/azure/iot/hub/routing-endpoint?view=azure-cli-latest), or the [Azure Powershell](https://docs.microsoft.com/powershell/module/az.iothub/add-aziothubroutingendpoint?view=azps-1.3.0). The following diagram shows how to select the encoding format in the Azure portal.
37+
IoT Hub supports writing data to Azure Blob Storage in the [Apache Avro](https://avro.apache.org/) format as well as in JSON format. The capability to encode JSON format is generally available in all regions in which IoT Hub is available. The default is AVRO. The encoding format can be only set when the blob storage endpoint is configured. The format cannot be edited for an existing endpoint. When using JSON encoding, you must set the contentType to JSON and contentEncoding to UTF-8 in the message [system properties](iot-hub-devguide-routing-query-syntax.md#system-properties). If this is not set, then IoT Hub will write the messages in base 64 encoded format. You can select the encoding format using the IoT Hub Create or Update REST API, specifically the [RoutingStorageContainerProperties](https://docs.microsoft.com/rest/api/iothub/iothubresource/createorupdate#routingstoragecontainerproperties), the Azure portal, [Azure CLI](https://docs.microsoft.com/cli/azure/iot/hub/routing-endpoint?view=azure-cli-latest), or the [Azure Powershell](https://docs.microsoft.com/powershell/module/az.iothub/add-aziothubroutingendpoint?view=azps-1.3.0). The following diagram shows how to select the encoding format in the Azure portal.
3838

3939
![Blob storage endpoint encoding](./media/iot-hub-devguide-messages-d2c/blobencoding.png)
4040

articles/iot-hub/iot-hub-event-grid.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ The following example shows the schema of a device connected event:
6767

6868
### Device Telemetry schema
6969

70-
The following example shows the schema of a device telemetry event:
70+
Device telemetry message must be in a valid JSON format with the contentType set to JSON and contentEncoding set to UTF-8 in the message [system properties](iot-hub-devguide-routing-query-syntax.md#system-properties). If this is not set, then IoT Hub will write the messages in base 64 encoded format. The following example shows the schema of a device telemetry event:
7171

7272
```json
7373
[{

0 commit comments

Comments
 (0)