NOW AVAILABLE

Azure IoT Hub Device Provisioning Service - June 2019 update

Updated: 02 August, 2019

Azure IoT Hub Device Provisioning Service - June 2019 update

The Azure IoT Hub Device Provisioning Service June 2019 release is available. The focus is on a broader enhancement of the provisioning experience and reducing limitations.

  • Support transferring additional data between device and DPS

This feature allows the device and DPS to send additional data to each other. Sometimes, DPS needs more data from devices to properly provision them to the correct IoT Hub, and that data needs to be provided by the device. Vice versa, DPS can return data to the device to facilitate client-side logics.

Use this feature as an enhancement for custom allocation. For instance, when you want to allocate your devices based on the device model without human intervention. Configure the device to report the model information as part of the register call. DPS will pass the device’s information to the custom allocation webhook, and your function can decide which IoT Hub this device will go to when it receives device model information. Similarly, if the webhook wishes to return some data to the device, it will pass the data back as a string in the webhook response.

This feature is also available in C, C#, JAVA and Node.js client SDKs.

 

  • Symmetric key support for IoT Edge

We now support symmetric key attestation for IoT Edge devices in both individual enrolment and group enrolment. With this change, if you think the “is IoT Edge device” option is true in symmetric key attestation, all devices registered under that enrolment group will be marked as IoT Edge devices.

 

This new attestation mechanism for IoT Edge device is recommended for use in developer scenarios when you want to quickly get going before choosing a more secure element.

  • Relaxing registration ID

We’ve removed several restrictions on registration ID and supported capital letters, so Registration ID is now case-insensitive. It can be alphanumeric, lowercase, uppercase, and may contain special characters including colon, full stop, underscore and hyphen.

As always, we want to offer our continued thanks to our customers for your feedback and suggestions. Microsoft engineers and Azure IoT community experts will respond to product-related questions on our MSDN forum and development questions on Stack Overflow. We also welcome product feedback and new feature requests.

 

  • Features
  • Services