Update Onboard-Windows-10-multi-session-device.md

windows/security/threat-protection/microsoft-defender-antivirus/Onboard-Windows-10-multi-session-device.md

@@ -27,9 +27,9 @@ Applies to:
 > [!WARNING]
 > Microsoft Defender ATP support for Windows Virtual Desktop multi-user scenarios is currently in Preview and limited up to 25 concurrent sessions per host/VM. However, single session scenarios on Windows Virtual Desktop are fully supported.
 
-Microsoft Defender for Endpoint supports monitoring both VDI as well as Windows Virtual Desktop sessions. Depending on the needs of your organization, you might need to implement VDI or Windows Virtual Desktop sessions to help your employees access corporate data and apps from an unmanaged device, remote location, or similar scenario. With Microsoft Defender for Endpoint, you can monitor these virtual machines for anomalous activity.
+Microsoft Defender for Endpoint supports monitoring both VDI as well as Windows Virtual Desktop sessions. Depending on your organization's needs, you might need to implement VDI or Windows Virtual Desktop sessions to help your employees access corporate data and apps from an unmanaged device, remote location, or similar scenario. With Microsoft Defender for Endpoint, you can monitor these virtual machines for anomalous activity.
 
- ##Before you begin
+ ## Before you begin
 Familiarize yourself with the [considerations for non-persistent VDI](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi#onboard-non-persistent-virtual-desktop-infrastructure-vdi-devices-1). While [Windows Virtual Desktop](https://docs.microsoft.com/azure/virtual-desktop/overview) does not provide non-persistence options, it does provide ways to use a golden Windows image that can be used to provision new hosts and redeploy machines. This increases volatility in the environment and thus impacts what entries are created and maintained in the Microsoft Defender for Endpoint portal, potentially reducing visibility for your security analysts.
 
 > [!NOTE]
@@ -44,23 +44,23 @@ Microsoft recommends adding the Microsoft Defender for Endpoint onboarding scrip
 > [!NOTE]
 > The placement and configuration of the VDI onboarding startup script on the WVD golden image configures it as a startup script that runs when the WVD starts. It is NOT recommended to onboard the actual WVD golden image. Another consideration is the method used to run the script. It should run as early in the startup/provisioning process as possible to reduce the time between the machine being available to receive sessions and the device onboarding to the service. Below scenarios 1 & 2 take this into account.
 
-###Scenarios
+### Scenarios
 There are several ways to onboard a WVD host machine:
 
 Run the script in the golden image (or from a shared location) during startup.
 Use a management tool to run the script.
 
-####*Scenario 1: Using local group policy*
+#### *Scenario 1: Using local group policy*
 This scenario requires placing the script in a golden image and uses local group policy to run early in the boot process.
 
 Use the instructions [https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi#onboard-non-persistent-virtual-desktop-infrastructure-vdi-devices-1 ](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi#onboard-non-persistent-virtual-desktop-infrastructure-vdi-devices-1)
 
 Follow the instructions for a single entry for each device.
 
-####*Scenario 2: Using domain group policy*
+#### *Scenario 2: Using domain group policy*
 This scenario uses a centrally located script and runs it using a domain-based group policy. You can also place the script in the golden image and run it in the same way.
 
-**Download the WindowsDefenderATPOnboardingPackage.zip file from the Windows Defender Security Center **
+**Download the WindowsDefenderATPOnboardingPackage.zip file from the Windows Defender Security Center**
 1. Open the VDI configuration package .zip file (WindowsDefenderATPOnboardingPackage.zip)  
 - In the Microsoft Defender Security Center navigation pane, select **Settings** > **Onboarding**. 
 - Select Windows 10 as the operating system. 
@@ -84,7 +84,7 @@ Add Arguments (optional) = -ExecutionPolicy Bypass -command "& \\Path\To\Onboard
 
 Click **OK** and close any open GPMC windows.
 
-####*Scenario 3: Onboarding using management tools*
+#### *Scenario 3: Onboarding using management tools*
 
 If you plan to manage your machines using a management tool, you can onboard devices with Microsoft Endpoint Configuration Manager.
 
@@ -96,12 +96,12 @@ For more information, see: [https://docs.microsoft.com/en-us/windows/security/th
 > [!TIP]
 > After onboarding the device, you can choose to run a detection test to verify that the device is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Microsoft Defender for Endpoint device](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/run-detection-test). 
 
-####Tagging your machines when building your golden image 
+#### Tagging your machines when building your golden image 
 
 As part of your onboarding, you may want to consider setting a machine tag to be able to differentiate WVD machines more easily in the Microsoft Security Center.  
 [https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/machine-tags#add-device-tags-by-setting-a-registry-key-value](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/machine-tags#add-device-tags-by-setting-a-registry-key-value)  
 
-####Other recommended configuration settings 
+#### Other recommended configuration settings 
 
 When building your golden image, you may want to configure initial protection settings as well. For more information, see [https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-gp#other-recommended-configuration-settings](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-gp#other-recommended-configuration-settings). 
 
@@ -124,6 +124,6 @@ Exclude Processes:
 %ProgramFiles%\FSLogix\Apps\frxccds.exe 
 %ProgramFiles%\FSLogix\Apps\frxsvc.exe 
 
-####Licensing requirements 
+#### Licensing requirements 
 
 Windows 10 Multi-session is a client OS. Licensing requirements for Microsoft Defender Advanced Threat Protection can be found at: [https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/minimum-requirements#licensing-requirements ](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/minimum-requirements#licensing-requirements)