Azure IoT Hub
Does ZopNight manage Azure IoT Hub?
IoT Hub bills per unit per day at a rate fixed by its tier, so a hub provisioned for a 10,000-device fleet that never shipped keeps billing every day it exists. ZopNight inventories each hub's tier and unit count via Resource Graph and holds 60 days of device traffic against it.
Rules that fire on Azure IoT Hub
No active rule family targets Azure IoT Hub today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost visibility only. |
IoT Hub connects and manages IoT devices at scale, billed per unit per day by tier. Hubs provisioned at high tiers for fleets that never materialized keep billing daily.
Daily unit charges tied to device tiers
An IoT Hub bills per unit per day at the rate its tier sets, and the meter is calendar-driven: the charge lands every day the hub exists, regardless of how many devices connect or how many messages arrive. Tier and unit count are chosen for the fleet you expect to have, which is exactly why hubs sized for projected device counts turn into standing charges the moment a rollout stalls.
Device-traffic evidence behind rightsizing
Discovered via Azure Resource Graph with tier and unit counts. Azure Monitor metrics across a 60-day window show device traffic, Cost Management billing attributes spend, and tier rightsizing surfaces in review. IoT Hub is not schedulable, because devices in the field reconnect and retry on their own timetable, and a hub switched off overnight sheds the telemetry it exists to collect. The cost lever is the tier-and-unit decision, informed by what the fleet actually sends.
Fleets that never arrived, hubs that stayed
Waste takes recognizable shapes on this type. The pilot hub provisioned at a paid tier for a deployment that topped out at a dozen test devices. Extra units added ahead of a scaling milestone that slipped by two quarters. And per-environment hubs (dev, test, certification) each carrying paid tiers when only production ever talks to real hardware. In every case the daily meter runs quietly because nobody puts unit count and device traffic on the same page.
Finding IoT Hub tier and units in the portal
Azure portal → IoT Hub lists every hub in the subscription. A hub’s Pricing and scale blade shows tier and unit count side by side, and the Overview’s device and message charts supply the traffic half of the comparison.