Introduction to separate registration of Azure DPS

Explanation of picture and text:

1. Automatic preallocation

DPS can pre-provision the device to the IoT center in real time (essentially the process of verifying the identity of the device and then registering the device with the IoT Hub according to the rules) without human intervention. After successful preconfiguration, the device is directly connected to the designated IoT center. This process is called automatic preconfiguration.

two。 Register

Registration is a record of the successful registration / pre-allocation of devices to the IoT center through the device provisioning service. Registration records are automatically created and can be deleted but not updated.

2.1 Registration Group

Is a group of devices that share a specific proof mechanism. The registration group supports X.509 and symmetry. All devices in the X.509 registration group provide X.509 certificates signed by the same root or intermediate certificate authority (CA). Each device in the symmetric key registration group provides an SAS token derived from the self-group symmetric key. The registration group name and certificate name must be lowercase alphanumeric and can contain hyphens.

It is recommended that you use registration groups for a large number of devices that share the required initial configuration, or for devices that are all transferred to the same tenant.

2.2 Registration separately

Separate registration is an entry for a single device that can be registered. Individual registration can use X.509 leaf certificates or SAS tokens (from physical or virtual TPM) as the certification mechanism. Registration ID in separate registration is lowercase alphanumeric and can contain hyphens. Separate registration may specify the required IoT central device ID.

It is recommended that you use personal registration for devices that require unique initial configuration or that can only be authenticated with TPM tokens using SAS tokens.