--- title: "Azure HTTP Event" slug: "azure-iot-hub" updated: 2025-06-13T08:23:12Z published: 2025-06-13T08:23:12Z canonical: "docs.connect.netmoregroup.com/azure-iot-hub" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.connect.netmoregroup.com/llms.txt > Use this file to discover all available pages before exploring further. # Azure HTTP Event ## **Configuration** This integration can be configured on the Export Configs tab on each Service Provider in the LoRaWAN Portal. First, you need to create a Device Policy in Azure, which outputs a connection string like this: HostName=IoTHubLoRa.azure-devices.net;SharedAccessKeyName=device;SharedAccessKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Then, when creating the Export Config, fill in the parameter with the output string that you got ![](https://cdn.document360.io/58c1b868-b36b-492e-aea3-32180613f31f/Images/Documentation/image(60).png) ### URL - **What it is:** The hostname of your Azure IoT Hub instance. - **Use case:** This is where the system will push messages. It should match the hostname of your IoT Hub. - **Example:** `IoTHubLoRa.azure-devices.net` (Equivalent to the *hostname* portion of your Azure IoT Hub resource.) ### **Topic** - **What it is:** The IoT Hub message route or logical target for messages. - **Use case:** Used to direct messages within Azure IoT Hub routing infrastructure (e.g., for telemetry, events, commands). - **Example:** `myTopic` — This may correspond to a custom topic filter used for routing messages in IoT Hub. ### **Shared Access Name** - **What it is:** The name of the shared access policy that grants permissions to publish messages to the IoT Hub. - **Use case:** Must correspond to a policy defined in the Azure IoT Hub with permission to send device-to-cloud messages (`ServiceConnect` or `DeviceSend`). - **Example:** `device` — Often a policy created for a specific device or logical app. ### **Shared Access Key** - **What it is:** The primary or secondary key associated with the Shared Access Name. - **Use case:** Used to authenticate requests. It's sensitive and should be treated like a password. - **Example:** `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx` — The actual key will be a long Base64 string from Azure.