Receive Data from Azure IoT Hub with an SAS Key

review the following guide for setting up an inbound data integration between belden horizon data operations and azure iot hub using an sas key before you begin you must first docid\ pms3cnfw5k2cbsueer8pu step 1 add the azure iot hub using sas key connector follow the steps to docid\ orxib vla2ngvdx94z1ow and select the mqtt azure iot hub using sas key provider configure the following parameters name enter a name for the connector hostname the ip address or server fqdn of the mqtt broker (must be reachable from your edge device) port the mqtt broker's port number the default value is 8883 device id copy the device id of your edge device from the iot devices page in the azure portal and paste it here sas key copy the primary or secondary shared access key from the iot devices page in the azure portal and paste it here parallel publish count the maximum number of concurrently published messages the default value is 16 integration topic the default topic to publish or subscribe to devices/\[deviceid]/messages/events/ replace \[deviceid] with the device id copied from azure token ttl the token expiry time in minutes the default value is 1440 lwt topic the topic for mqtt's last will and testament feature lwt payload the payload for mqtt's last will and testament feature lwt payload type the payload type for mqtt's last will and testament feature the options are string and base64 lwt qos the quality of service value for mqtt's last will and testament feature lwt retained select this check box to retain the value for mqtt's last will and testament feature throttling limit the maximum number of messages per second to be processed the default value is zero, which means that there is no limit persistent storage when enabled, this will cause messages to undergo a store and forward procedure messages will be stored within belden horizon data operations when cloud providers are online step 2 enable the connector after adding the connector, click the toggle in the connector tile to enable it if you see a failed status, review the docid\ ocbqwycy xmmkwv9aunq and any relevant error messages step 3 create inbound topics for connector you will now need to create inbound topics for the connector that will receive the data from azure iot hub to create topics click the connector tile the connector dashboard appears click the topics tab add topics to the connector with the details below see the add a topic to a connector section in docid\ ocbqwycy xmmkwv9aunq for more information data direction select remote to local inbound local data topic paste the raw topic for the tag created in step 2 remote data topic replace devices/\[device id]/messages/events/ with devices/\[device id]/messages/devicebound/%24 to=%2fdevices%2fmessages%2fdevicebound replace \[device id] with the device id parameter configured for the connector enable click the toggle to enable the topic click yes to add the topic after adding all required topics, navigate to the integration pane and ensure the connector has a connected status step 4 initiate and view inbound messages you will need to create a flow to view the inbound messages from the connector to initiate and view inbound messages follow the steps to docid\ crmxroqtwtycjcddtoahd and add the following nodes datahub subscribe debug connect the two nodes double click the datahub subscribe node the edit datahub subscribe node dialog box appears paste the local topic you created in step 4 if needed, configure the datahub subscribe connection see the "step 3 configure connector nodes" section in docid\ crmxroqtwtycjcddtoahd to learn more click done , and then click deploy log in to azure open the device pane and click message to device the message to device pane appears enter test message in the message body field and click send message open the flow you created in belden horizon data operations and check the debug messages tab see the additional options section in docid uyecathnnfdy3 ggst1m for more details verify that test message appears in the debug results