Merge pull request #312434 from sethmanheim/iotfrsh2-27

IoT Edge freshness pass

Author: Court72

articles/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric.md

@@ -6,7 +6,7 @@ ms.author: sethm
 ms.service: azure-iot-edge
 services: iot-edge
 ms.topic: how-to
-ms.date: 05/16/2025
+ms.date: 03/02/2026
 ms.custom:
   - linux-related-content
   - sfi-ropc-nochange
@@ -24,7 +24,7 @@ The steps in this article walk through a process called manual provisioning, whe
 
 * **Symmetric keys**: When you create a new device identity in IoT Hub, the service creates two keys. You place one of the keys on the device, and it presents the key to IoT Hub when authenticating.
 
-  This authentication method is faster to get started, but not as secure.
+  This authentication method is faster to get started, but isn't as secure.
 
 * **X.509 self-signed**: You create two X.509 identity certificates and place them on the device. When you create a new device identity in IoT Hub, you provide thumbprints from both certificates. When the device authenticates to IoT Hub, it presents one certificate and IoT Hub verifies that the certificate matches its thumbprint.
 
@@ -33,15 +33,15 @@ The steps in this article walk through a process called manual provisioning, whe
 This article covers using symmetric keys as your authentication method. If you want to use X.509 certificates, see [Create and provision an IoT Edge for Linux on Windows device using X.509 certificates](how-to-provision-single-device-linux-on-windows-x509.md).
 
 > [!NOTE]
-> If you have many devices to set up and don't want to manually provision each one, use one of the following articles to learn how IoT Edge works with the IoT Hub device provisioning service:
+> If you need to set up many devices and don't want to manually provision each one, use one of the following articles to learn how IoT Edge works with the IoT Hub device provisioning service:
 >
 > * [Create and provision IoT Edge for Linux on Windows devices at scale using X.509 certificates](how-to-provision-devices-at-scale-linux-on-windows-x509.md)
 > * [Create and provision an IoT Edge for Linux on Windows device at scale by using a TPM](how-to-provision-devices-at-scale-linux-on-windows-tpm.md)
 > * [Create and provision IoT Edge for Linux on Windows devices at scale using symmetric keys](how-to-provision-devices-at-scale-linux-on-windows-symmetric.md)
 
 ## Prerequisites
 
-This article covers registering your IoT Edge device and installing IoT Edge for Linux on Windows. These tasks have different prerequisites and utilities used to accomplish them. Make sure you have all the prerequisites covered before proceeding.
+This article covers registering your IoT Edge device and installing IoT Edge for Linux on Windows. These tasks have different prerequisites and use different utilities. Make sure you meet all the prerequisites before proceeding.
 
 <!-- Device registration prerequisites H3 and content -->
 [!INCLUDE [iot-edge-prerequisites-register-device.md](includes/iot-edge-prerequisites-register-device.md)]
@@ -57,9 +57,9 @@ This article covers registering your IoT Edge device and installing IoT Edge for
 
 ## Provision the device with its cloud identity
 
-You're ready to set up your device with its cloud identity and authentication information.
+Set up your device with its cloud identity and authentication information.
 
-To provision your device using symmetric keys, you need your device's **connection string**.
+To provision your device using symmetric keys, you need your device *connection string*.
 
 Run the following command in an elevated PowerShell session on your target device. Replace the placeholder text with your own values.
 
