We’ve deployed Azure IoT Central (aziotc) to manage a global fleet of industrial sensors across four regions: US-East, EU-West, Asia-Pacific, and South America. Each region has its own IoT Hub instance feeding into a centralized IoT Central application.
When we initiate firmware updates through IoT Central’s device management interface, the viz-dashboard shows progress only for devices in US-East (our primary region). Devices in the other three regions receive and successfully install the firmware - we can verify this through direct device queries - but the dashboard remains blank for those regions throughout the entire update cycle.
Our cross-region device groups are configured correctly in IoT Central, with devices properly tagged by geographic location. We’ve verified that dashboard data connectors have read permissions across all four IoT Hub endpoints. The IoT Hub endpoint configuration in IoT Central lists all four hubs with valid connection strings and active status.
Has anyone successfully configured multi-region firmware update visibility in IoT Central dashboards? What configuration aspect might cause selective regional reporting?
Good suggestions. I verified the device templates are identical across regions, and the firmware update telemetry schema matches. I also checked message routing in each IoT Hub - US-East has a route named ‘FirmwareUpdateProgress’ that points to IoT Central’s built-in endpoint. The other three regional hubs don’t have this specific route, which might be the issue. I’m going to add the same routing rules to the other hubs and see if that resolves the visibility gap.
This sounds like a data aggregation issue in IoT Central. When you have multiple IoT Hub instances feeding one IoT Central app, the device telemetry and state updates need to be properly mapped. Check your device templates - each regional device group might need its own template with region-specific properties. Also verify that the firmware update telemetry schema is identical across all regions.
Before you add those routes, make sure you understand how IoT Central’s device bridge works with multiple hubs. Each hub needs not just the route, but also the correct enrichment properties that tag messages with region metadata. Without those enrichments, IoT Central can’t properly attribute firmware progress to the right device groups in the dashboard. The enrichment should include at minimum: region, hubName, and deviceGroupId. These are used by the dashboard aggregation logic.