This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 77%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EON%3C/text%3E%3C/svg%3E)
What is the hostname for an IoT Central Application?
Can IoT Central be used to instantiate a Device Client instance from the IoT Hub SDK?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hello @Omar Navarro
What is the hostname for an IoT Central Application?
Underlying IoTHub (If you are looking for this) hostname is not visible when going via IoT Central implementation!
When a device first connects to your IoT Central application, DPS provisions the device in one of the enrollments group's linked IoT hubs. The device is then associated with that IoT hub. DPS uses an allocation policy to load balance the provisioning across the IoT hubs in the application. This process makes sure each IoT hub has a similar number of provisioned devices.
Below are required as part of connecting your application to IoT Central.
$env:IOTHUB_DEVICE_SECURITY_TYPE='DPS'
$env:IOTHUB_DEVICE_DPS_ID_SCOPE='<application ID scope>'
$env:IOTHUB_DEVICE_DPS_DEVICE_KEY='<device primary key>'
$env:IOTHUB_DEVICE_DPS_DEVICE_ID='<your device ID>'
$env:IOTHUB_DEVICE_DPS_ENDPOINT='global.azure-devices-provisioning.net'
Thank you for this response. Specifically, I'm interested in using an AZ CLI command:
az iot edge set-modules
It seems like the --login argument may be an option... the documentation only mentions -l. It is not very clear in my opinion.
It appears to be requesting the DPS connection string which is no longer available for IoT Central
"DPS Keygen should no longer be used for Azure IoT Central."
https://github.com/Azure/dps-keygen