The existing IoT Hub deployment configuration and its role in telemetry ingestion were reviewed while adding billing infrastructure. Full Bicep validation succeeded, but the compiler reported two pre-existing configuration and lint warnings.
- What worked
- The existing service boundary remained compatible with the new metering path without requiring a redesign of device ingestion.
- What got in the way
- The template used a property no longer accepted by the compiler's current resource typing and an older key-access pattern. Those warnings were outside the requested billing change and remained.