How To Create Azure IoT Hub

In this article, we will be creating an azure IoT hub using the azure portal so we can avoid confusion for beginners however Azure IoT Hub can be created using:
  • Azure CLI
  • SDK
  • API
  • ARM
Prerequisites
 
To create any Azure service, we need an active Azure subscription, whether it’s a paid or trial subscription. I am assuming you have an active Azure subscription

What is Azure IoT Hub?

Azure IoT is the IoT gateway for IoT devices which allows bi-directional communication between IoT devices to cloud and cloud to IoT device

Step 1: Go to the Azure Portal

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


After a successful login, the page will be redirected to the Azure portal, by default, the dashboard page is set as:


Step 2: Create Azure IoT

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



Click on the left side option to create a resource & type IoT hub into the populated search box, it will pop up the following screen as:



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




Provide required details as shown in the preceding image:
  • Subscription: Choose the available azure subscription which you want to use for creating service from drop-down list
  • Resource Group: Choose an existing resource group or create a new resource group that you may want to use.
  • Region: Choose the deployment location for IoT hub device provisioning from the 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.
  • IoT Hub Name: Name of the IoT hub service which must contain only alphanumeric characters or a hyphen.
After providing all the basic required details, click to review and create the IoT hub, which skips the remaining steps, or click to choose the next step, networking. It shows the following screen to configure networking:



In the above image, we choose the connectivity method for the IoT hub which decides which network the devices can connect to the IoT hub, there are three methods:
  • Public Endpoint all Network
  • Public Endpoint selected IP addresses
  • Private Endpoint 

Public Endpoint all Network

This option allows us to connect devices to the IoT hub on all public networks for whoever has access to public URI and the required credentials.

Public Endpoint selected IP addresses

Even you have a public endpoint (URI) but want to restrict devices, you should connect from a specific IP address. Then you can define the range of IP addresses. The IoT hub allows you to connect only to devices that fall within the defined IP address range. This option gives the useful feature to allow only known networks to connect to the devices

Private Endpoint 

This is the URI or endpoint which allows us to connect devices over the private network, which gives the robust security between devices and IoT hub communication
Once you choose your intended connectivity method, click on the next step which shows the step to configure the scalability of the IoT hub as:


The preceding management step allows us to define the scalability and security of the IoT hub with the help of the following options:
  • Pricing and Scale Tier
  • IoT Hub Units
  • Defender
Pricing and Scale Tier
 
There are different types of pricing and scale tiers that decide how many messages the device sends to the IoT hub per day and what feature does it supports. The features and message frequency of IoT hub can differ based on the pricing and scale tier. The pricing tiers are categorized as:

Free Tier
 
The F1 is the free tier by using you can use the free tier of IoT hub for your learning and check how IoT hub works. it allows 8000 messages per day with limited feature

Basic Tier

The basic tier is sub-categorized into the three types as
  • B1
  • B2
  • B3
Basic tiers are suitable for development activities but you can not get all the features in this pricing and scale tier.

Standard Tier

The standard pricing and scale tier provides the most advanced features and scales for the incoming IoT messages, The standard tier subcategorized into the three types as:
  • S1
  • S2
  • S3 
These tiers are most suitable for a production environment where hyper scalability and advanced security are required. Once you choose the configuration for the IoT hub, click on the next step tags, which shows the following screen:



The tagging helps to identify or categorize the services across the line of applications, after providing tags details, click on the next step review and create, it will show the following screen to review the details before creating the service:


After reviewing details, click on the create button, it will take some time to create the service. Once the service is created, the status can be notified on the notification icon as shown in the following image: 


Now click on the Go to resource button, you will be redirected to the newly created IoT hub service as shown in the following image:


Let’s learn about the preceding Azure IoT hub key sections in brief, listed below:
  • Overview
  • Certificates
  • Built-in Endpoints
  • Query Explorer
  • IoT Devices
  • Automatic Device Management
  • Messaging
  • Security
  • Monitoring
Overview
 
The overview section of the IoT hub is like a dashboard where you can see an overview of the service details, including the charts for incoming messages, status, etc.

Certificates
 
