Azure: Provisioning Hardware

Gateway Provisioning

Provisioning of Gateways is slightly easier with Azure - although the Gateway’s hardware ID must still be uploaded to our IoT Console, provisioning on the LNS is handled automatically.

As part of the process of integrating new Gateway models, myDevices is requiring our Manufacturing partners to configure for automatic provisioning as per our guidelines. This means that new Azure Gateways will complete provisioning once communicating with us for the first time - our new device provisioning service will automatically configure records necessary for the gateway communication to work.

Once a gateway has communicated and is provisioned successfully, it can be found in the LNS records.

Device Provisioning

Provisioning new device hardware will continue to be done prior to delivering to the customer. The process of doing so is very similar to what was done previously, only now of course using our LNS server instead of TTN.

Here is an overview of how devices are provisioned:

1. Make sure the Hardware model is fully defined (i.e. a device profile exists along with a codec) in the LNS.

   E.g. if you are adding yet another Dragino device and the functionality is basically the same as the current Dragino profile, you’re good. If it’s a completely new type of model, create a codec and define a new device profile in LNS.

2. Add the Device IDs in the Console. If this new device has never been registered on the network, make sure to register the device to the LNS from the Console.

You can then scan the QR codes and add the devices into an account as normal. Once a device is registered via the console, it can be found in the LNS.

Production vs Staging

Device provisioning for Azure no longer requires adding devices specifically into the Staging environment. As part of the LNS configuration already in place, data is mirrored into all the appropriate environments automatically.