According to Microsoft's own Azure IoT Edge lifecycle page, the 1.5 LTS release — the long-term-support branch that most production gateways deployed over the last two years — stops receiving standard support at 11:59:59 PM PT on November 10, 2026 (6:59:59 AM UTC on November 11). Independent industrial-IoT analysis from Kai Waehner's Q4 2026 landscape report confirms the same date and frames it inside a broader retreat: Microsoft also retires Azure IoT Central on March 31, 2027, pointing every remaining customer toward Azure IoT Operations, its newer Arc-enabled, Kubernetes-based edge platform.
What Actually Changes on the Factory Floor
Devices already running IoT Edge 1.5 LTS do not stop working on November 11. What stops is the safety net: no more security patches, no more bug fixes, no more support tickets accepted for that version. For a gateway sitting between a PLC network and a cloud dashboard, that is a slow-burn risk rather than an outage — every CVE disclosed against the container runtime, the module twin sync logic or the underlying OS image from this point on goes unpatched unless the plant moves to a newer branch itself. The previous LTS, 1.4, already hit the same wall in November 2024, so some sites are now two major support cycles behind.
Azure IoT Edge 1.5 LTS — Key Facts
- End of standard support — November 10/11, 2026 (per Microsoft's official lifecycle page);
- Previous LTS (1.4) — already out of support since November 13, 2024;
- Related retirement — Azure IoT Central shuts down March 31, 2027;
- Microsoft's recommended path — migrate to Azure IoT Operations, a Kubernetes-based edge data plane;
- Who is affected — any plant, utility or logistics site running IoT Edge 1.5 modules on gateways, edge servers or industrial PCs;
- Immediate risk — unpatched CVEs in the container runtime and module stack, not a sudden device failure.
Why a Straight Upgrade Isn't Always the Right Call
Azure IoT Operations is built around a different operating model — Arc-enabled Kubernetes at the edge, an MQTT broker as the central nervous system, and a unified-namespace approach to tagging data — rather than being a drop-in replacement for IoT Edge modules. For manufacturers that built a handful of custom modules on top of 1.5 LTS (protocol translators, local historians, a specific OPC UA bridge), re-platforming onto IoT Operations on Microsoft's schedule is a real engineering project, not a config change. Some sites will decide the simpler move is to replace the aging gateway stack with a smaller, purpose-built edge service that does exactly what their line needs and isn't tied to a hyperscaler's own roadmap and retirement cycle.
That kind of scoped migration — mapping what the existing 1.5 LTS modules actually do, then rebuilding only those functions on a stack the plant controls going forward — is exactly the type of fixed-scope project a turnkey software development team is set up to deliver: a defined contract, a defined deadline and a working replacement before the old gateway runs out of patches.
Sources: Microsoft Learn — Azure IoT Edge lifecycle page; Kai Waehner, Industrial IoT Landscape Q4 2026.