This section allows to add and save the device certificates which can be assigned to the devices during creating or adding the devices to the IoT hub.

Built-in Endpoints
 
This section contains the details which allow us to use the IoT hub as an event hub. The event hub compatible connectionString gives almost the same functionality as an event hub without creating any instance of the event hub.

Query Explorer
 
This section allows us to query devices that reside in the IoT hub. This feature is useful to query any device from the millions of devices from the IoT hub.

IoT Devices
 
This section lets you add the different types of IoT devices and related configuration.

Automatic Device Management
 
This section allows us to upgrade the firmware of individual or bulk of IoT devices based on the properties of the device such as tags or deviceId.

Messaging
 
This feature allows to capture the IoT device messages and their related events also you can route the messages to any other service such as data store etc.

Security
 
This section allows to secure the IoT devices using the IoT defender feature and create the security-related alerts

Monitoring

This section allows to monitor the logs related to the IoT hub, you can set any filter or rule for monitoring and create the alerts

Summary

I hope this article is useful for creating the Azure IoT hub service using the portal. In this series of Azure IoT, next, we will learn about creating Azure IoT hub using PowerShell.

Articles you may interested 

How To Create Azure Device Provisioning Service

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.

Create Azure IoT Hub Using Azure Portal

In this article, we will be creating an azure IoT hub using the azure portal so we can avoid confusion for beginners however Azure IoT Hub can be created using:
  • Azure CLI
  • SDK
  • API
  • ARM
Prerequisites
 
To create any Azure service, we need an active Azure subscription, whether it’s a paid or trial subscription. I am assuming you have an active Azure subscription

What is Azure IoT Hub?

Azure IoT is the IoT gateway for IoT devices which allows bi-directional communication between IoT devices to cloud and cloud to IoT device

Step 1: Go to the Azure Portal

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


After a successful login, the page will be redirected to the Azure portal, by default, the dashboard page is set as:


Step 2: Create Azure IoT

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



Click on the left side option to create a resource & type IoT hub into the populated search box, it will pop up the following screen as:



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




Provide required details as shown in the preceding image:
  • Subscription: Choose the available azure subscription which you want to use for creating service from drop-down list
  • Resource Group: Choose an existing resource group or create a new resource group that you may want to use.
  • Region: Choose the deployment location for IoT hub device provisioning from the 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.
  • IoT Hub Name: Name of the IoT hub service which must contain only alphanumeric characters or a hyphen.
After providing all the basic required details, click to review and create the IoT hub, which skips the remaining steps, or click to choose the next step, networking. It shows the following screen to configure networking:



In the above image, we choose the connectivity method for the IoT hub which decides which network the devices can connect to the IoT hub, there are three methods:
  • Public Endpoint all Network
  • Public Endpoint selected IP addresses
  • Private Endpoint 

Public Endpoint all Network

This option allows us to connect devices to the IoT hub on all public networks for whoever has access to public URI and the required credentials.

Public Endpoint selected IP addresses

Even you have a public endpoint (URI) but want to restrict devices, you should connect from a specific IP address. Then you can define the range of IP addresses. The IoT hub allows you to connect only to devices that fall within the defined IP address range. This option gives the useful feature to allow only known networks to connect to the devices

Private Endpoint 

This is the URI or endpoint which allows us to connect devices over the private network, which gives the robust security between devices and IoT hub communication
Once you choose your intended connectivity method, click on the next step which shows the step to configure the scalability of the IoT hub as:


The preceding management step allows us to define the scalability and security of the IoT hub with the help of the following options:
  • Pricing and Scale Tier
  • IoT Hub Units
  • Defender
Pricing and Scale Tier
 
There are different types of pricing and scale tiers that decide how many messages the device sends to the IoT hub per day and what feature does it supports. The features and message frequency of IoT hub can differ based on the pricing and scale tier. The pricing tiers are categorized as:

Free Tier
 
The F1 is the free tier by using you can use the free tier of IoT hub for your learning and check how IoT hub works. it allows 8000 messages per day with limited feature

Basic Tier

The basic tier is sub-categorized into the three types as
  • B1
  • B2
  • B3
