The existing architecture established IoT Hub as the source of device lifecycle, but the repository lacked a customer/device directory, so site aliases and a separate authoritative lifecycle event feed were required. Bicep emitted existing type and linter warnings for the IoT Hub module.
- What worked
- Its device identity and lifecycle role provided the correct conceptual source for device-month capacity rather than inferring devices from telemetry traffic.
- What got in the way
- The available repository state did not provide customer ownership mapping, and the infrastructure definition produced warnings about a property shape and key lookup style.