Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

How to provision IoT devices at scale with IoT Hub Device Provisioning Service

Play How to provision IoT devices at scale with IoT Hub Device Provisioning Service

The Discussion

  • User profile image

    je vais a coeur ou met a install
    ou viedo.
    merci walter.p

  • User profile image

    this is awesome.. much appreciate building it Olivier

  • User profile image

    could we also do a video about flashing a x.509 cert on rpi using win10 iot core?

  • User profile image

    Hey Olivier,

    Suppose i have a new device[MXCHIP] , I power on this device, I have IOT HUb setup, Provisioning service setup etc. When we say Azure IOT provisioning is Zero-touch provisioning service, so how my device is going to communicate with the service initially  saying My Id is ABC123 where i needs to go ?  This is little confusing. 

  • User profile image

    Hey @Aaadil

    You always have something that needs to be flashed on the device (firmware, bootstrap) that will have the code to connect to the DPS service. But this code will be the exact same on all devices coming out of the production line. When we say zero-touch provisioning in the device management space, that means that you don't need to have manual intervention on every single device to provision them with unique credentials and code.

    You will ask "but how will DPS identify and differentiate devices from one another if they all have the same code running on them?". Well, this is where HSMs solutions like TPM are used. HSMs usually have unique secret seeds flashed in factory by chip makers which  are used by our bootstrap code to authenticate when connecting to DPS. in the case of the MXChip devkit, there is an ST-Safe chip in there. Check out this sample that shows how to provision an MXChip devkit with DPS:

Add Your 2 Cents