Skip to content

Commit 80e7e9e

Browse files
committed
More edits
1 parent 950856d commit 80e7e9e

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
@@ -210,7 +210,7 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
210210
After you select **Send**, it might take up to five minutes for the FHIR resources to be available in the FHIR service.
211211

212212
> [!IMPORTANT]
213-
> 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 with all properties starting with `iothub`. For example: `iothub-creation-time-utc`. 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).
213+
> 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
>
215215
> Example:
216216
>

0 commit comments

Comments
 (0)