Basic tiers are suitable for development activities but you can not get all the features in this pricing and scale tier.

Standard Tier

The standard pricing and scale tier provides the most advanced features and scales for the incoming IoT messages, The standard tier subcategorized into the three types as:
  • S1
  • S2
  • S3 
These tiers are most suitable for a production environment where hyper scalability and advanced security are required. Once you choose the configuration for the IoT hub, click on the next step tags, which shows the following screen:



The tagging helps to identify or categorize the services across the line of applications, after providing tags details, click on the next step review and create, it will show the following screen to review the details before creating the service:


After reviewing details, click on the create button, it will take some time to create the service. Once the service is created, the status can be notified on the notification icon as shown in the following image: 


Now click on the Go to resource button, you will be redirected to the newly created IoT hub service as shown in the following image:


Let’s learn about the preceding Azure IoT hub key sections in brief, listed below:
  • Overview
  • Certificates
  • Built-in Endpoints
  • Query Explorer
  • IoT Devices
  • Automatic Device Management
  • Messaging
  • Security
  • Monitoring
Overview
 
The overview section of the IoT hub is like a dashboard where you can see an overview of the service details, including the charts for incoming messages, status, etc.

Certificates
 
This section allows to add and save the device certificates which can be assigned to the devices during creating or adding the devices to the IoT hub.

Built-in Endpoints
 
This section contains the details which allow us to use the IoT hub as an event hub. The event hub compatible connectionString gives almost the same functionality as an event hub without creating any instance of the event hub.

Query Explorer
 
This section allows us to query devices that reside in the IoT hub. This feature is useful to query any device from the millions of devices from the IoT hub.

IoT Devices
 
This section lets you add the different types of IoT devices and related configuration.

Automatic Device Management
 
This section allows us to upgrade the firmware of individual or bulk of IoT devices based on the properties of the device such as tags or deviceId.

Messaging
 
This feature allows to capture the IoT device messages and their related events also you can route the messages to any other service such as data store etc.

Security
 
This section allows to secure the IoT devices using the IoT defender feature and create the security-related alerts

Monitoring

This section allows to monitor the logs related to the IoT hub, you can set any filter or rule for monitoring and create the alerts

Summary

I hope this article is useful for creating the Azure IoT hub service using the portal. In this series of Azure IoT, next, we will learn about creating Azure IoT hub using PowerShell.

Articles you may interested 

Getting Started with Azure IoT Hub


In my last article, we learned about the Azure device provisioning service, which allows us to manage IoT devices. If you have not read my previous article about Azure device provisioning service yet, then please read it using the following link:Now we have a platform to manage the IoT devices, but what about connecting the devices to some platform and getting the data from those connected devices? We must connect the device to some gateway platform to establish a secure connection between the cloud and the device to exchange the data. So, in this article we will learn about the Azure IoT hub and the role of IoT Hub in managing the IoT devices communication and telemetry data.

What is IoT?

IoT Stands for Internet of Things, which is a network of internet-connected hardware devices that give some insightful information about things such as a car, bike, truck, factory, etc.

What is the use of IoT?

You might have heard the word digital and smart multiple times such as digital services or smart cities etc. A real-world example is Indian prime minister Narendra Modi who always talks about digital India and smart cities.

So, what does digital mean? Simply the access of the services to an individual over the internet in the form of web applications, mobile applications, etc. which helps to minimize the presence of humans at particular facilities in order to get work done from the location where the person resides with the help of mobile apps or web applications.

A smart city is also a part of a digital service in which citizens can see the temperature and humidity of their cities and it automatically generates alerts to their citizens regarding sudden changes in the environment and specific precautions to take. Citizens can even track the live location of specific bus routes so he or she can plan accordingly. Streetlight management is another example of a smart city service in which streetlights are automatically managed by a digital service that is responsible for turning on or off lights based on surrounding visibility and generates alerts if any light bulb has a problem, so servicemen can fix it immediately.

Benefits of IoT

