Merge pull request #277209 from PatAltimore/patricka-freshness

prmerger-automator[bot] · web-flow · commit 83a38eaf10ce · 2024-06-05T15:48:11.000Z
Freshness
diff --git a/articles/iot-edge/how-to-share-windows-folder-to-vm.md b/articles/iot-edge/how-to-share-windows-folder-to-vm.md
@@ -1,13 +1,13 @@
 ---
-title: Share a Windows folder with Azure IoT Edge for Linux on Windows | Microsoft Docs
-description: How to share a Windows folder with the Azure IoT Edge for Linux on Windows virtual machine
+title: Share Windows folder with Azure IoT Edge for Linux on Windows
+description: How to share a Windows folders and files with the Azure IoT Edge for Linux on Windows virtual machine.
 author: PatAltimore
 ms.reviewer: fcabrera
 ms.service: iot-edge
 ms.custom: linux-related-content
 services: iot-edge
-ms.topic: conceptual
-ms.date: 11/1/2022
+ms.topic: how-to
+ms.date: 06/04/2024
 ms.author: patricka
 ---
 
@@ -22,22 +22,22 @@ This article shows you how to enable the folder sharing between the Windows host
 ## Prerequisites
 - Azure IoT Edge for Linux on Windows 1.4.4 LTS update or higher. For more information about EFLOW release notes, see [EFLOW Releases](https://aka.ms/AzEFLOW-Releases).
 - A machine with an x64/x86 processor.
-- Windows 10/11 (21H2) or higher with [November 2022](https://support.microsoft.com/en-us/topic/november-15-2022-kb5020030-os-builds-19042-2311-19043-2311-19044-2311-and-19045-2311-preview-237a9048-f853-4e29-a3a2-62efdbea95e2) update applied.
+- Windows 10/11 (21H2) or higher with [November 2022](https://support.microsoft.com/topic/november-15-2022-kb5020030-os-builds-19042-2311-19043-2311-19044-2311-and-19045-2311-preview-237a9048-f853-4e29-a3a2-62efdbea95e2) update applied.
 
-If you don't have an EFLOW device ready, you should create one before continuing with this guide. Follow the steps in [Create and provision an IoT Edge for Linux on Windows device using symmetric keys](how-to-provision-single-device-linux-on-windows-symmetric.md) to install, deploy and provision EFLOW.
+If you don't have an EFLOW device ready, you should create one before continuing with this guide. Follow the steps in [Create and provision an IoT Edge for Linux on Windows device using symmetric keys](how-to-provision-single-device-linux-on-windows-symmetric.md) to install, deploy, and provision EFLOW.
 
 ## How it works?
 
 The Azure IoT Edge for Linux on Windows file and folder sharing mechanism is implemented using [virtiofs](https://virtio-fs.gitlab.io/) technology. *Virtiofs* is a shared file system that lets virtual machines access a directory tree on the host OS. Unlike other approaches, it's designed to offer local file system semantics and performance. *Virtiofs* isn't a network file system repurposed for virtualization. It's designed to take advantage of the locality of virtual machines and the hypervisor. It takes advantage of the virtual machine's co-location with the hypervisor to avoid overhead associated with network file systems.
 
 :::image type="content" source="media/how-to-share-windows-folder-to-vm/folder-sharing-virtiofs.png" alt-text="Screenshot of a Windows folder shared with the EFLOW virtual machine using Virtio-FS technology.":::
 
-Only Windows folders can be shared to the EFLOW Linux VM and not the other way. Also, for security reasons, when setting the folder sharing mechanism, the user must provide a _root folder_ and all the shared folders must be under that _root folder_. 
+Only Windows folders can be shared to the EFLOW Linux VM and not the other way. Also, for security reasons, when setting the folder sharing mechanism, the user must provide a *root folder* and all the shared folders must be under that *root folder*. 
 
 Before starting with the adding and removing share mechanisms, let's define four concepts:
 
 - **Root folder**: Windows folder that is the root path containing subfolders to be shared to the EFLOW VM. The root folder isn't shared to the EFLOW VM. Only the subfolders under the root folder are shared to the EFLOW VM.
-- **Shared folder**: A Windows folder that's under the _root folder_ and is shared with the EFLOW VM. All the content inside this folder is shared with the EFLOW VM.
+- **Shared folder**: A Windows folder that's under the *root folder* and is shared with the EFLOW VM. All the content inside this folder is shared with the EFLOW VM.
 - **Mounting point**: Path inside the EFLOW VM where the Windows folder content is placed. 
 - **Mounting option**: *Read-only* or *read and write* access. Controls the file access of the mounted folder inside the EFLOW VM. 
 
@@ -49,25 +49,25 @@ The following steps provide example EFLOW PowerShell commands to share one or mo
 
 1. Start by creating a new root shared folder. Go to **File Explorer** and choose a location for the *root folder* and create the folder. 
 
-   For example, create a *root folder* under _C:\Shared_ named **EFLOW-Shared**.
+   For example, create a *root folder* under *C:\Shared* named **EFLOW-Shared**.
 
-   :::image type="content" source="media/how-to-share-windows-folder-to-vm/root-folder.png" alt-text="Screenshot of the Windows root folder.":::
+   :::image type="content" source="media/how-to-share-windows-folder-to-vm/root-folder.png" alt-text="Screenshot of the C:\Shared folder that includes EFLOW-Shared folder.":::
 
 1. Create one or more *shared folders* to be shared with the EFLOW virtual machine. Shared folders should be created under the *root folder* from the previous step. 
 
    For example, create two folders one named **Read-Access** and one named **Read-Write-Access**. 
 
-   :::image type="content" source="media/how-to-share-windows-folder-to-vm/shared-folders.png" alt-text="Screenshot of Windows shared folders.":::
+   :::image type="content" source="media/how-to-share-windows-folder-to-vm/shared-folders.png" alt-text="Screenshot of Windows shared folders Read-Access and Read-Write-Access.":::
 
-1. Within the _Read-Access_ shared folder, create a sample file that we'll later read inside the EFLOW virtual machine.
+1. Within the *Read-Access* shared folder, create a sample file that we'll later read inside the EFLOW virtual machine.
 
-    For example, using a text editor, create a file named _Hello-World.txt_ within the _Read-Access_ folder and save some text in the file.
+    For example, using a text editor, create a file named *Hello-World.txt* within the *Read-Access* folder and save some text in the file.
 
 1. Using a text editor, create the shared folder configuration file. This file contains the information about the folders to be shared with the EFLOW VM including the mounting points and the mounting options. For more information about the JSON configuration file, see [PowerShell functions for IoT Edge for Linux on Windows](reference-iot-edge-for-linux-on-windows-functions.md).
 
     For example, using the previous scenario, we'll share the two *shared folders* we created under the *root folder*. 
-    - _Read-Access_ shared folder will be mounted in the EFLOW virtual machine under the path _/tmp/host-read-access_ with *read-only* access.
-    - _Read-Write-Access_ shared folder will be mounted in the EFLOW virtual machine under the path _/tmp/host-read-write-access_ with *read and write* access.
+    - *Read-Access* shared folder is mounted in the EFLOW virtual machine under the path */tmp/host-read-access* with *read-only* access.
+    - *Read-Write-Access* shared folder is mounted in the EFLOW virtual machine under the path */tmp/host-read-write-access* with *read and write* access.
 
     Create the JSON configuration file named **sharedFolders.json** within the *root folder* *EFLOW-Shared* with the following contents:
 
@@ -91,9 +91,9 @@ The following steps provide example EFLOW PowerShell commands to share one or mo
     ]
     ```
 
-1. Open an elevated _PowerShell_ session by starting with **Run as Administrator**.
+1. Open an elevated *PowerShell* session by starting with **Run as Administrator**.
 
-1. Create the shared folder assignation using the configuration file (_sharedFolders.json_) previously created.
+1. Create the shared folder assignation using the configuration file (*sharedFolders.json*) previously created.
 
     ```powershell
     Add-EflowVmSharedFolder -sharedFoldersJsonPath "C:\Shared\EFLOW-Shared\sharedFolders.json"
@@ -104,7 +104,7 @@ The following steps provide example EFLOW PowerShell commands to share one or mo
     Connect-EflowVm
     ``` 
 
-1. Go to the _Read-Access_ shared folder (mounted under _/tmp/host-read-access_) and check the content of the _Hello-World.txt_ file.
+1. Go to the *Read-Access* shared folder (mounted under */tmp/host-read-access*) and check the content of the *Hello-World.txt* file.
     
     >[!NOTE]
     >By default, all shared folders are shared under *root* ownership. To access the folder, you should log in as root using `sudo su` or change the folder ownership to *iotedge-user* using `chown` command.
@@ -114,15 +114,15 @@ The following steps provide example EFLOW PowerShell commands to share one or mo
     cd /tmp/host-read-access
     cat Hello-World.txt
     ```
-If everything was successful, you should be able to see the contents of the _Hello-World.txt_ file within the EFLOW virtual machine. Verify write access by creating a file inside the _/tmp/host-read-write-access_ and then checking the contents of the new created file inside the _Read-Write-Access_ Windows host folder. 
+If everything was successful, you should be able to see the contents of the *Hello-World.txt* file within the EFLOW virtual machine. Verify write access by creating a file inside the */tmp/host-read-write-access* and then checking the contents of the new created file inside the *Read-Write-Access* Windows host folder. 
 
 ## Check shared folders
 The following steps provide example EFLOW PowerShell commands to check the Windows shared folders and options (access permissions and mounting point) with the EFLOW virtual machine.
 
 1. Open an elevated PowerShell session by starting with **Run as Administrator**.
 
 1. List the information of the Windows shared folders under the *root folder*.
-    For example, using the scenario in the previous section, we can list the information of both _Read-Access_ and _Read-Write-Access_ shared folders. 
+    For example, using the scenario in the previous section, we can list the information of both *Read-Access* and *Read-Write-Access* shared folders. 
     ```powershell
     Get-EflowVmSharedFolder -sharedfolderRoot "C:\Shared\EFLOW-Shared" -hostFolderPath @("Read-Access", "Read-Write-Access")
     ``` 
@@ -135,7 +135,7 @@ The following steps provide example EFLOW PowerShell commands to stop sharing a
 
 1. Open an elevated PowerShell session by starting with **Run as Administrator**.
 
-1. Stop sharing the folder named _Read-Access_ under the **Root folder** with the EFLOW virtual machine.
+1. Stop sharing the folder named *Read-Access* under the **Root folder** with the EFLOW virtual machine.
     ```powershell
     Remove-EflowVmSharedFolder -sharedfolderRoot "C:\Shared\EFLOW-Shared" -hostFolderPath "Read-Access"
     ``` 
diff --git a/articles/iot-edge/iot-edge-as-gateway.md b/articles/iot-edge/iot-edge-as-gateway.md
@@ -1,10 +1,10 @@
 ---
-title: Gateways for downstream devices - Azure IoT Edge | Microsoft Docs 
-description: Use Azure IoT Edge to create a transparent, opaque, or proxy gateway device that sends data from multiple downstream devices to the cloud or processes it locally.
+title: Gateways for downstream devices - Azure IoT Edge 
+description: Use Azure IoT Edge to create a transparent, opaque, or proxy gateway device that sends data from multiple downstream devices to the cloud or processes locally.
 author: PatAltimore
 
 ms.author: patricka
-ms.date: 06/27/2022
+ms.date: 06/04/2024
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
@@ -65,7 +65,7 @@ IoT Edge devices can be both parents and children in transparent gateway relatio
 
 #### Gateway discovery
 
-A child device needs to be able to find its parent device on the local network. Configure gateway devices with a **hostname**, either a fully qualified domain name (FQDN) or an IP address, that its child devices will use to locate it.
+A child device needs to be able to find its parent device on the local network. Configure gateway devices with a **hostname**, either a fully qualified domain name (FQDN) or an IP address, that its child devices use to locate it.
 
 On downstream IoT devices, use the **gatewayHostname** parameter in the connection string to point to the parent device.
 
diff --git a/articles/iot-edge/iot-edge-for-linux-on-windows-benefits.md b/articles/iot-edge/iot-edge-for-linux-on-windows-benefits.md
@@ -1,9 +1,9 @@
 ---
-title: Why use Azure IoT Edge for Linux on Windows? | Microsoft Docs 
-description: Benefits - Azure IoT Edge for Linux on Windows 
+title: Why use Azure IoT Edge for Linux on Windows?
+description: Benefits for using Azure IoT Edge for Linux on Windows (EFLOW) to deploy production Linux-based cloud-native workloads on Windows devices.
 author: PatAltimore
-ms.author: fcabrera
-ms.date: 04/15/2022
+ms.author: patricka
+ms.date: 06/04/2024
 ms.topic: conceptual
 ms.service: iot-edge
 ms.custom: linux-related-content
diff --git a/articles/iot-edge/iot-edge-for-linux-on-windows-networking.md b/articles/iot-edge/iot-edge-for-linux-on-windows-networking.md
@@ -1,16 +1,15 @@
 ---
 title: Azure IoT Edge for Linux on Windows networking
-description: Overview of Azure IoT Edge for Linux on Windows networking
+description: Overview of Azure IoT Edge for Linux on Windows networking between the Windows host OS and the IoT Edge for Linux on Windows (EFLOW) virtual machine.
 author: PatAltimore
 
-# this is the PM responsible
 ms.reviewer: fcabrera
 ms.service: iot-edge
 ms.custom: linux-related-content
 services: iot-edge
 ms.topic: conceptual
-ms.date: 11/15/2022
-ms.author: fcabrera
+ms.date: 06/04/2024
+ms.author: patricka
 ---
 
 # IoT Edge for Linux on Windows networking
@@ -22,7 +21,7 @@ ms.author: fcabrera
 ## Networking
 To establish a communication channel between the Windows host OS and the EFLOW virtual machine, we use Hyper-V networking stack. For more information about Hyper-V networking, see [Hyper-V networking basics](/windows-server/virtualization/hyper-v/plan/plan-hyper-v-networking-in-windows-server#hyper-v-networking-basics). Basic networking in EFLOW is simple; it uses two parts, a virtual switch and a virtual network. 
 
-The easiest way to establish basic networking on Windows client SKUs is by using the [**default switch**](https://techcommunity.microsoft.com/t5/virtualization/hyper-v-virtual-machine-gallery-and-networking-improvements/ba-p/382375) already created by the Hyper-V feature. During EFLOW deployment, if no specific virtual switch is specified using the `-vSwitchName` and `-vSwitchType` flags, the virtual machine will be created using the **default switch**.
+The easiest way to establish basic networking on Windows client SKUs is by using the [**default switch**](https://techcommunity.microsoft.com/t5/virtualization/hyper-v-virtual-machine-gallery-and-networking-improvements/ba-p/382375) already created by the Hyper-V feature. During EFLOW deployment, if no specific virtual switch is specified using the `-vSwitchName` and `-vSwitchType` flags, the virtual machine is created using the **default switch**.
 
 On Windows Server SKUs devices, networking is a bit more complicated as there's no **default switch** available. However, there's a comprehensive guide on [Azure IoT Edge for Linux on Windows virtual switch creation](./how-to-create-virtual-switch.md). 
 
@@ -82,7 +81,7 @@ By default, the EFLOW VM DNS configuration file contains the local stub *127.0.0
 
 It's possible to configure the EFLOW virtual machine to use a specific DNS server, or list of servers. To do so, you can use the `Set-EflowVmDnsServers` PowerShell cmdlet. For more information about DNS configuration, see [PowerShell functions for IoT Edge for Linux on Windows](./reference-iot-edge-for-linux-on-windows-functions.md#set-eflowvmdnsservers).
 
-To check the DNS servers assigned to the EFLOW VM, from inside the EFLOW VM, use the command: `resolvectl status`. The command's output will show a list of the DNS servers configured for each interface. In particular, it's important to check the *eth0* interface status, which will be the default interface for the EFLOW VM communication. Also, make sure to check the IP addresses of the **Current DNS Server**s and **DNS Servers** fields of the list. If there's no IP address, or the IP address isn't a valid DNS server IP address, then the DNS service won't work.
+To check the DNS servers assigned to the EFLOW VM, from inside the EFLOW VM, use the command: `resolvectl status`. The command's output shows a list of the DNS servers configured for each interface. In particular, it's important to check the *eth0* interface status, which is the default interface for the EFLOW VM communication. Also, make sure to check the IP addresses of the **Current DNS Server**s and **DNS Servers** fields of the list. If there's no IP address, or the IP address isn't a valid DNS server IP address, then the DNS service won't work.
 
 ![Screenshot of console showing sample output from resolvectl command.](./media/iot-edge-for-linux-on-windows-networking/resolvctl-status.png)
 
@@ -95,14 +94,14 @@ Get-EflowVmAddr
 
 
 ### Multiple Network Interface Cards (NICs)
-There are many network virtual appliances and scenarios that require multiple NICs. The EFLOW virtual machine supports attaching multiple NICs. With multiple NICs you can better manage your network traffic. You can also isolate traffic between the frontend NIC and backend NICs, or separating data plane traffic from the management plane communication. 
+There are many network virtual appliances and scenarios that require multiple NICs. The EFLOW virtual machine supports attaching multiple NICs. With multiple NICs, you can better manage your network traffic. You can also isolate traffic between the frontend NIC and backend NICs, or separating data plane traffic from the management plane communication. 
 
 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).
 
 >[!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).
+>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).
 
 ## Next steps
 
diff --git a/articles/iot-edge/iot-edge-for-linux-on-windows-security.md b/articles/iot-edge/iot-edge-for-linux-on-windows-security.md
