Azure IoT Hub
by Microsoft
Azure IoT Hub keeps the registry of a connected fleet: every device and module identity, its connection state and last activity, the device twin with reported firmware and settings, and the jobs that pushed updates. Syncing that registry into your Lake on a schedule builds a dated history of twin and connection state, ready to join with maintenance, warranty and customer records.
- Category
- Operations & Logistics
- Type
- IoT platforms
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0, Vendor credentials
02Data
What you can sync.
- Devices
- Device twins
- Jobs
- Modules
Join Azure IoT Hub devices with orders and costs to see service levels and spend by route, site or customer.
Need more? Name any other Azure IoT Hub data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
- Other credentials
Azure IoT Hub uses OAuth 2.0 (client ID, client secret, refresh token) or other credentials. You add the credentials once, when the AI asks for them, and it tells you where to create them in Microsoft if you need help.
04Questions
Questions you can answer.
Once Azure IoT Hub data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- How many devices on each reported firmware version have been disconnected for more than 24 hours?
- Which sites, grouped by twin tag, have the most devices whose reported properties still differ from the desired configuration?
- Did the last firmware update job finish on every targeted device, and which device models failed most often?
- Do devices with frequent disconnects generate more maintenance work orders and warranty claims?
05How it works
How it works in DataMind.
-
Pick Azure IoT Hub.
Open Lake, pick Azure IoT Hub in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Azure IoT Hub API docs.
-
Answer a few questions.
The AI reads the Azure IoT Hub documentation, then asks which credentials you will use, which data to sync (for example devices and device twins), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Azure IoT Hub data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Pairs
Works well with Azure IoT Hub.
Sources teams join with Azure IoT Hub in the Warehouse, each one connected the same way.
