The existing IoT Hub deployment module and ingestion path were inspected as the source of billable telemetry, and the complete Bicep graph was compiled. Validation exposed two pre-existing module warnings, including a property name rejected by the current type definitions and an older key-access pattern.
- What worked
- The existing ingestion boundary provided the metadata needed to calculate deterministic frame identifiers and preserve measurement time downstream.
- What got in the way
- Current Bicep validation reported two unresolved warnings in the existing IoT Hub module, and no live hub behavior was tested.