Implementing the IoT devices for business solution might be easy but managing the millions of devices including their data and entire device life cycle including deployment, upgradation and securing the IoT devices is much difficult to overcomes these limitations Microsoft introduces the services azure IoT hub device provisioning service which formally known as azure DPS, Let's learn about the IoT hub device provisioning service.
Advantages of Azure IoT Hub Device Provisioning Service
- Helps to manage and connect thousands of IoT devices without worrying about setup configuration
- Device provisioning service helps of automatically balance the load of device across the multiple IoT Hubs
- Device provisioning service provides the feature to automatically connect the device to the IoT hub with nearest location of device
- Whenever required change in the configuration of existing connected device, Device provisioning service provides the feature how the device will be re-provision without or changing the existing configuration
- Easily secure the devices with X509 certificate and TPM which allow verify the identity of device when device need to be connected from deployed location
- Device provisioning service allows to connect individual or group of devices to the IoT hub with the help of devices enrolled using the feature group and individual enrollment
- Helps to manage the configuration of single as well as group of devices
Step 1: Go to Azure Portal
Step 2: Create IoT Hub Device Provisioning Service on Portal
- Name: Name of the IoT hub device provisioning service which must be contain only alphanumeric characters or hyphen
- Subscription: Choose the available azure subscription which you want to use for creating service from drop down list
- Resource Group: Choose existing resource group or create a new resource group which you may want to use.
- Location: Choose the deployment location for IoT hub device provisioning from given list, however the device provisioning service is global and associated with any specific location but you must specify a location for the resource group where the metadata associated with the service profile will reside.
- Resource Group: The name of the resource group in which IoT hub device provisioning resides.
- Service Endpoint: Unique URI to connect to the IoT hub device provisioning for device enrollment related operations
- Status: IoT hub device provisioning working status
- Global Device Endpoint: Global endpoint of IoT hub device provisioning service to perform the device provisioning related operation.
- ID Scope: Unique Id for identifying your specific IoT hub device provisioning service for device related operation since device operation related endpoint is global to all device provisioning services
- Subscription ID: Name of the subscription id in which your IoT hub device provisioning service resides
- Pricing & Scale Tier: Each IoT hub device provisioning service has pricing tier which can be decided to use based on the what scalability and performance required for an application. Currently IoT hub DPS support S1 tier which cost $ 0.10 that is INR 6.610 for 1000 operations
- Linked IoT Hub: This property allows to link upto ten IoT hub to the device provisioning service as well to see the list of linked IoT hubs. All the enrolled devices after provisioning registered into respective IoT hubs
- Certificates: This Section allows to add the device certificates which can be assigned to the devices during enrollment.
- Manage Enrollments: This section allows to enroll the various types of security feature devices such as TPM (Trusted Platform Module) and X.509. Device enrollment can be enrolled using the following two concepts
- Manage Allocation Policy: Device provisioning service allows to link the multiple IoT hub & using manage allocation policy we can set the IoT hub allocation policy for enrolled devices which automatically decides on which IoT hub device should belong when the device is connected or registered.
- Lowest latency: This policy automatically assigns device to the closest IoT hub ((Datacenter) of device location which will make faster communication between devices and IoT hub.
- Evenly weighted distribution: This is the default policy and recommended by Microsoft which will equally distributes devices to the linked IoT hubs, Let’s say we have ten IoT devices and two linked IoT hubs then five devices will be assigned to one IoT hub and five devices to another IoT hub
- Static configuration: This policy assigns the devices to the specific IoT which is selected during the device enrollment.