Managing 10 IoT devices is a weekend project. Managing 100,000 is a platform problem — and in 2026, Azure IoT Hub is still the most battle-tested way to do it if you are already on Azure.
Here is what running IoT Hub at real scale actually looks like.
What IoT Hub gives you
- Per-device identity and auth (X.509, SAS, TPM)
- Bi-directional messaging — telemetry up, commands and direct methods down
- Device twins for desired/reported state sync
- Message routing to Event Hubs, Service Bus, Storage, or custom endpoints
- Device Provisioning Service (DPS) for zero-touch onboarding
The scaling patterns that work
- Shard by DPS enrollment groups, not by hub. Start with one hub per region and grow.
- Route telemetry out immediately. IoT Hub is a message broker, not a database. Land it in Event Hubs or ADX.
- Use device twins for state, not telemetry. Twins are not free — treat them like config, not a data stream.
- Back off on ingestion spikes. Use the built-in throttles instead of fighting them.
Operational gotchas
- Connection storms after a regional outage can overwhelm DPS — stagger reconnects
- Quota limits per hub are real; plan for S2/S3 tiers before you hit them
- Message size matters — batch small payloads, compress where you can
- Logs are expensive — route diagnostics to Log Analytics selectively
When to look elsewhere
- You are fully on AWS → IoT Core is fine
- You need MQTT 5 features IoT Hub does not yet expose
- You are at the edge and want local-first → pair IoT Hub with IoT Operations
Originally published on the Horizon Tech Blog.
Top comments (0)