Device Identities are exported to a secondary region
Impact:HighCategory:Disaster Recovery
APRL GUID:783c6c18-760b-4867-9ced-3010a0bc5aa3
Description:
Device Identities should be copied to the failover region IoT Hub for all IoT devices to ensure connectivity in case of a failover. Manual Failover to another region is quicker (RTO), suitable for mission critical workloads.
In regions supporting Availability Zones for IoT Hub, using these zones boosts availability. They're automatically activated for new IoT Hubs in supported areas.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Use Device Provisioning Service
Impact:HighCategory:Scalability
APRL GUID:b1e1378d-4572-4414-bebd-b8872a6d4d1c
Description:
Device Provisioning Service (DPS) enables easy redistribution of IoT devices for scaling and availability, allowing devices to be reassigned and not bound to specific IoT Hub instances. Devices in IoT Hubs using DPS should be verified for DPS utilization.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Disabled Fallback Route
Impact:LowCategory:Monitoring and Alerting
APRL GUID:e7dbd21f-b27a-4b8c-a901-cedb1e6d8e1e
Description:
Using message routing for custom endpoints in IoT Hub, messages might not reach these destinations if specific conditions are unmet. A default route ensures all messages are received, but disabling this safety net risks leaving some messages undelivered.