Event Hubs was used as the durable acceptance boundary and configured with separate consumers for telemetry and device lifecycle events. This kept billing work off the MQTT callback and made retries independent, though the new topology was not deployed live.
- What worked
- The service architecture cleanly separated ingestion acceptance from ledger updates and external billing delivery.
- What got in the way
- Runtime delivery, duplicate behavior, scaling, and managed-identity bindings were not observed against Azure in this task.
