Remove deprecated Windows containers content and clarify Windows support

- Remove three deprecated 'Windows containers' sections from proxy support page
  (install, Moby daemon, IoT Edge daemon). Native Windows containers are no longer
  supported; only EFLOW is supported on Windows.
- Remove stale 'offline installation option' reference for Windows in intro.
- Clarify Windows support in about-iot-edge.md: replace ambiguous 'supports both
  Linux and Windows' with specific language about EFLOW, linking to the EFLOW
  overview page.

Author: jlian

articles/iot-edge/about-iot-edge.md

@@ -6,7 +6,7 @@ ms.author: sethm
 ms.service: azure-iot-edge
 services: iot-edge
 ms.topic: overview
-ms.date: 02/20/2026
+ms.date: 04/01/2026
 ms.custom:
   - mvc, linux-related-content
   - ai-gen-docs-bap
@@ -44,7 +44,7 @@ Azure IoT Edge allows you to deploy advanced AI capabilities like machine learni
 
 ### Bring your own code
 
-When you want to deploy your own code to your devices, Azure IoT Edge supports that, too. Azure IoT Edge holds to the same programming model as the other Azure IoT services. You can run the same code on a device or in the cloud. Azure IoT Edge supports both Linux and Windows so you can code to the platform of your choice. It supports Java, .NET, Node.js, C, and Python, so your developers can code in a language they already know and use existing business logic.
+When you want to deploy your own code to your devices, Azure IoT Edge supports that, too. Azure IoT Edge holds to the same programming model as the other Azure IoT services. You can run the same code on a device or in the cloud. Azure IoT Edge runs natively on Linux and on Windows devices through [IoT Edge for Linux on Windows (EFLOW)](iot-edge-for-linux-on-windows.md). It supports Java, .NET, Node.js, C, and Python, so your developers can code in a language they already know and use existing business logic.
 
 ## IoT Edge runtime
 
@@ -60,7 +60,7 @@ The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices. T
 
 How you use an Azure IoT Edge device is up to you. The runtime is often used to deploy AI to gateway devices that aggregate and process data from other on-premises devices, but this deployment model is just one option.
 
-The Azure IoT Edge runtime runs on a large set of IoT devices that enables using it in a wide variety of ways. It supports both Linux and Windows operating systems and abstracts hardware details. Use a device smaller than a Raspberry Pi 3 if you're not processing much data, or use an industrial server to run resource-intensive applications.
+The Azure IoT Edge runtime runs on a large set of IoT devices that enables using it in a wide variety of ways. It runs natively on Linux and on Windows devices through [IoT Edge for Linux on Windows (EFLOW)](iot-edge-for-linux-on-windows.md), and abstracts hardware details. Use a device smaller than a Raspberry Pi 3 if you're not processing much data, or use an industrial server to run resource-intensive applications.
 
 ## IoT Edge cloud interface
 

articles/iot-edge/how-to-configure-proxy-support.md

@@ -3,7 +3,7 @@ title: Configure devices for network proxies for Azure IoT Edge
 description: Learn how to configure Azure IoT Edge devices to communicate through a proxy server.
 author: sethmanheim
 ms.author: sethm
-ms.date: 05/09/2025
+ms.date: 04/01/2026
 ms.topic: how-to
 ms.service: azure-iot-edge
 services: iot-edge
