Skip to content

Commit 5b7e6e7

Browse files
(Azure CXP) Fixing Maximum desired properties size
Fixing Maximum desired properties size to 32 KB as per https://github.com/microsoftdocs/azure-docs/issues/48535
1 parent 79ed273 commit 5b7e6e7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Here is a detailed comparison of the various device-to-cloud communication optio
2828
| ---- | ------- | ---------- | ---- |
2929
| Scenario | Telemetry time series and alerts. For example, 256-KB sensor data batches sent every 5 minutes. | Available capabilities and conditions. For example, the current device connectivity mode such as cellular or WiFi. Synchronizing long-running workflows, such as configuration and software updates. | Media files. Large (typically compressed) telemetry batches. |
3030
| Storage and retrieval | Temporarily stored by IoT Hub, up to 7 days. Only sequential reading. | Stored by IoT Hub in the device twin. Retrievable using the [IoT Hub query language](iot-hub-devguide-query-language.md). | Stored in user-provided Azure Storage account. |
31-
| Size | Up to 256-KB messages. | Maximum reported properties size is 8 KB. | Maximum file size supported by Azure Blob Storage. |
31+
| Size | Up to 256-KB messages. | Maximum reported properties size is 32 KB. | Maximum file size supported by Azure Blob Storage. |
3232
| Frequency | High. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). | Medium. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). | Low. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). |
3333
| Protocol | Available on all protocols. | Available using MQTT or AMQP. | Available when using any protocol, but requires HTTPS on the device. |
3434

@@ -37,4 +37,4 @@ An application may need to send information both as a telemetry time series or a
3737
* The device app sends a device-to-cloud message and reports a property change.
3838
* The solution back end can store the information in the device twin's tags when it receives the message.
3939

40-
Since device-to-cloud messages enable a much higher throughput than device twin updates, it is sometimes desirable to avoid updating the device twin for every device-to-cloud message.
40+
Since device-to-cloud messages enable a much higher throughput than device twin updates, it is sometimes desirable to avoid updating the device twin for every device-to-cloud message.

0 commit comments

Comments
 (0)