Register device in IOT HUB using ADR integration

Question

Hi,

I have created an IOTHUB with ADR integration preview feature. But when I am trying to register a device using device provision service (DPS) using symmetric key enrollment group, the device has been registered on IOTHUB successfully but not visible on ADR.

Can some one help in proving trouble shooting steps how can device will be registred on ADR as well.

Answer 1

Hi Dev Sharma,

When you use IoT Hub with Azure Device Registry integration in preview, it helps to know that device registration happens in two steps, and they are not always visible at the same time.

When you register a device through Device Provisioning Service using a symmetric key enrollment group, the device identity is created in IoT Hub first. That part working correctly means DPS and IoT Hub are configured properly. Azure Device Registry is updated by IoT Hub after provisioning, and this update can take some time or may depend on how the integration was set up.

Here are a few things to check that usually explain why the device is visible in IoT Hub but not yet in Azure Device Registry.

First, confirm that the IoT Hub is actually linked to an Azure Device Registry namespace. In the IoT Hub settings, there should be an Azure Device Registry section showing the linked namespace. If the hub is not linked, devices will never appear in ADR even though they register successfully in IoT Hub.

Second, make sure all three resources are in supported regions and correctly connected. IoT Hub, Device Provisioning Service, and Azure Device Registry must all be created in regions that support ADR integration. If DPS is in a different region or not associated during setup, devices can provision to IoT Hub but not sync to ADR.

Third, keep in mind that ADR sync is not instant. Azure Device Registry represents devices as Azure Resource Manager resources, and those entries are created asynchronously. After a device provisions, it may take a short while before it appears in the ADR namespace, especially in preview scenarios.

Fourth, check permissions. The IoT Hub service needs the right permissions to create device resources in Azure Device Registry. If role assignments were added recently, give them some time to fully take effect before testing again.

Also note that symmetric key enrollment through DPS is supported for IoT Hub registration, but ADR is primarily focused on unified device representation and management. In preview, some provisioning paths may not immediately surface devices in ADR, even though IoT Hub registration succeeds.

You can read more about how Azure Device Registry works with IoT Hub and how devices are represented as Azure resources

https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-device-registry-overview

This article also explains how to deploy IoT Hub with Azure Device Registry integration and what dependencies need to be in place.

https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-device-registry-setup

In short, if the device is registering in IoT Hub, your DPS flow is working. Focus on confirming the IoT Hub to ADR linkage, region support, permissions, and allow some time for the registry sync to complete.

Thankyou!