@@ -25,7 +25,7 @@ This article explains the four steps to configure and manage an IoT Edge device
 
 1. [**Install the IoT Edge runtime on your device**](#install-iot-edge-through-a-proxy)
 
-   The IoT Edge installation scripts pull packages and files from the internet, so the device communicates through the proxy server to make those requests. For Windows devices, the installation script also provides an offline installation option.
+   The IoT Edge installation scripts pull packages and files from the internet, so the device communicates through the proxy server to make those requests.
 
    This step is a one-time process to configure the IoT Edge device when you first set it up. You also need these same connections when you update the IoT Edge runtime.
 
@@ -71,34 +71,6 @@ If you're installing the IoT Edge runtime on a Linux device, set up the package
 
 If you're installing the IoT Edge runtime using IoT Edge for Linux on Windows, the IoT Edge runtime is installed by default on your Linux virtual machine. You're not required to install or update any other steps.
 
-### Windows devices using Windows containers
-
-If you're installing the IoT Edge runtime on a Windows device, you need to go through the proxy server twice. The first connection downloads the installer script file, and the second connection downloads the necessary components during installation. You can configure proxy information in Windows settings, or include your proxy information directly in the PowerShell commands.
-
-The following steps show an example of a Windows installation using the `-proxy` argument:
-
-1. The Invoke-WebRequest command needs proxy information to access the installer script. Then the Deploy-IoTEdge command needs the proxy information to download the installation files.
-
-   ```powershell
-   . {Invoke-WebRequest -proxy <proxy URL> -useb aka.ms/iotedge-win} | Invoke-Expression; Deploy-IoTEdge -proxy <proxy URL>
-   ```
-
-2. The Initialize-IoTEdge command doesn't need to go through the proxy server, so the second step only requires proxy information for Invoke-WebRequest.
-
-   ```powershell
-   . {Invoke-WebRequest -proxy <proxy URL> -useb aka.ms/iotedge-win} | Invoke-Expression; Initialize-IoTEdge
-   ```
-
-If your proxy server credentials are complex and can't be included in the URL, use the `-ProxyCredential` parameter within `-InvokeWebRequestParameters`. For example,
-
-```powershell
-$proxyCredential = (Get-Credential).GetNetworkCredential()
-. {Invoke-WebRequest -proxy <proxy URL> -ProxyCredential $proxyCredential -useb aka.ms/iotedge-win} | Invoke-Expression; `
-Deploy-IoTEdge -InvokeWebRequestParameters @{ '-Proxy' = '<proxy URL>'; '-ProxyCredential' = $proxyCredential }
-```
-
-For more information about proxy parameters, see [Invoke-WebRequest](/powershell/module/microsoft.powershell.utility/invoke-webrequest).
-
 ## Configure IoT Edge and Moby
 
 IoT Edge uses two daemons running on the IoT Edge device. The Moby daemon pulls container images from container registries. The IoT Edge daemon communicates with IoT Hub.
@@ -113,8 +85,6 @@ Select the article that applies to your IoT Edge device operating system:
 
 * [Configure Docker daemon on Linux](https://docs.docker.com/config/daemon/systemd/#httphttps-proxy)
     On Linux devices, the Moby daemon is still called Docker.
-* [Configure Docker daemon on Windows](/virtualization/windowscontainers/manage-docker/configure-docker-daemon#proxy-configuration)
-    The Moby daemon on Windows devices is called iotedge-moby. The names are different because it's possible to run both Docker Desktop and Moby in parallel on a Windows device.
 
 ### IoT Edge daemon
 
@@ -179,20 +149,6 @@ Connect-EflowVm
 
 Follow the same steps as the Linux section of this article to configure the IoT Edge daemon.
 
-#### Windows using Windows containers
-
-Open a PowerShell window as an administrator and run the following command to edit the registry with the new environment variable. Replace **\<proxy url>** with your proxy server address and port.
-
-```powershell
-reg add HKLM\SYSTEM\CurrentControlSet\Services\iotedge /v Environment /t REG_MULTI_SZ /d https_proxy=<proxy URL>
-```
-
-Restart IoT Edge for the changes to take effect.
-
-```powershell
-Restart-Service iotedge
-```
-
 ## Configure the IoT Edge agent
 
 The IoT Edge agent is the first module to start on any IoT Edge device. This module starts for the first time based on information in the IoT Edge config file. The IoT Edge agent then connects to IoT Hub to retrieve deployment manifests. The manifest declares which other modules the device should deploy.