Skip to content

Commit cee6bb7

Browse files
committed
Final edit
1 parent d0af26a commit cee6bb7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/healthcare-apis/iot/device-messages-through-iot-hub.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,7 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
212212
> [!IMPORTANT]
213213
> To avoid device spoofing in device-to-cloud (D2C) messages, Azure IoT Hub enriches all device messages with additional properties before sending it to the MedTech service device event hub. For example: **Properties**: `iothub-creation-time-utc` and **SystemProperties**: `iothub-connection-device-id`. For more information, see [Anti-spoofing properties](../../iot-hub/iot-hub-devguide-messages-construct.md#anti-spoofing-properties) and [How to use IotJsonPathContent mappings](how-to-use-iot-jsonpath-content-mappings.md).
214214
>
215-
> You do not want to send this example device message to your IoT hub as the enrichment will be duplicated by the IoT hub and cause an error with your MedTech service. This is only an example of how your device messages are enrichment by the IoT hub.
215+
> You do not want to send this example device message to your IoT hub as the enrichments will be duplicated by the IoT hub and cause an error with your MedTech service. This is only an example of how your device messages are enriched by the IoT hub.
216216
>
217217
> Example:
218218
>

0 commit comments

Comments
 (0)