Azure IoT Edge Documentation

Introduction to Azure IoT Edge

Azure IoT Edge is a managed cloud service that enables you to move cloud analytics and custom business logic from the cloud closer to your IoT devices. This hybrid cloud and edge pattern allows for rapid response, efficient operation, and reduced bandwidth costs.

IoT Edge enables you to deploy and manage intelligent edge solutions. It consists of three main components:

Key Capabilities

Important Note

IoT Edge is crucial for scenarios where processing data locally is beneficial due to latency, bandwidth, or privacy concerns. It bridges the gap between edge devices and powerful cloud services.

Getting Started with IoT Edge

To begin using Azure IoT Edge, you'll typically follow these steps:

  1. Provision an IoT Hub: Create an Azure IoT Hub instance to manage your devices and deploy workloads.
  2. Prepare your edge device: Install the IoT Edge runtime on your chosen device (Windows, Linux, or even virtual machines).
  3. Create and deploy modules: Develop or select pre-built modules (e.g., a data collector, a processing module) and define your deployment manifest.
  4. Deploy to device: Use IoT Hub to send the deployment manifest to your edge device, instructing it to download and run the specified modules.

For detailed instructions, refer to the Deployment guide.

Example Scenario: Local Data Processing

Consider a manufacturing plant where sensors generate a high volume of data. Instead of sending all raw data to the cloud, an IoT Edge device can run an Azure Stream Analytics module locally to filter, aggregate, and analyze the data in real-time. Only relevant insights or alerts are then sent to the cloud for further storage or analysis.


# Example: Deploying a simple "hello world" module
az iot edge set-modules --device-id myEdgeDevice --hub-name myIoTHub --content deployment.json
            

Tip

Explore the Azure IoT Edge Samples repository on GitHub for practical examples and ready-to-use code.

Key Concepts

For a deeper understanding of the underlying architecture, please visit the Architecture section.