Azure IoT Edge supported platforms
Applies to: IoT Edge 1.4
This article explains what operating system platforms, IoT Edge runtimes, container engines, and components are supported by IoT Edge whether generally available or in preview.
If you experience problems while using the Azure IoT Edge service, there are several ways to seek support. Try one of the following channels for support:
Reporting bugs - Most development that goes into the Azure IoT Edge product happens in the IoT Edge open-source project. Bugs can be reported on the issues page of the project. Bugs related to Azure IoT Edge for Linux on Windows can be reported on the iotedge-eflow issues page. Fixes rapidly make their way from the projects in to product updates.
Microsoft Customer Support team - Users who have a support plan can engage the Microsoft Customer Support team by creating a support ticket directly from the Azure portal.
Feature requests - The Azure IoT Edge product tracks feature requests via the product's Azure feedback community.
Azure IoT Edge modules are implemented as containers, so IoT Edge needs a container engine to launch them. Microsoft provides a container engine, moby-engine, to fulfill this requirement. This container engine is based on the Moby open-source project. Docker CE and Docker EE are other popular container engines. They're also based on the Moby open-source project and are compatible with Azure IoT Edge. Microsoft provides best effort support for systems using those container engines; however, Microsoft can't ship fixes for issues in them. For this reason, Microsoft recommends using moby-engine on production systems.
Azure IoT Edge runs on most operating systems that can run containers; however, not all of these systems are equally supported. Operating systems are grouped into tiers that represent the level of support users can expect.
- Tier 1 systems are supported. For tier 1 systems, Microsoft:
- has this operating system in automated tests
- provides installation packages for them
- Tier 2 systems are compatible with Azure IoT Edge and can be used relatively easily. For tier 2 systems:
- Microsoft has done informal testing on the platforms or knows of a partner successfully running Azure IoT Edge on the platform
- Installation packages for other platforms may work on these platforms
The systems listed in the following tables are supported by Microsoft, either generally available or in public preview, and are tested with each new release.
Modules built as Linux containers can be deployed to either Linux or Windows devices. For Linux devices, the IoT Edge runtime is installed directly on the host device. For Windows devices, a Linux virtual machine prebuilt with the IoT Edge runtime runs on the host device.
IoT Edge for Linux on Windows is the recommended way to run IoT Edge on Windows devices.
|Debian 11 (Bullseye)|
|Red Hat Enterprise Linux 8|
|Ubuntu Server 22.04|
|Ubuntu Server 20.04|
|Ubuntu Server 18.04|
|Windows 10/11 Pro|
|Windows 10/11 Enterprise|
|Windows 10/11 IoT Enterprise|
|Windows Server 2019/2022|
All Windows operating systems must be minimum build 17763 with all current cumulative updates installed.
We no longer support Windows containers. IoT Edge for Linux on Windows is the recommended way to run IoT Edge on Windows devices.
The systems listed in the following table are considered compatible with Azure IoT Edge, but aren't actively tested or maintained by Microsoft.
|Debian 10 1|
|Mentor Embedded Linux Flex OS|
|Mentor Embedded Linux Omni OS|
|Ubuntu 18.04 2|
|Ubuntu 20.04 2|
|Ubuntu 22.04 2|
|Wind River 8|
|Raspberry Pi OS Buster|
1 With the release of 1.3, there are new system calls that cause crashes in Debian 10. To see the workaround, view the Known issue: Debian 10 (Buster) on ARMv7 section of the 1.3 release notes for details.
2 Installation packages are made available on the Azure IoT Edge releases. See the installation steps in Offline or specific version installation.
The following table lists the currently supported releases. IoT Edge release assets and release notes are available on the azure-iotedge releases page.
|Release notes and assets||Type||Release Date||End of Support Date|
|1.4||Long-term support (LTS)||August 2022||November 12, 2024|
For more information on IoT Edge version history, see, Version history.
- Every Microsoft product has a lifecycle. The lifecycle begins when a product is released and ends when it's no longer supported. Knowing key dates in this lifecycle helps you make informed decisions about when to upgrade or make other changes to your software. IoT Edge is governed by Microsoft's Modern Lifecycle Policy.
IoT Edge uses the Microsoft.Azure.Devices.Client SDK. For more information, see the Azure IoT C# SDK GitHub repo or the Azure SDK for .NET reference content. The following list shows the version of the client SDK that each release is tested against:
|IoT Edge version||Microsoft.Azure.Devices.Client SDK version|
Azure IoT Edge can be run in virtual machines, such as an Azure Virtual Machine. Using a virtual machine as an IoT Edge device is common when customers want to augment existing infrastructure with edge intelligence. The family of the host VM OS must match the family of the guest OS used inside a module's container. This requirement is the same as when Azure IoT Edge is run directly on a device. Azure IoT Edge is agnostic of the underlying virtualization technology and works in VMs powered by platforms like Hyper-V and vSphere.
Minimum system requirements
Azure IoT Edge runs great on devices as small as a Raspberry Pi3 to server grade hardware. Choosing the right hardware for your scenario depends on the workloads that you want to run. Making the final device decision can be complicated; however, you can easily start prototyping a solution on traditional laptops or desktops.
Experience while prototyping will help guide your final device selection. Questions you should consider include:
- How many modules are in your workload?
- How many layers do your modules' containers share?
- In what language are your modules written?
- How much data will your modules be processing?
- Do your modules need any specialized hardware for accelerating their workloads?
- What are the desired performance characteristics of your solution?
- What is your hardware budget?
Submit and view feedback for