Consider just one of the scenarios which I have explained in the preceding paragraphs, let’s assume we have implemented smart streetlight management using IoT, the benefits are:

  • Monitor the network of streetlights at one place using the web application or mobile application.
  • Turn the lights on or off automatically based on the surrounding visibility such as sunrise and sunset which help to save a huge amount of electricity consumption.
  • Consider some lights are turned off due to some problem, then IoT generates an alert with details which helps servicemen to fix it immediately without going in person at sites.
By considering just the few examples above, you can imagine how IoT helps to give meaning to things that save time, cost, and effort. The IoT will play a very important role to shape the future of the world. In the coming years, we will see the IoT in everything, which will make human life much easier and faster.

How IoT works

To understand how IoT works, understand the following basic terminology of IoT:
  • Things
  • Device
  • Sensor
  • Network
  • IoT Gateway
  • Communication Protocol
Things
 
Any object around us that we use in our daily life such as a car, truck or any vehicle, water taps, pumps, machines, house, factory or room, AC, fan, etc.
 
Device
 
This is the hardware installed on the things to get the data
 
Sensor
 
The sensor is situated on the device to monitor the intended information such as temperature, speed, humidity, visibility, etc.

Examples

  • Temperature and humidity sensor
  • Pressure sensor
  • Visibility sensor
  • Magnetometer sensor
  • Accelerometer sensor
Network
 
This is the way of communication how device sensors and data collection platforms are connected to each other, such as Bluetooth, LAN, Wi-Fi, WAN, Internet, etc.
 
IoT Gateway
 
The IoT gateway is the platform or mediator between devices to cloud or cloud to device communication which is responsible for collecting the messages from IoT devices and sending messages back to the devices.
 
The IoT gateway provides the features to collect and process the IoT device's data and upgrade the IoT devices. The most common example of an IoT gateway is Microsoft Azure IoT.
 
Communication Protocol

The communication protocols are the medium that is responsible to establish the communication between IoT devices and IoT gateways to send and receive the messages between them.

Examples of the most common protocols are:
  • AMQP
  • MQTT
  • Https
  • TCP
  • UDP
  • DDS
  • XMPP
  • LwM2M
  • ZigBee
Azure IoT Hub Supported Protocols
  • AMQP
  • AMQP Over WebSockets
  • MQTT
  • MQTT Over WebSockets
  • HTTPS


Now we have seen what IoT is in brief and the advantages it gives. We can achieve these preceding scenarios with the help of Microsoft Azure IoT. Let’s see about Azure IoT.

What is Microsoft Azure IoT?

Azure IoT is the IoT gateway for IoT devices which allows bi-directional communication between IoT devices to cloud and cloud to IoT devices. Azure IoT can process the millions of IoT devices and route the messages to specific data storage platforms.

Key Advantages of Azure IoT

  • Built-in UI to manage and monitor the IoT devices
  • Allows us to capture entire device lifecycle events using the device life cycle change event feature
  • Allows us to upgrade the firmware of single or bulk of devices using the automatic device management feature
  • Allows the bi-directional communication between IoT devices to cloud and cloud to IoT devices
  • IoT hub allows us to connect the edge devices and IoT devices its means IoT hub capable to connect low powered and high processing devices
  • IoT devices can send telemetry data as well as can connect devices over a network using AMQP, MQTT, and HTTPS protocol to the Azure IoT hub
  • Azure IoT hub supports the wide range of IoT device authentication mechanisms such as X509, tpm, and symmetric key
  • Azure IoT hub allows routing the messages to the specific data store and data process platform using the message routing feature
  • Azure IoT hub allows uploading the file for a specific device which can be used for device upgradation for storing device process-related information
  • Azure IoT hub IoT Hub allows us to send commands to the device which can help to change the behavior of the device using the Cloud to Device message feature
  • Provides the device twin feature to store the metadata or any specific information about the IoT devices
  • Azure IoT hub is supposed to be a secure platform for communication and authentication for the devices with the help of communication protocol AMQP, MQTT and HTTPS and authentication mechanisms such as X509, TPM, and symmetric key
  • Provides the wide range of SDK which help to connect to the IoT hub and devices programmatically C#, java, python, C, Node.js, android SDK also IoT hub supports api
  • Provides the feature to enable or disable the connected IoT devices

Creating An Azure IoT Hub Using Azure Portal

