You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot/iot-introduction.md
+31-18Lines changed: 31 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,19 +5,23 @@ author: dominicbetts
5
5
ms.service: iot
6
6
services: iot
7
7
ms.topic: overview
8
-
ms.date: 11/29/2022
8
+
ms.date: 03/24/2023
9
9
ms.author: dobett
10
10
ms.custom: [amqp, mqtt]
11
11
#Customer intent: As a newcomer to IoT, I want to understand what IoT is, what services are available, and examples of business cases so I can figure out where to start.
12
12
---
13
13
14
14
# What is Azure Internet of Things (IoT)?
15
15
16
-
The Azure Internet of Things (IoT) is a collection of Microsoft-managed cloud services that connect, monitor, and control billions of IoT assets. In simpler terms, an IoT solution is made up of one or more IoT devices that communicate with one or more back-end services hosted in the cloud.
16
+
The Azure Internet of Things (IoT) is a collection of Microsoft-managed cloud services that let you connect, monitor, and control billions of IoT assets. In simpler terms, an IoT solution is made up of IoT devices that communicate with cloud services.
17
+
18
+
The following diagram shows a high-level view of the components in a typical IoT solution. This article is focused key groups of components: devices, IoT cloud services, other cloud services, and solution-wide concerns. Other articles in this section provide more detail on each of these components.
An IoT device is typically made up of a circuit board with sensors attached that use WiFi to connect to the internet. For example:
24
+
An IoT device is typically made up of a circuit board with sensors attached that uses WiFi to connect to the internet. For example:
21
25
22
26
* A pressure sensor on a remote oil pump.
23
27
* Temperature and humidity sensors in an air-conditioning unit.
@@ -26,23 +30,25 @@ An IoT device is typically made up of a circuit board with sensors attached that
26
30
27
31
There's a wide variety of devices available from different manufacturers to build your solution. For a list of devices certified to work with Azure IoT Hub, see the [Azure Certified for IoT device catalog](https://devicecatalog.azure.com). For prototyping, you can use devices such as an [MXChip IoT DevKit](https://microsoft.github.io/azure-iot-developer-kit/) or a [Raspberry Pi](https://www.raspberrypi.org/). The Devkit has built-in sensors for temperature, pressure, humidity, and a gyroscope, accelerometer, and magnetometer. The Raspberry Pi lets you attach many different types of sensor.
28
32
29
-
Microsoft provides open-source [Device SDKs](../iot-hub/iot-hub-devguide-sdks.md) that you can use to build the apps that run on your devices. These [SDKs simplify and accelerate](https://azure.microsoft.com/blog/benefits-of-using-the-azure-iot-sdks-in-your-azure-iot-solution/) the development of your IoT solutions.
33
+
Microsoft provides open-source [Device SDKs](../iot-hub/iot-hub-devguide-sdks.md) that you can use to build the apps that run on your devices.
34
+
35
+
To learn more, see [IoT device development](iot-overview-device-development.md).
30
36
31
-
## Communication
37
+
## Connectivity
32
38
33
-
Typically, IoT devices send telemetry from the sensors to back-end services in the cloud. However, other types of communication are possible such as a back-end service sending commands to your devices. The following are some examples of device-to-cloud and cloud-to-device communication:
39
+
Typically, IoT devices send telemetry from the sensors to cloud services in your solution. However, other types of communication are possible such as a cloud service sending commands to your devices. The following are some examples of device-to-cloud and cloud-to-device communication:
34
40
35
41
* A mobile refrigeration truck sends temperature every 5 minutes to an IoT Hub.
36
42
37
-
*The back-end service sends a command to a device to change the frequency at which it sends telemetry to help diagnose a problem.
43
+
*A cloud service sends a command to a device to change the frequency at which it sends telemetry to help diagnose a problem.
38
44
39
45
* A device sends alerts based on the values read from its sensors. For example, a device monitoring a batch reactor in a chemical plant, sends an alert when the temperature exceeds a certain value.
40
46
41
47
* Your devices send information to display on a dashboard for viewing by human operators. For example, a control room in a refinery may show the temperature, pressure, and flow volumes in each pipe, enabling operators to monitor the facility.
42
48
43
49
The [IoT Device SDKs](../iot-hub/iot-hub-devguide-sdks.md) and IoT Hub support common [communication protocols](../iot-hub/iot-hub-devguide-protocols.md) such as HTTP, MQTT, and AMQP.
44
50
45
-
IoT devices have different characteristics when compared to other clients such as browsers and mobile apps. The device SDKs help you address the challenges of connecting devices securely and reliably to your back-end service. Specifically, IoT devices:
51
+
IoT devices have different characteristics when compared to other clients such as browsers and mobile apps. The device SDKs help you address the challenges of connecting devices securely and reliably to your cloud services. Specifically, IoT devices:
46
52
47
53
* Are often embedded systems with no human operator.
48
54
* Can be deployed in remote locations, where physical access is expensive.
@@ -51,9 +57,11 @@ IoT devices have different characteristics when compared to other clients such a
51
57
* May have intermittent, slow, or expensive network connectivity.
52
58
* May need to use proprietary, custom, or industry-specific application protocols.
53
59
54
-
## Back-end services
60
+
To learn more, see [Device infrastructure and connectivity](iot-overview-device-connectivity.md).
55
61
56
-
In an IoT solution, the back-end service provides functionality such as:
62
+
## Cloud services
63
+
64
+
In an IoT solution, the cloud services provide functionality such as:
57
65
58
66
* Receiving telemetry at scale from your devices, and determining how to process and store that data.
59
67
* Analyzing the telemetry to provide insights, either in real time or after the fact.
@@ -62,18 +70,23 @@ In an IoT solution, the back-end service provides functionality such as:
62
70
* Controlling the state of your devices and monitoring their activities.
63
71
* Managing the firmware installed on your devices.
64
72
65
-
For example, in a remote monitoring solution for an oil pumping station, the cloud back end uses telemetry from the pumps to identify anomalous behavior. When the back-end service identifies an anomaly, it can automatically send a command back to the device to take a corrective action. This process generates an automated feedback loop between the device and the cloud that greatly increases the solution efficiency.
73
+
For example, in a remote monitoring solution for an oil pumping station, the cloud back end uses telemetry from the pumps to identify anomalous behavior. When a cloud service identifies an anomaly, it can automatically send a command back to the device to take a corrective action. This process generates an automated feedback loop between the device and the cloud that greatly increases the solution efficiency.
66
74
67
-
## Azure IoT examples
75
+
Some cloud services, such as IoT Hub and the Device Provisioning Service, are IoT specific. Other cloud services can provide generic services to your solution such as storage and visualizations.
68
76
69
-
For real-life examples of how organizations use Azure IoT, see [Microsoft Technical Case Studies for IoT](https://microsoft.github.io/techcasestudies/#technology=IoT&sortBy=featured).
77
+
## Solution-wide concerns
70
78
71
-
For an in-depth discussion of IoT architecture, see the [Microsoft Azure IoT Reference Architecture](/azure/architecture/reference-architectures/iot).
79
+
Any IoT solution has to address the following solution-wide concerns:
72
80
73
-
## Next steps
81
+
*[Security](iot-security-best-practices.md) including physical security, authentication, authorization, and encryption
82
+
* Solution management including deployment and monitoring.
83
+
* High availability and disaster recovery for all the services in your solution.
84
+
* Scalability for all the services in your solution.
74
85
75
-
For some actual business cases and the architecture used, see the [Microsoft Azure IoT Technical Case Studies](https://microsoft.github.io/techcasestudies/#technology=IoT&sortBy=featured).
86
+
## Next steps
76
87
77
-
For some sample projects that you can try out with an IoT DevKit, see the [IoT DevKit Project Catalog](https://microsoft.github.io/azure-iot-developer-kit/docs/projects/).
88
+
Suggested next steps to explore Azure IoT further include:
78
89
79
-
For a more comprehensive explanation of the different services and how they're used, see [Azure IoT services and technologies](iot-services-and-technologies.md).
Copy file name to clipboardExpand all lines: articles/iot/iot-overview-device-connectivity.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ IoT Central applications use the IoT Hub and the Device Provisioning Service (DP
20
20
21
21
The following diagram shows a high-level view of the components in a typical IoT solution. This article is focused on the connectivity between the devices and the IoT cloud services shown in the diagram.
Copy file name to clipboardExpand all lines: articles/iot/iot-overview-device-development.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,7 +123,7 @@ Using containers, such as Docker, to run your device code lets you deploy code t
123
123
Azure IoT Edge runs device code in containers. You can use Azure IoT Edge to deploy code modules to your devices. To learn more, see [Develop your own IoT Edge modules](../iot-edge/module-development.md).
124
124
125
125
> [!TIP]
126
-
> Azure IoT Edge enables multiple scenarios. In addition to running your IoT device code in containers, you can use Azure IoT Edge to run Azure services on your devices and implement [field gateways](iot-overview-connectivity.md#field-gateways). For more information, see [What is Azure IoT Edge?](../iot-edge/about-iot-edge.md)
126
+
> Azure IoT Edge enables multiple scenarios. In addition to running your IoT device code in containers, you can use Azure IoT Edge to run Azure services on your devices and implement [field gateways](iot-overview-device-connectivity.md#field-gateways). For more information, see [What is Azure IoT Edge?](../iot-edge/about-iot-edge.md)
127
127
128
128
## Development tools
129
129
@@ -139,5 +139,5 @@ The following table lists some of the available IoT development tools:
139
139
140
140
Now that you've seen an overview of device development in Azure IoT solutions, some suggested next steps include:
141
141
142
-
-[Device infrastructure and connectivity](iot-overview-connectivity.md)
142
+
-[Device infrastructure and connectivity](iot-overview-device-connectivity.md)
143
143
-[Device management and control](iot-overview-device-management.md)
0 commit comments