You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-edge/how-to-provision-devices-at-scale-linux-x509.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure IoT Edge
4
4
description: Use X.509 certificates to test provisioning devices at scale for Azure IoT Edge with device provisioning service
5
5
author: sethmanheim
6
6
ms.author: sethm
7
-
ms.date: 02/24/2026
7
+
ms.date: 03/02/2026
8
8
ms.topic: how-to
9
9
ms.service: azure-iot-edge
10
10
ms.custom: linux-related-content
@@ -26,7 +26,7 @@ Here are the steps to provision IoT Edge devices using X.509 certificates:
26
26
X.509 certificates let you scale production and simplify device provisioning. Typically, X.509 certificates are arranged in a certificate chain of trust. The chain starts with a self-signed or trusted root certificate, and each certificate in the chain signs the next lower certificate. This pattern creates a delegated chain of trust from the root certificate through each intermediate certificate to the final downstream device certificate installed on a device.
27
27
28
28
> [!TIP]
29
-
> If your device has a Hardware Security Module (HSM) like a TPM 2.0, store the X.509 keys securely in the HSM. Learn how to implement zero-touch provisioning at scale in [this blueprint](https://azure.microsoft.com/blog/the-blueprint-to-securely-solve-the-elusive-zerotouch-provisioning-of-iot-devices-at-scale/)with the [iotedge-tpm2cloud](https://aka.ms/iotedge-tpm2cloud) sample.
29
+
> If your device has a Hardware Security Module (HSM) like a TPM 2.0, store the X.509 keys securely in the HSM. Learn how to implement zero-touch provisioning at scale with the [iotedge-tpm2cloud](https://aka.ms/iotedge-tpm2cloud) sample.
Copy file name to clipboardExpand all lines: articles/iot-edge/iot-edge-security-manager.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: iot-edge
5
5
keywords: security, secure element, enclave, TEE, IoT Edge
6
6
author: sethmanheim
7
7
ms.author: sethm
8
-
ms.date: 02/24/2026
8
+
ms.date: 03/02/2026
9
9
ms.topic: concept-article
10
10
ms.service: azure-iot-edge
11
11
---
@@ -127,8 +127,5 @@ Create and provision an IoT Edge device with a virtual TPM on [Linux](how-to-pro
127
127
128
128
## Next steps
129
129
130
-
Learn more about securing your IoT Edge devices in these blog posts:
131
-
132
-
*[Securing the intelligent edge](https://azure.microsoft.com/blog/securing-the-intelligent-edge/)
133
-
*[The blueprint to securely solve the elusive zero-touch provisioning of IoT devices at scale](https://azure.microsoft.com/blog/the-blueprint-to-securely-solve-the-elusive-zerotouch-provisioning-of-iot-devices-at-scale/)
134
-
*[Solving IoT device security at scale through standards](https://azure.microsoft.com/blog/solving-iot-device-security-at-scale-through-standards/)
130
+
*[Understand the IoT Edge security framework](security.md)
131
+
*[Learn about IoT Edge certificates](iot-edge-certs.md)
Copy file name to clipboardExpand all lines: articles/iot-edge/version-history.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: IoT Edge version history and release notes
3
3
description: Release history and notes for IoT Edge.
4
4
author: sethmanheim
5
5
ms.author: sethm
6
-
ms.date: 02/25/2026
6
+
ms.date: 03/02/2026
7
7
ms.topic: concept-article
8
8
ms.service: azure-iot-edge
9
9
---
@@ -49,7 +49,7 @@ This table provides recent version history for IoT Edge package releases, and hi
49
49
|[1.5](https://github.com/Azure/azure-iotedge/releases/tag/1.5.0)| 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](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle). <br> Edge Agent and Edge Hub now support TLS 1.3 for inbound/outbound communication. |
50
50
|[1.4](https://github.com/Azure/azure-iotedge/releases/tag/1.4.0)| Long-term support (LTS) | August 2022 | November 12, 2024 | IoT Edge 1.4 LTS was supported through November 12, 2024 to match the [.NET 6 release lifecycle](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle). <br> Automatic image clean-up of unused Docker images. <br> Ability to pass a [custom JSON payload to DPS on provisioning](../iot-dps/how-to-send-additional-data.md#iot-edge-support). <br> Ability to require all modules in a deployment to be downloaded before restart. <br> 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 configuration](https://github.com/Azure/iotedge/blob/main/edgelet/contrib/config/linux/template.toml#L276-L302). |
51
51
|[1.3](https://github.com/Azure/azure-iotedge/releases/tag/1.3.0)| Stable | June 2022 | August 2022 | Support for Red Hat Enterprise Linux 8 on AMD and Intel 64-bit architectures.<br>Edge Hub now enforces that inbound/outbound communication uses minimum TLS version 1.2 by default.<br>Updated runtime modules (edgeAgent, edgeHub) based on .NET 6. |
52
-
|[1.2](https://github.com/Azure/azure-iotedge/releases/tag/1.2.0)| Stable | April 2021 | June 2022 |[IoT Edge devices behind gateways](how-to-connect-downstream-iot-edge-device.md)<br>[IoT Edge MQTT broker (preview)](how-to-publish-subscribe.md)<br>New IoT Edge packages introduced, with new installation and configuration steps.<br>Includes [Microsoft Defender for IoT micro-agent for Edge](../defender-for-iot/device-builders/overview.md).<br> Integration with Device Update. For more information, see [Update IoT Edge](how-to-update-iot-edge.md). |
52
+
|[1.2](https://github.com/Azure/azure-iotedge/releases/tag/1.2.0)| Stable | April 2021 | June 2022 |[IoT Edge devices behind gateways](how-to-connect-downstream-iot-edge-device.md)<br>IoT Edge MQTT broker (preview)<br>New IoT Edge packages introduced, with new installation and configuration steps.<br>Includes [Microsoft Defender for IoT micro-agent for Edge](../defender-for-iot/device-builders/overview.md).<br> Integration with Device Update. For more information, see [Update IoT Edge](how-to-update-iot-edge.md). |
53
53
|[1.1](https://github.com/Azure/azure-iotedge/releases/tag/1.1.0)| 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](https://dotnet.microsoft.com/platform/support/policy/dotnet-core). <br> [Long-term support plan and supported systems updates](support.md)|
54
54
|[1.0.10](https://github.com/Azure/azure-iotedge/releases/tag/1.0.10)| Stable | October 2020 | February 2021 |[UploadSupportBundle direct method](how-to-retrieve-iot-edge-logs.md#upload-support-bundle-diagnostics)<br>[Upload runtime metrics](how-to-access-built-in-metrics.md)<br>[Route priority and time-to-live](module-composition.md#priority-and-time-to-live)<br>[Module startup order](module-composition.md#configure-modules)<br>[X.509 manual provisioning](how-to-provision-single-device-linux-x509.md)|
55
55
|[1.0.9](https://github.com/Azure/azure-iotedge/releases/tag/1.0.9)| Stable | March 2020 | October 2020 | X.509 autoprovisioning with DPS<br>[RestartModule direct method](how-to-edgeagent-direct-method.md#restart-module)<br>[support-bundle command](troubleshoot.md#gather-debug-information-with-support-bundle-command)|
0 commit comments