Azure IoT Hub can be created using:
  • Azure CLI
  • SDK
  • API
  • ARM
  • Azure portal 
In this article, we will be creating an IoT hub using the portal so we can avoid confusion for beginners. Now let’s start creating the azure IoT hub step-by-step via the Azure portal.

Prerequisites
 
To create any Azure service, we need an active Azure subscription, whether it’s a paid or trial subscription. I am assuming you have an active Azure subscription

Step 1: Go to the Azure Portal

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


After a successful login, the page will be redirected to the Azure portal, by default, the dashboard page is set as:


Step 2: Create Azure IoT

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



Click on the left side option to create a resource & type IoT hub into the populated search box, it will pop up the following screen as:



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



Provide required details as shown in the preceding image:
  • Subscription: Choose the available azure subscription which you want to use for creating service from drop-down list
  • Resource Group: Choose an existing resource group or create a new resource group that you may want to use.
  • Region: Choose the deployment location for IoT hub device provisioning from the 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.
  • IoT Hub Name: Name of the IoT hub service which must contain only alphanumeric characters or a hyphen.
After providing all the basic required details, click to review and create the IoT hub, which skips the remaining steps, or click to choose the next step, networking. It shows the following screen to configure networking:



In the above image, we choose the connectivity method for the IoT hub which decides which network the devices can connect to the IoT hub, there are three methods:
  • Public Endpoint all Network
  • Public Endpoint selected IP addresses
  • Private Endpoint 

Public Endpoint all Network

This option allows us to connect devices to the IoT hub on all public networks for whoever has access to public URI and the required credentials.

Public Endpoint selected IP addresses

Even you have a public endpoint (URI) but want to restrict devices, you should connect from a specific IP address. Then you can define the range of IP addresses. The IoT hub allows you to connect only to devices that fall within the defined IP address range. This option gives the useful feature to allow only known networks to connect to the devices

Private Endpoint 

This is the URI or endpoint which allows us to connect devices over the private network, which gives the robust security between devices and IoT hub communication
Once you choose your intended connectivity method, click on the next step which shows the step to configure the scalability of the IoT hub as:


The preceding management step allows us to define the scalability and security of the IoT hub with the help of the following options:
  • Pricing and Scale Tier
  • IoT Hub Units
  • Defender
Pricing and Scale Tier
 
There are different types of pricing and scale tiers that decide how many messages the device sends to the IoT hub per day and what feature does it supports. The features and message frequency of IoT hub can differ based on the pricing and scale tier. The pricing tiers are categorized as:

Free Tier
 
The F1 is the free tier by using you can use the free tier of IoT hub for your learning and check how IoT hub works. it allows 8000 messages per day with limited feature

Basic Tier

The basic tier is sub-categorized into the three types as
  • B1
  • B2
  • B3
Basic tiers are suitable for development activities but you can not get all the features in this pricing and scale tier.

Standard Tier

The standard pricing and scale tier provides the most advanced features and scales for the incoming IoT messages, The standard tier subcategorized into the three types as:
  • S1
  • S2
  • S3 
These tiers are most suitable for a production environment where hyper scalability and advanced security are required. Once you choose the configuration for the IoT hub, click on the next step tags, which shows the following screen:



The tagging helps to identify or categorize the services across the line of applications, after providing tags details, click on the next step review and create, it will show the following screen to review the details before creating the service:


After reviewing details, click on the create button, it will take some time to create the service. Once the service is created, the status can be notified on the notification icon as shown in the following image: 


Now click on the Go to resource button, you will be redirected to the newly created IoT hub service as shown in the following image:


Let’s learn about the preceding Azure IoT hub key sections in brief, listed below:
  • Overview
  • Certificates
  • Built-in Endpoints
  • Query Explorer
  • IoT Devices
  • Automatic Device Management
  • Messaging
  • Security
  • Monitoring
Overview
 
The overview section of the IoT hub is like a dashboard where you can see an overview of the service details, including the charts for incoming messages, status, etc.

Certificates
 
This section allows to add and save the device certificates which can be assigned to the devices during creating or adding the devices to the IoT hub.

Built-in Endpoints
 
