IoT Hub
IoT device telemetry ingestion
Overview
We set up IoT Hub for device telemetry: device identities, the protocol the devices already speak, and routes into Event Hubs, storage, or a processing job. Device twins and tags are used where you need desired and reported properties, not for data that belongs in the stream.
We agree enrolment, whether manual or through Device Provisioning Service, and a process for retiring a device. Telemetry routes are tested with a sample device before field hardware is pointed at the hub.
What we deliver
- IoT Hub with device identity and the required protocol endpoints
- Message routes to storage, Event Hubs, or a downstream job
- Enrolment and retirement process for devices
- A tested sample device and alerts on dropped messages
Business benefits
- Devices authenticate as themselves instead of sharing one connection string
- Telemetry is routed to the lake or a processor without a custom gateway on day one
- A lost or retired device can be disabled without rebuilding the hub
Typical use
IoT device telemetry ingestion
Related services
Contact
Let's talk about your Azure project
We're a real team, not bots. Send a few details and we'll reply within one working day.