@@ -71,18 +71,18 @@ For more information about the `Provision-EflowVM` command, see [PowerShell func
 
 ## Verify successful configuration
 
-Verify that IoT Edge for Linux on Windows was successfully installed and configured on your IoT Edge device.
+Verify that IoT Edge for Linux on Windows is successfully installed and configured on your IoT Edge device.
 
-1. Sign in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
+1. Sign in to your IoT Edge for Linux on Windows virtual machine by using the following command in your PowerShell session:
 
    ```powershell
    Connect-EflowVm
    ```
 
-   >[!NOTE]
-   >The only account allowed to SSH to the virtual machine is the user that created it.
+   > [!NOTE]
+   > The only account allowed to SSH to the virtual machine is the user that created it.
 
-1. Once you're logged in, you can check the list of running IoT Edge modules using the following Linux command:
+1. After you sign in, check the list of running IoT Edge modules by using the following Linux command:
 
    ```bash
    sudo iotedge list
@@ -96,23 +96,23 @@ Verify that IoT Edge for Linux on Windows was successfully installed and configu
        sudo iotedge system logs
        ```
 
-    2. Use the `check` tool to verify configuration and connection status of the device.
+    1. Use the `check` tool to verify configuration and connection status of the device.
 
        ```bash
        sudo iotedge check
        ```
 
-    >[!NOTE]
-    >On a newly provisioned device, you might see an error related to IoT Edge Hub:
+    > [!NOTE]
+    > On a newly provisioned device, you might see an error related to IoT Edge Hub:
     >
-    >**× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error**
+    > **× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error**
     >
-    >**Could not check current state of edgeHub container**
+    > **Could not check current state of edgeHub container**
     >
-    >This error is expected on a newly provisioned device because the IoT Edge Hub module isn't running. To resolve the error, in IoT Hub, set the modules for the device and create a deployment. Creating a deployment for the device starts the modules on the device including the IoT Edge Hub module.
+    > This error is expected on a newly provisioned device because the IoT Edge Hub module isn't running. To resolve the error, in IoT Hub, set the modules for the device and create a deployment. Creating a deployment for the device starts the modules on the device including the IoT Edge Hub module.
 
 
-When you create a new IoT Edge device, it displays the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
+When you create a new IoT Edge device, it displays the status code **417 -- The device's deployment configuration is not set** in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
 
 <!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
 [!INCLUDE [uninstall-iot-edge-linux-on-windows.md](includes/iot-edge-uninstall-linux-on-windows.md)]

articles/iot-edge/how-to-retrieve-iot-edge-logs.md

@@ -274,7 +274,7 @@ In the Azure portal, invoke the method with the method name `UploadModuleLogs` a
 
 ## Upload support bundle diagnostics
 
-Use the **UploadSupportBundle** direct method to bundle and upload a zip file of IoT Edge module logs to an available Azure Blob Storage container. This direct method runs the [`iotedge support-bundle`](./troubleshoot.md#gather-debug-information-with-support-bundle-command) command on your IoT Edge device to obtain the logs.
+Use the **UploadSupportBundle** direct method to bundle and upload a zip file of IoT Edge module logs to an available Azure Blob Storage container. This direct method runs the [`iotedge support-bundle`](./troubleshoot.md#gather-debug-information-by-using-the-support-bundle-command) command on your IoT Edge device to obtain the logs.
 
 > [!NOTE]
 > To upload logs from a device behind a gateway device, make sure the [API proxy and blob storage modules](how-to-configure-api-proxy-module.md) are set up on the top layer device. These modules route logs from your lower layer device through your gateway device to your storage in the cloud.

articles/iot-edge/includes/iot-edge-clean-up-cloud-resources.md

@@ -6,17 +6,17 @@ author: sethmanheim
 ms.author: sethm
 ms.service: azure-iot-edge
 ms.topic: include
-ms.date: 11/07/2025
+ms.date: 02/27/2026
 ms.custom: include file
 ---
 
 
 ### Delete Azure resources
 
-Deleting Azure resources and resource groups is irreversible. Make sure that you don't accidentally delete the wrong resource group or resources. If you created the IoT Hub inside an existing resource group that has resources that you want to keep, delete only the IoT Hub resource itself, not the resource group.
+You can't undo deleting Azure resources and resource groups. Make sure that you don't accidentally delete the wrong resource group or resources. If you created the IoT Hub inside an existing resource group that has resources you want to keep, delete only the IoT Hub resource itself, not the resource group.
 
 To delete the resources:
 
 1. Sign in to the [Azure portal](https://portal.azure.com), and then select **Resource groups**.
 1. Select the name of the resource group that contains your IoT Edge test resources.
-1. Review the list of resources that your resource group contains. If you want to delete all of them, you can select **Delete resource group**. If you want to delete only some of them, you can select each resource to delete them individually.
+1. Review the list of resources that your resource group contains. If you want to delete all of them, you can select **Delete resource group**. If you want to delete only some of them, select each resource to delete them individually.

articles/iot-edge/includes/iot-edge-install-linux-on-windows.md

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 01/16/2025
+ms.date: 03/02/2026
 author: sethmanheim
 ms.author: sethm
 ms.service: azure-iot-edge
@@ -46,7 +46,7 @@ Deploy Azure IoT Edge for Linux on Windows on your target device.
    Start-Process -Wait msiexec -ArgumentList "/i","$([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))","/qn","INSTALLDIR=D:\EFLOW", "VHDXDIR=D:\EFLOW-VHDX"
    ```
 
-1. Set the execution policy on the target device to `AllSigned` if it is not already. See the PowerShell prerequisites for commands to check the current execution policy and set the execution policy to `AllSigned`.
+1. Set the execution policy on the target device to `AllSigned` if it isn't already. See the PowerShell prerequisites for commands to check the current execution policy and set the execution policy to `AllSigned`.
 
 1. Create the IoT Edge for Linux on Windows deployment. The deployment creates your Linux virtual machine and installs the IoT Edge runtime for you.
 
@@ -55,9 +55,9 @@ Deploy Azure IoT Edge for Linux on Windows on your target device.
    ```
 
    >[!TIP]
-   >By default, the `Deploy-Eflow` command creates your Linux virtual machine with 1 GB of RAM, 1 vCPU core, and 16 GB of disk space. However, the resources your VM needs are highly dependent on the workloads you deploy. If your VM does not have sufficient memory to support your workloads, it will fail to start.
+   >By default, the `Deploy-Eflow` command creates your Linux virtual machine with 1 GB of RAM, 1 vCPU core, and 16 GB of disk space. However, the resources your VM needs are highly dependent on the workloads you deploy. If your VM doesn't have sufficient memory to support your workloads, it fails to start.
    >
-   >You can customize the virtual machine's available resources using the `Deploy-Eflow` command's optional parameters. This is required to deploy EFLOW on a device with the minimum hardware requirements.
+   >You can customize the virtual machine's available resources by using the `Deploy-Eflow` command's optional parameters. This customization is required to deploy EFLOW on a device with the minimum hardware requirements.
    >
    >For example, the following command creates a virtual machine with 1 vCPU core, 1 GB of RAM (represented in MB), and 2 GB of disk space:
    >
@@ -68,21 +68,21 @@ Deploy Azure IoT Edge for Linux on Windows on your target device.
    >For information about all the optional parameters available, see [PowerShell functions for IoT Edge for Linux on Windows](/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions#deploy-eflow).
 
    >[!WARNING]
-   >By default, the EFLOW Linux virtual machine has no DNS configuration. Deployments using DHCP will try to obtain the DNS configuration propagated by the DHCP server. Please check your DNS configuration to ensure internet connectivity. For more information, see [AzEFLOW-DNS](https://aka.ms/AzEFLOW-DNS).
+   >By default, the EFLOW Linux virtual machine has no DNS configuration. Deployments using DHCP try to obtain the DNS configuration propagated by the DHCP server. Check your DNS configuration to ensure internet connectivity. For more information, see [AzEFLOW-DNS](https://aka.ms/AzEFLOW-DNS).
 
    You can assign a GPU to your deployment to enable GPU-accelerated Linux modules. To gain access to these features, you need to install the prerequisites detailed in [GPU acceleration for Azure IoT Edge for Linux on Windows](/azure/iot-edge/gpu-acceleration).
 
    To use a GPU passthrough, add the **gpuName**, **gpuPassthroughType**, and **gpuCount** parameters to your `Deploy-Eflow` command. For information about all the optional parameters available, see [PowerShell functions for IoT Edge for Linux on Windows](/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions#deploy-eflow).
 
    >[!WARNING]
-   >Enabling hardware device passthrough may increase security risks. Microsoft recommends a device mitigation driver from your GPU's vendor, when applicable. For more information, see [Deploy graphics devices using discrete device assignment](/windows-server/virtualization/hyper-v/deploy/deploying-graphics-devices-using-dda).
+   >Enabling hardware device passthrough might increase security risks. Microsoft recommends a device mitigation driver from your GPU's vendor, when applicable. For more information, see [Deploy graphics devices using discrete device assignment](/windows-server/virtualization/hyper-v/deploy/deploying-graphics-devices-using-dda).
 
-1. Enter 'Y' to accept the license terms.
+1. Enter **Y** to accept the license terms.
 
-1. Enter 'O' or 'R' to toggle **Optional diagnostic data** on or off, depending on your preference.
+1. Enter **O** or **R** to toggle **Optional diagnostic data** on or off, depending on your preference.
 
 1. Once the deployment is complete, the PowerShell window reports **Deployment successful**.
 
-   ![A successful deployment will say 'Deployment successful' at the end of the messages, PNG.](media/iot-edge-install-linux-on-windows/successful-powershell-deployment.png)
+   ![Screenshot showing "Deployment successful" at the end of the messages.](media/iot-edge-install-linux-on-windows/successful-powershell-deployment.png)
 
-   After a successful deployment, you are ready to provision your device.
+   After a successful deployment, you're ready to provision your device.

articles/iot-edge/includes/iot-edge-prerequisites-linux-on-windows.md

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 05/15/2025
+ms.date: 03/02/2026
 author: sethmanheim
 ms.author: sethm
 ms.service: azure-iot-edge
@@ -12,45 +12,45 @@ services: iot-edge
 
 A Windows device with the following minimum requirements:
 
-* System Requirements
+* System requirements
    * Windows 10<sup>1</sup>/11 (Pro, Enterprise, IoT Enterprise)
    * Windows Server 2019<sup>1</sup>/2022  
-   <sub><sup>1</sup> Windows 10 and Windows Server 2019 minimum build 17763 with all current cumulative updates installed.</sub>
+   <sub><sup>1</sup> Windows 10 and Windows Server 2019, minimum build 17763, with all current cumulative updates installed.</sub>
 
 * Hardware requirements
-  * Minimum Free Memory: 1 GB
-  * Minimum Free Disk Space: 10 GB
+  * Minimum free memory: 1 GB
+  * Minimum free disk space: 10 GB
 
 * Virtualization support
   * On Windows 10, enable Hyper-V. For more information, see [Install Hyper-V](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v).
   * On Windows Server, install the Hyper-V role and create a default network switch. For more information, see [Nested virtualization for Azure IoT Edge for Linux on Windows](../nested-virtualization.md).
   * On a virtual machine, configure nested virtualization. For more information, see [Nested virtualization for Azure IoT Edge for Linux on Windows](../nested-virtualization.md).
 
 * Networking support
-  * Windows Server doesn't come with a default switch. Before you can deploy EFLOW to a Windows Server device, you need to create a virtual switch. For more information, see [Azure IoT Edge for Linux on Windows virtual switch creation](../how-to-create-virtual-switch.md).
-  * Windows Desktop versions come with a default switch that can be used for EFLOW installation. If needed, you can create your own custom virtual switch.
+  * Windows Server doesn't include a default switch. Before you can deploy EFLOW to a Windows Server device, you need to create a virtual switch. For more information, see [Azure IoT Edge for Linux on Windows virtual switch creation](../how-to-create-virtual-switch.md).
+  * Windows Desktop versions include a default switch that you can use for EFLOW installation. If needed, you can create your own custom virtual switch.
 
 > [!TIP]
-> If you want to use **GPU-accelerated Linux modules** in your Azure IoT Edge for Linux on Windows deployment, there are several configuration options to consider.
+> If you want to use **GPU-accelerated Linux modules** in your Azure IoT Edge for Linux on Windows deployment, consider several configuration options.
 >
 > You need to install the correct drivers depending on your GPU architecture, and you might need access to a Windows Insider Program build. To determine your configuration needs and satisfy these prerequisites, see [GPU acceleration for Azure IoT Edge for Linux on Windows](../gpu-acceleration.md).
 >
-> Make sure you take the time to satisfy the prerequisites for GPU acceleration now. You need to restart the installation process if you decide you want GPU acceleration during installation.
+> Make sure you satisfy the prerequisites for GPU acceleration now. You must restart the installation process if you decide you want GPU acceleration during installation.
 
 ### Developer tools
 
 Prepare your target device for the installation of Azure IoT Edge for Linux on Windows and the deployment of the Linux virtual machine:
 
-1. Set the execution policy on the target device to `AllSigned`. You can check the current execution policy in an elevated PowerShell prompt using the following command:
+1. Set the execution policy on the target device to `AllSigned`. You can check the current execution policy in an elevated PowerShell prompt by using the following command:
 
    ```powershell
    Get-ExecutionPolicy -List
    ```
 
-   If the execution policy of `local machine` isn't `AllSigned`, you can set the execution policy using:
+   If the execution policy for `local machine` isn't `AllSigned`, set the execution policy by using:
 
    ```powershell
    Set-ExecutionPolicy -ExecutionPolicy AllSigned -Force
    ```
 
-For more information on the Azure IoT Edge for Linux on Windows PowerShell module, see the [PowerShell functions reference](../reference-iot-edge-for-linux-on-windows-functions.md).
+For more information about the Azure IoT Edge for Linux on Windows PowerShell module, see the [PowerShell functions reference](../reference-iot-edge-for-linux-on-windows-functions.md).

articles/iot-edge/includes/iot-edge-uninstall-linux-on-windows.md

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 02/26/2026
+ms.date: 03/02/2026
 author: sethmanheim
 ms.author: sethm
 ms.service: azure-iot-edge

articles/iot-edge/includes/iot-edge-version-all-supported.md

@@ -6,11 +6,11 @@ author: sethmanheim
 ms.author: sethm
 ms.service: azure-iot-edge
 ms.topic: include
-ms.date: 08/28/2025
+ms.date: 02/27/2026
 ms.custom: include file
 ---
 
 **Applies to:** ![IoT Edge 1.5 checkmark](./media/iot-edge-version/yes-icon.png) IoT Edge 1.5
 
 > [!IMPORTANT]
-> IoT Edge 1.5 LTS is the [supported release](../support.md#releases). IoT Edge 1.4 LTS is end of life as of November 12, 2024. If you are on an earlier release, see [Update IoT Edge](../how-to-update-iot-edge.md).
+> IoT Edge 1.5 LTS is the [supported release](../support.md#releases). IoT Edge 1.4 LTS reached end of life on November 12, 2024. If you're using an earlier release, see [Update IoT Edge](../how-to-update-iot-edge.md).