# Azure IoT Hub

The **Azure IoT Hub connector** can be used to forward data to Azure IoT Hub. It can be applied to process e.g. LoRaWAN device data with Azure IoT Hub and use it further in the [Azure ecosystem](https://azure.microsoft.com/en-us/services/). The Azure IoT Hub connector is available on both **Data Flow** and **Rule Engine**.

Azure IoT Hub has an identity registry that stores information about the devices and modules permitted to connect to the IoT Hub. Every akenza device, using the connector, will therefore be present in the identity registry of the IoT Hub. For identifying a device in the registry the device ID is used. If a device sends data and does not yet exist in the registry of IoT Hub, it will be automatically created.

For creating an Azure IoT Hub connector, the IoT Hub **connection string** needs to be entered, with Registry Read, Registry Write, Service Connect, and Device Connect permissions. Refer to [shared access policies](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-security).

A tutorial about "How to send data to Azure IoT Hub" can be found [here](/akenza.io/tutorials/create-enterprise-solutions/how-to-send-data-to-the-azure-iot-hub.md). 

{% hint style="info" %}
The whole data sample will be forwarded to Azure IoT Hub.
{% endhint %}

![Azure IoT Hub template](/files/bsUkSKzqsUQjrDCLGekM)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.akenza.io/akenza.io/get-started/your-data-flow/connectors/streaming/azure-iot-hub.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.