Skip to main content
Technical Preview

Overview

A client-mode connector for a curated cloud-IoT slice of Azure IoT Hub covering registry, device-to-cloud events, device twin, and direct methods: Default BASE_ADDRESS is https://YOUR_HUB.azure-devices.net (no trailing slash). Topics use cloud-iot/azure-iot-hub/<object>/<verb>. Default api-version is 2021-04-12. See the base guide: REST API Connectors.
Auth: pass Authorization as {value.json.authorization} — either SharedAccessSignature sr=…&sig=…&se=…&skn=… or Bearer {entra_token} for service APIs. Prefer Hub secrets — never commit real keys into the .lot.
Device SendDeviceEvent requires a DeviceConnect SAS scoped to the device. Microsoft Entra ID is not supported for IoT Hub device APIs.
Event Grid device events are docs-only / future ENABLE_SERVER. This package is client-mode only. Prefer Hub secrets for SAS / Entra. This template has not been verified against a live IoT Hub. Status remains blocked until an authenticated live smoke succeeds.

Basic Syntax

MQTT examples

GetDevice smoke (cloud-iot/azure-iot-hub/devices/get):
SendDeviceEvent (cloud-iot/azure-iot-hub/messages/events/post) — device SAS; expect 204:
UpdateTwin (cloud-iot/azure-iot-hub/twins/update):
InvokeDeviceMethod (cloud-iot/azure-iot-hub/twins/methods/post):

Notes

  • Replace YOUR_HUB in BASE_ADDRESS before deploy.
  • api-version=2021-04-12 is required on every request (pass api_version in MQTT JSON).
  • Service twin PATCH updates desired properties and tags. Catalog wording said “reported”; reported properties are typically updated by the device.
  • Event Grid inbound webhooks are not packaged (future server connector).
  • Suggested branches: feat/rest-api-route-azure-iot-hub, feat/docs-rest-api-azure-iot-hub (Hugo pushes).
Last modified on October 21, 2026