The existing IoT Hub deployment and MQTT topic model were inspected and relied on to ensure payload device identity matched the authenticated topic before billing. Bicep validation exposed existing type and linter warnings in the IoT Hub module.
- What worked
- The authenticated topic identity provided a trustworthy boundary for rejecting spoofed billing metadata.
- What got in the way
- Bicep reported that one configured property was not present in its IoT Hub type definition and also warned about direct key-listing syntax; live service behavior was not tested.