What is Azure Internet of Things (IoT)?

The Azure Internet of Things (IoT) is a collection of Microsoft-managed cloud services, edge components, and SDKs that let you connect, monitor, and control your IoT assets at scale. In simpler terms, an IoT solution is made up of IoT devices that communicate with cloud services.

The following diagram shows a high-level view of the components in a typical IoT solution. This article focuses on the 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.

Solution options

To build an IoT solution for your business, you typically evaluate your solution by using the managed app platform approach. You can build your enterprise solution by using either the platform services or the managed app platform approach.

A managed app platform lets you quickly evaluate your IoT solution by reducing the number of decisions needed to achieve results. The managed app platform takes care of most infrastructure elements in your solution, letting you focus on adding industry knowledge and evaluating the solution. Azure IoT Central is a managed app platform.

Platform services provide all the building blocks for customized and flexible IoT applications. You have more options to choose and code when you connect your devices, and ingest, store, and analyze your data. Azure IoT platform services include Azure IoT Hub, Device Provisioning Service, and Azure Digital Twins. Other platform services that might be part of your IoT solution include Azure Data Explorer, Azure Storage platform, and Azure Functions.

To learn more, see What Azure technologies and services can you use to create IoT solutions?.

IoT devices

An IoT device is typically made up of a circuit board with sensors attached that uses WiFi to connect to the internet. For example:

• A pressure sensor on a remote oil pump.
• Temperature and humidity sensors in an air-conditioning unit.
• An accelerometer in an elevator.
• Presence sensors in a room.

There's a wide variety of devices available from different manufacturers to build your solution. For prototyping a microprocessor device, you can use a device such as a Raspberry Pi. The Raspberry Pi lets you attach many different types of sensor. For prototyping a microcontroller device, use devices such as the ESPRESSIF ESP32, or Tutorial: Use Eclipse ThreadX to connect an STMicroelectronics B-L475E-IOT01A Discovery kit to IoT Hub. These boards typically have built-in sensors, such as temperature and accelerometer sensors.

Microsoft provides open-source Device SDKs that you can use to build the apps that run on your devices.

To learn more about the devices in your IoT solution, see IoT device development.

Connectivity

Typically, IoT devices send telemetry from their attached 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 examples of device-to-cloud and cloud-to-device communication:

• A mobile refrigeration truck sends temperature every 5 minutes to an IoT Hub.

• A cloud service sends a command to a device to change the frequency at which it sends telemetry to help diagnose a problem.

• A device monitoring a batch reactor in a chemical plant sends an alert when the temperature exceeds a certain value.

• A thermostat reports the maximum temperature the device has reached since the last reboot.

• A cloud service sets the target temperature for a thermostat device.

The IoT Device SDKs and IoT Hub support common communication protocols such as HTTP, MQTT, and AMQP for device-to-cloud and cloud-to-device communication. In some scenarios, you might need a gateway to connect your IoT devices to your cloud services.

IoT devices have different characteristics when compared to other clients such as browsers and mobile apps. Specifically, IoT devices:

• Are often embedded systems with no human operator.
• Can be deployed in remote locations, where physical access is expensive.
• Might only be reachable through the solution back end.
• Might have limited power and processing resources.
• Might have intermittent, slow, or expensive network connectivity.
• Might need to use proprietary, custom, or industry-specific application protocols.

The device SDKs help you address the challenges of connecting devices securely and reliably to your cloud services.

To learn more device connectivity and gateways, see Device infrastructure and connectivity.

Cloud services

In an IoT solution, the cloud services typically:

• Receive telemetry at scale from your devices, and determine how to process and store that data.
• Analyze the telemetry to provide insights, either in real time or after the fact.
• Send commands from the cloud to specific devices.
• Provision devices and control which devices can connect to your infrastructure.
• Control the state of your devices and monitor their activities.
• Manage the firmware installed on your devices.

For example, in a remote monitoring solution for an oil pumping station, the services use telemetry from the pumps to identify anomalous behavior. When a cloud service identifies an anomaly, it can automatically send a command to the device to take a corrective action. This process implements an automated feedback loop between the device and the cloud that greatly increases the solution efficiency.

Some cloud services, such as IoT Hub and the Device Provisioning Service, are IoT specific. Other cloud services, such as storage and visualization, provide generic services to your solution.

To learn more, see:

• Device management and control
• Message processing in an IoT solution
• Extend your IoT solution
• Analyze and visualize your IoT data

Solution-wide concerns

Any IoT solution must address the following solution-wide concerns:

• Security including physical security, authentication, authorization, and encryption.
• Solution management including deployment and monitoring.
• High availability and disaster recovery for all the components in your solution.
• Scalability for all the services in your solution.

IoT Operations

Azure IoT Operations Preview – enabled by Azure Arc is a unified data plane for the edge. Azure IoT Operations is a set of modular, scalable, and highly available data services that run on Azure Arc-enabled edge Kubernetes clusters. It enables data capture from various different systems and integrates with data modeling applications such as Microsoft Fabric to help organizations deploy the industrial metaverse. To learn more, see What is Azure IoT Operations?.

Next steps

Suggested next steps to explore Azure IoT further include:

• IoT device development
• Device infrastructure and connectivity
• Azure IoT services and technologies

To learn more about Azure IoT architecture, see:

• Well-architected framework: overview of IoT workloads
• Azure IoT reference architecture
• Industry specific Azure IoT reference architectures