Creating Azure IoT Hub Device Provisioning Service Using Azure Portal

In this article, we will learn how to create an azure IoT Azure IoT hub device provisioning service using azure portal so we can avoid confusion for beginners however Azure IoT Hub DPS can be created using:
  • Azure CLI
  • SDK
  • API
  • ARM

Step 1: Go to Azure Portal

Navigate to the portal.azure.com using browser and login into portal with valid credentials, as shown in following image


After successful login page will be redirected to the azure portal default dashboard page as shown in the following image


Step 2: Create IoT Hub Device Provisioning Service on Portal

Find the create resource option which can be found left top side of the portal as shown into the following image or follow any other option which you may know to create the resource (service) in azure portal




Click on left side option to create a resource & type IoT hub device provisioning service into the populated search box, it will pop up the following screen which is shown in the following image


As shown in preceding image click on create button, it will show the following screen


Provide required details as shown in preceding image as
  • Name: Name of the IoT hub device provisioning service which must be contain only alphanumeric characters or hyphen
Example

Valid Name

Invalid Name
Compilemode-dps-001
compilemode@-01_

Compilemode-dps

Compilemode dps
  • 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.
  • LocationChoose 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.
After providing all required details, click on create button, it will take some time to create service, once service created status can be notified  on notification icon as shown in following image



Now click on Go to resource button it will redirected to the newly created IoT hub device provisioning service as shown in the following image


Let’s know about preceding IoT hub device provisioning service settings and overview section
  • 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
  •  Shared Access Policies: Shared access policies section reside the different keys & connection string to connect with IoT hub device provisioning service programmatically using SDK’s & REST services
  • 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 EnrollmentsThis 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
            Individual EnrollmentThis allows to enroll the one device at a time which allows unique                  configuration per device.
           Group EnrollmentGroup Enrollment allows to enroll the group of devices at a time which                  allows common configuration for group of devices.
  • Manage Allocation PolicyDevice 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.
Following are the allocation policies can be set
  • Lowest latencyThis 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 configurationThis policy assigns the devices to the specific IoT which is selected during the device enrollment. 
Summary

Hope this article helped you to understand how to create azure device provisioning service using portal, if you have any suggestion then please send using the comment box.

Post a Comment

www.CodeNirvana.in

Protected by Copyscape Online Copyright Protection
Copyright © Compilemode