Merge pull request #293169 from PatAltimore/patricka-eflow-nics

Fix EFLOW NIC link

Author: prmerger-automator[bot]

articles/iot-edge/iot-edge-for-linux-on-windows-networking.md

@@ -8,7 +8,7 @@ ms.service: azure-iot-edge
 ms.custom: linux-related-content
 services: iot-edge
 ms.topic: conceptual
-ms.date: 06/04/2024
+ms.date: 01/16/2025
 ms.author: patricka
 ---
 
@@ -96,7 +96,7 @@ There are many network virtual appliances and scenarios that require multiple NI
 
 For example, there are numerous of industrial IoT scenarios that require connecting the EFLOW virtual machine to a demilitarized zone (DMZ), and to the offline network where all the OPC UA compliant devices are connected. This is just one of the multiple scenarios that can be supported by attaching multiple NICs to the EFLOW VM. 
 
-For more information about multiple NICs, see [Multiple NICs support](https://github.com/Azure/iotedge-eflow/wiki/Multiple-NICs).
+For more information on adding NICs, see [PowerShell functions for IoT Edge for Linux on Windows](reference-iot-edge-for-linux-on-windows-functions.md).
 
 >[!WARNING]
 >When using EFLOW multiple NICs feature, you may want to set up the different routes priorities. By default, EFLOW will create one default route per *ehtX* interface assigned to the VM and assign a random priority. If all interfaces are connected to the internet, random priorities may not be a problem. However, if one of the NICs is connected to an offline network, you may want to prioritize the online NIC over the offline NIC to get the EFLOW VM connected to the internet. For more information about custom routing, see [EFLOW routing](https://github.com/Azure/iotedge-eflow/tree/main/samples/networking/routing).