---
title: Receive Data from Azure IoT Hub with a Device Certificate
slug: bhdo/receive-data-from-azure-iot-hub-with-a-device-certificate
createdAt: 2022-11-24T18:16:55.000Z
---

Review the following guide for setting up an inbound data integration between Belden Horizon Data Operations and Azure IoT Hub using an SAS key.

# Additional Resources

Refer to the following resources for more information. 

- [Send device-to-cloud and cloud-to-device messages with IoT Hub](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messaging?WT.mc_id=Portal-Microsoft_Azure_IotHub#message-format)
- [Using the MQTT protocol directly (as a module)](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support#using-the-mqtt-protocol-directly-as-a-module)
- [Receiving cloud-to-device messages](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support#receiving-cloud-to-device-messages)

:::hint{type="info"}
**Note**: Integration does not support wildcard characters for inbound messages.
:::

# Before You Begin

You must first [Set up an Azure IoT Hub](docId\:GUm_YolvJoNqSWrxJDRUh). When you add the IoT device to the hub, select **X.509 Self-Signed** as the **Authentication type **when you add the IoT device in Azure. 

# Step 1: Retrieve Connector Parameters

You will need to log in to Azure to retrieve the parameters for configuring the connector in Belden Horizon Data Operations. 

::::hint{type="info"}
**Tip**: Use the following command to generate a public/private key pair:

:::BlockQuote
openssl req -newkey rsa:2048 -nodes -keyout myprivatekey.pem -x509 -days 365 -out mydevicekeycer.pem
:::
::::

**To retrieve the connector parameters:**

1. From the Microsoft Azure home page, click your IoT Hub.
2. From the Navigation panel under *Explorers*, click **IoT devices**.
3. From the *Azure IoT devices *pane, copy the device name from the **Device ID **column.
4. Click the **Device ID **for the device you want to connect.
5. Copy the **key ID **and paste it to the **Primary Thumbprint **field, and then copy the **certificate ID **and paste it to the **Secondary Thumbprint **field.

# Step 2: Add the Azure IoT Hub Using Device Certificates Connector

Follow the steps to [Add a Connector](docId\:tkKE__fVsjbk_6yAmnFNW) and select the **MQTT - Azure IoT Hub using Device Certificates** provider. 

- **Name**: Enter a name for the connector. 
- **Hostname**: IP Address or Server FQDN of MQTT broker. 
- **Port**: Verify the default value of 8883 is entered. 
- **Device ID**: Copy the **Device ID** retrieved in Step 1.
- **Certificate**: Paste the certificate from the **mydevicekeycer.pem** file generated in Step 1. 
- **Private key**: Paste the key certificate from the **myprivatekey.pem **file generated in Step 1. 
- **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. 
- **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 3: Enable the Connector

After adding the connector, click the toggle in the connector tile to enable it. 

::Image[]{src="https://api.archbee.com/api/optimize/vAqK-046vdh4I0e1y9cfX/YtSjhZ-y4uZaqVnC5V5VW_azureiotdevice.png" size="60" width="370" height="345" position="center" showCaption="false"}

If you see a *Failed *status, review the [Connector Logs](docId\:q8Q3J9CWP9n67ro4lmdZV) and any relevant error messages. 

# Step 4: Create Inbound Topics for Connector

You will now need to create inbound topics that will receive the data from Azure IoT Hub. 

**To create topics:**

1. Click the connector tile.
   The connector *Dashboard *appears. 
2. Click the **Topics **tab. 
3. Add topics to the connector with the details below. See the *Add a Topic to a Connector* section in [Manage Connectors](docId\:q8Q3J9CWP9n67ro4lmdZV) for more information. 
   - **Data Direction**: Select **Remote to Local - Inbound**. 
   - **Local Data Topic**: Enter **integration.raw\.inboundtest**. 
   - **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 value configured for the connector. 
   - **Enable**: Click the toggle to enable the topic. 
4. Click **Yes **to add the topic. 
5. After adding all required topics, navigate to the *Integration *pane and make sure the connector shows a *Connected *status. 

# Step 5: 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:**

1. Follow the steps to [Create a Flow](docId\:txzrrzE-F1bVhJ4vPDAIW) and add the following nodes.
   - **DataHub Subscribe**: 
   - **Debug**
2. Double-click the **DataHub Subscribe **node.
   The *Edit DataHub Subscribe node* dialog box appears.
3. Enter **Azure inbound **in the **Name **field.
4. Paste the Topic you created in Step 4 in the **Topic **field. 
5. If needed, configure the *Datahub Subscribe* connection. See the "Step 3: Configure Connector Nodes" section in [Create a Flow](docId\:txzrrzE-F1bVhJ4vPDAIW) to learn more. 
6. Click **Done**, and then click **Deploy**.
7. Click the **debug **tab.
8. Log in to Azure. 
9. Open the device pane and click **Message to Device**.
   The *Message to device* pane appears. 
10. Enter **Test Message **in the **Message Body **field and click **Send Message**.
11. Open the flow you created in Belden Horizon Data Operations and check the *Debug messages* tab. See the *Additional Options* section in [Manage the Flow Canvas](docId\:RN8FJGqWnxIaGmsJn0MNv) for more details. 
12. Verify that *Test Message* appears in the debug results.