Skip to main content

General

Export to Azure IoT Hub

Secure device telemetry export to Azure IoT Hub using MQTT over TLS.

Send device telemetry to Azure IoT Hub using the Proxus outbound connector. The integration uses Azure's device SDK over MQTT with automatic retries, plus a flat telemetry message format that is consistent with AWS IoT exports.

open_in_new

Azure IoT Hub Documentation

learn.microsoft.com/azure/iot-hub

Configuration Parameters

ParameterRequiredTypeDefaultDescription
HostNameYesstring-IoT Hub host name (e.g., myhub.azure-devices.net).
DeviceIdYesstring-Device ID registered in IoT Hub.
SharedAccessKeyYesstring-Device key for SAS authentication.
ValueModeNostringMeasureValueFieldsData serialization mode: MeasureValueFields or siemens.
RetryMaxAttemptsNoint5Max retry attempts for transient failures.
RetryMinBackoffMsNoint200Minimum backoff for retry policy.
RetryMaxBackoffMsNoint5000Maximum backoff for retry policy.
RetryDeltaBackoffMsNoint200Delta backoff step for retry policy.
OperationTimeoutMsNoint30000Operation timeout for SDK calls.

[!NOTE] Authentication uses device-level credentials. Ensure the device exists in IoT Hub and has a valid SAS key.

Message Format

Each payload entry is sent as a flat JSON message. This format matches the AWS IoT connector for consistency.

Default Mode (MeasureValueFields)

{
  "deviceId": "dev-1",
  "deviceName": "sensor-1",
  "measureName": "Temperature",
  "timestamp": "2024-02-01T00:00:00.000Z",
  "measureValueType": "DOUBLE",
  "measureValueDouble": 25.5
}

Siemens Mode (siemens)

{
  "deviceId": "dev-22",
  "deviceName": "line-2",
  "measureName": "Status",
  "timestamp": "2024-02-02T10:15:30.000Z",
  "measureValueType": "BOOLEAN",
  "value": "true"
}

Operational Notes

  • Transport: MQTT over TLS (managed by Azure Device SDK).
  • Reliability: Exponential backoff retry policy for transient failures.
  • Performance: Messages are serialized once per payload entry.