Sandervandevelde.wordpress.com Website Review

Once you are able to provision your IoT devices to the Azure IoT Platform using a DPS, a whole new world of possibilities opens up for Before, you registered your device to one IoTHub. To change it, you had to go to the device and fix it. But now you are able to make a choice between multiple IoT Hubs within the cloud, dynamically! Microsoft provides three standard strategies out of the box: This fourth strategy makes use of a custom Azure Function which you can write yourself. You could, for instance, access a database and read some data before you make the decision to which IoTHub you as*ign this device. Let’s see how we can build a custom function ourselves and get the most out of it. Continue reading “Custom IoT Hub as*ignment in Device Provisioning Service” → IoT Devices need a secure connection, the reason is obvious. It all starts with a secure connection between a device in the field and the Microsoft provides a secure connection for devices to the IoT Hub in three ways: We are interested in how to get our connection secured using the TPM. generate private keys and expose the public keys related to them. So it somewhat behaves like a set of certificates but now as a physical If somebody tries to physically compromise the chip to retrieve a private key, it should break thus destroying the chip and its content. for a Raspberry PI) but it’s better to have it already attached to your PC’s motherboard. The chip acts as an identity and you do not My Advantech UNO 2372G has a TPM 2.0 chip already built in. The same goes for a few laptops I have. Keep in mind that older versions of this security chip (like the TPM 1.2) are not supported by Microsoft. Symmetric keys and certificates are supported by the Azure IoT Hub. We need another service, the Azure Device Provisioning Service to provision a device using the TPM and get access to an IoT Hub of your choice. The Device Provisioning Service acts as a broker between provisioned devices and one or more IoTHubs.