Azure IoT Edge versions and release notes
Applies to: 
IoT Edge 1.5 IoT Edge 1.4
Important
IoT Edge 1.5 LTS and IoT Edge 1.4 LTS are supported releases. IoT Edge 1.4 LTS is end of life on November 12, 2024. If you are on an earlier release, see Update IoT Edge.
Azure IoT Edge is a product built from the open-source IoT Edge project hosted on GitHub. All new releases are made available in the Azure IoT Edge project. Contributions and bug reports can be made on the open-source IoT Edge project.
Azure IoT Edge is governed by Microsoft's Modern Lifecycle Policy.
Documented versions
The IoT Edge documentation on this site is available for two different versions of the product. Currently, the two supported versions are:
- IoT Edge 1.5 (LTS) is the latest long-term support (LTS) version of IoT Edge and contains content for new features and capabilities that are in the latest stable release. The documentation for this version covers all features and capabilities from all previous versions through 1.5.
- IoT Edge 1.4 (LTS) is the previous long-term support (LTS) version of IoT Edge and is supported until November 12, 2024. This version of the documentation also contains content for the IoT Edge for Linux on Windows (EFLOW). The documentation for this version is included with IoT Edge 1.5.
IoT Edge 1.1 (LTS) is the first long-term support (LTS) version of IoT Edge. It is no longer supported. The documentation has been archived.
For more information about IoT Edge releases, see Azure IoT Edge supported systems.
IoT Edge for Linux on Windows
Azure IoT Edge for Linux on Windows (EFLOW) supports the following versions:
- EFLOW Continuous Release (CR) based on the latest non-LTS Azure IoT Edge version, it contains new features and capabilities that are in the latest stable release. For more information, see the EFLOW release notes.
- EFLOW 1.1 (LTS) based on Azure IoT Edge 1.1, it's the Long-term support version. This version will be stable through the supported lifetime of this version and won't include new features released in later versions. This version will be supported until Dec 2022 to match the IoT Edge 1.1 LTS release lifecycle.
- EFLOW 1.4 (LTS) based on Azure IoT Edge 1.4. It's the latest Long-term support version. This version will be stable through the supported lifetime of this version and won't include new features released in later versions. This version will be supported until Nov 2024 to match the IoT Edge 1.4 LTS release lifecycle.
All new releases are made available in the Azure IoT Edge for Linux on Windows project.
Version history
This table provides recent version history for IoT Edge package releases, and highlights documentation updates made for each version.
Note
Long-term servicing (LTS) releases are serviced for a fixed period. Updates to this release type contain critical security and bug fixes only. All other stable releases are continuously supported and serviced. A stable release may contain features updates along with critical security fixes. Stable releases are supported only until the next release (stable or LTS) is generally available.
| Release notes and assets | Type | Release Date | End of Support Date | Highlights |
|---|---|---|---|---|
| 1.5 | Long-term support (LTS) | April 2024 | November 10, 2026 | IoT Edge 1.5 LTS is supported through November 10, 2026 to match the .NET 8 release lifecycle. Edge Agent and Edge Hub now support TLS 1.3 for inbound/outbound communication. |
| 1.4 | Long-term support (LTS) | August 2022 | November 12, 2024 | IoT Edge 1.4 LTS is supported through November 12, 2024 to match the .NET 6 release lifecycle. Automatic image clean-up of unused Docker images Ability to pass a custom JSON payload to DPS on provisioning Ability to require all modules in a deployment be downloaded before restart Use of the TCG TPM2 Software Stack which enables TPM hierarchy authorization values, specifying the TPM index at which to persist the DPS authentication key, and accommodating more TPM configurations |
| 1.3 | Stable | June 2022 | August 2022 | Support for Red Hat Enterprise Linux 8 on AMD and Intel 64-bit architectures. Edge Hub now enforces that inbound/outbound communication uses minimum TLS version 1.2 by default Updated runtime modules (edgeAgent, edgeHub) based on .NET 6 |
| 1.2 | Stable | April 2021 | June 2022 | IoT Edge devices behind gateways IoT Edge MQTT broker (preview) New IoT Edge packages introduced, with new installation and configuration steps. Includes Microsoft Defender for IoT micro-agent for Edge. Integration with Device Update. For more information, see Update IoT Edge. |
| 1.1 | Long-term support (LTS) | February 2021 | December 13, 2022 | IoT Edge 1.1 LTS is supported through December 13, 2022 to match the .NET Core 3.1 release lifecycle. Long-term support plan and supported systems updates |
| 1.0.10 | Stable | October 2020 | February 2021 | UploadSupportBundle direct method Upload runtime metrics Route priority and time-to-live Module startup order X.509 manual provisioning |
| 1.0.9 | Stable | March 2020 | October 2020 | X.509 auto-provisioning with DPS RestartModule direct method support-bundle command |
IoT Edge for Linux on Windows
| IoT Edge release | Available in EFLOW branch | Release date | End of Support Date | Highlights |
|---|---|---|---|---|
| 1.4 | Long-term support (LTS) | November 2022 | November 12, 2024 | Azure IoT Edge 1.4.0 CBL-Mariner 2.0 USB passthrough using USB-Over-IP File/Folder sharing between Windows OS and the EFLOW VM |
| 1.3 | Continuous release (CR) | September 2022 | In support | Azure IoT Edge 1.3.0 CBL-Mariner 2.0 USB passthrough using USB-Over-IP File/Folder sharing between Windows OS and the EFLOW VM |
| 1.2 | Continuous release (CR) | January 2022 | September 2022 | Public Preview |
| 1.1 | Long-term support (LTS) | June 2021 | December 13, 2022 | IoT Edge 1.1 LTS is supported through December 13, 2022 to match the .NET Core 3.1 release lifecycle. Long-term support plan and supported systems updates |
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for