This section contains the details which allow us to use the IoT hub as an event hub. The event hub compatible connectionString gives almost the same functionality as an event hub without creating any instance of the event hub.

Query Explorer
 
This section allows us to query devices that reside in the IoT hub. This feature is useful to query any device from the millions of devices from the IoT hub.

IoT Devices
 
This section lets you add the different types of IoT devices and related configuration.

Automatic Device Management
 
This section allows us to upgrade the firmware of individual or bulk of IoT devices based on the properties of the device such as tags or deviceId.

Messaging
 
This feature allows to capture the IoT device messages and their related events also you can route the messages to any other service such as data store etc.

Security
 
This section allows to secure the IoT devices using the IoT defender feature and create the security-related alerts

Monitoring

This section allows to monitor the logs related to the IoT hub, you can set any filter or rule for monitoring and create the alerts

Summary

I hope this article was useful for understanding the basics of the Azure IoT hub service. In this series of Azure IoT, next, we will learn about the device enrollments using Azure IoT hub device provisioning service.

Articles you may interested 

How To Estimate Azure Services Cost

The cost is very important factor while building the application over the cloud. Microsoft provides the tool named azure pricing calculator to estimate the rough cost of services which are required for your application.

To estimate the price using the azure pricing calculator, first you need to analyze your application in terms of  which database, OS, hosting environment required and based on that need to identify the azure services which are fit for your application. Let's assume we analyzed the application and our identified services are as follows

  • App Service: Hosting the application
  • SQL Database: Storing the application data
  • Azure SignalR Service: Realtime updating the UI dashboard

Now visit the azure pricing calculator by clicking on the following button


Azure Pricing Calculator



Now add the services which you wants estimate, we are trying to estimate the app service cost, now after choosing the all the parameter the estimation look like as follows


Note: The preceding is the just example to show the functionality  and introduce the of the tool, The preceding is the not proper way to estimation

Features of Azure pricing calculator

  • Allows to estimate the cost of each service by choosing the custom parameters
  • Allows to Export, Save and share the estimation
  • Sample example scenarios to help to choose right estimation
  • Allows to see estimate value in any currency type 
Now visit the azure pricing calculator and see the capability of calculator by estimating your own application.

Summary

I hope this article is useful to know, how to estimate the azure services cost, if you have any suggestion then please share by using the following comment box.

What is Azure Resource and Resource Group

Azure resource and azure resource group are two most commonly used terms while working with Microsoft azure. Recently one of the readers asked me about the difference between these two terms, so I have decided to write a post on these two terms.

What is Resource?

The resource is nothing but an Azure service such as app service, Azure storage, azure active directory etc. It means whenever you create a new resource, you are actually creating the azure service.

What is Azure Resource Group?

The azure resource group is the collection of resources, the resource group is the container in which multiple azure services reside.

Every Azure service must be located in the resource group. The Resource group gives better flexibility to manage the life cycle of all services at one place, which are located in the resource group. You can deploy, update and delete these services together.

Key Points of Azure Resource Group

  • The resource group can be created using Azure portal, Azure CLI, Azure PowerShell and Azure ARM Template.
  • The every resource group has its own deployment location to store the metadata of the services which are contained in the resource group, no matter in which location your services are deployed.
  • All services located in the resource group have a similar life cycle, you can delete, update and deploy them together.
  • You can move services from one resource group to another resource group.
  • If the service has the same metadata, it won't be allowed in a different resource group. It means you cannot have two resource groups for one service which is identical.
  • The resource group and resources can be in different regions. It means that if your resource group location is the US region, then your service might have any other deployment location such as west Europe etc.
  • The Resource group provides better control to manage the security of a group of services such as user access and resource permission etc. so someone cannot harm the service.
  • Every resource in the resource group can connect to the other resource group services.
  • Each resource group can deploy 800 services at a time.
  • When you delete the resource group, then all the services which are in the resource are deleted.

Summary

I hope this article is useful to understand the difference between the Azure resource and resource group. If you have any doubts, then please ask using the comment box.

Related articles

www.CodeNirvana.in

Protected by Copyscape
Copyright © Compilemode