Create a new Azure IoT Hub resource, by clicking the + Create a resource button, and then entering IoT Hub
Assign a resource group by choosing an existing group or creating a new one and fill the IoT hub name and region fields; choose Public access in the networking tab to select a tier that fits your use case in the Management tab (use the free tier for testing)
Click review and create to provision the IoT hub resource
Add a shared access policy
Navigate to your IoT Hub resource and click Shared access policies in the Settings section.
Click + Add shared access policy, give it a nameand check all boxes for the permissions (registry read, registry write, service connect, and device connect permissions).
Adding a shared access policy
2. Obtain an Azure IoT Hub connection string
Once the policy is created, obtain the Primary Connection String, by clicking the policy and copying the connection string. The connection string will be used to create the connector in akenza.
Obtaining the connection string
3. Setup a Data Flow in akenza
In akenza, create a new Data Flow with Azure IoT Hub as Output Connector. Define a Connector Name and insert the Connection String obtained from the shared access policy.
Data Flow with Azure IoT Hub as Output Connector
Create a new device using the Data Flow and start sending data.
The whole data sample will be forwarded to Azure IoT Hub
If a device sends data and does not yet exist in the registry of IoT Hub, it will be automatically created
4. Monitor Events
In order to monitor uplinks that are sent to Azure IoT Hub, you can use Azure CLI with the Azure IoT CLI Extension. Use the following commands to install the extension and monitor incoming uplinks:
az extension add --name azure-iot
az iot hub monitor-events -n <azure-iot-hub-name> --login <azure-iot-hub-connection-string>
All devices which have sent data can be inspected in the IoT Device Explorer on IoT Hub.
IoT Device Explorer on IoT Hub
5. Use of further Azure services
Once a device is connected to the IoT Hub, device data can be further used on various Azure services: