Merge pull request #7806 from MicrosoftDocs/main

Publish 06/13/2022, 10:30 AM

Author: v-dihans

memdocs/intune/protect/antivirus-microsoft-defender-settings-windows.md

@@ -30,16 +30,16 @@ ms.reviewer: laarrizz
 
 # Settings for Microsoft Defender Antivirus policy in Microsoft Intune for Windows devices
 
-> [!NOTE]  
-> This article details the settings in the  Microsoft Defender Antivirus and Microsoft Defender Antivirus Exclusions profiles for the *Windows 10 and later* platform for endpoint security Antivirus policy. Beginning on April 5, 2022, the *Windows 10 and later* platform was replaced by the *Windows 10, Windows 11, and Windows Server* platform. Although you can no longer create new instances of the original profile, you can continue to edit and use your existing profiles. The settings details in this article apply to those deprecated profiles. 
-
 View details about the [endpoint security](../protect/endpoint-security-policy.md) antivirus policy settings you can configure for the Microsoft Defender Antivirus profile for Windows 10 and later in Microsoft Intune.  
 
-These settings are available in the following profiles:
-
-- Microsoft Defender Antivirus
+> [!NOTE]  
+> This article details the settings you can find in Microsoft Defender Antivirus and Microsoft Defender Antivirus Exclusions profiles created before April 5, 2022, for the *Windows 10 and later* platform for endpoint security Antivirus policy. On April 5, 2022, the *Windows 10 and later* platform was replaced by the *Windows 10, Windows 11, and Windows Server* platform. Profiles created after that date use a new settings format as found in the Settings Catalog. With this change you can no longer create new versions of the old profile and they are no longer being developed. Although you can no longer create new instances of the older profile, you can continue to edit and use instances of it that you previously created.
+>
+> For profiles that use the new settings format, Intune no longer maintains a list of each setting by name. Instead, the name of each setting, its configuration options, and its explanatory text you see in the Microsoft Endpoint Manager admin center are taken directly from the settings authoritative content. That content can provide more information about the use of the setting in its proper context. When viewing a settings information text, you can use its *Learn more* link to open that content.
+>
+> The following settings details for Windows profiles apply to those deprecated profiles.
 
-**Settings**:
+## Cloud protection
 
 - **Turn on cloud-delivered protection**  
   CSP: [AllowCloudProtection](/windows/client-management/mdm/policy-csp-defender#defender-allowcloudprotection)
@@ -66,7 +66,7 @@ These settings are available in the following profiles:
 
 ## Microsoft Defender Antivirus Exclusions
 
-The following setting is only available in the Microsoft Defender Antivirus profile:
+The following settings are available in the Microsoft Defender Antivirus profile:
 
 - **Defender local admin merge**  
   CSP: [Configuration/DisableLocalAdminMerge](/windows/client-management/mdm/defender-csp)

memdocs/intune/protect/endpoint-security-asr-profile-settings.md

@@ -61,7 +61,7 @@ Supported platforms and profiles:
 - **Turn on Application Guard**  
   CSP: [AllowWindowsDefenderApplicationGuard](/windows/client-management/mdm/windowsdefenderapplicationguard-csp#allowwindowsdefenderapplicationguard)
 
-  - **Not configured** (*default*) - Microsoft Defender Application Guard is not configured for Microsoft Edge or isolated Windows environments.
+  - **Not configured** (*default*) - Microsoft Defender Application Guard isn't configured for Microsoft Edge or isolated Windows environments.
   - **Enabled for Edge** - Application Guard opens unapproved sites in a Hyper-V virtualized browsing container.
   - **Enabled for isolated Windows environments** - Application Guard is turned on for any applications enabled for App Guard within Windows.
   - **Enabled for Edge AND isolated Windows environments** - Application Guard is configured for both scenarios.
@@ -147,7 +147,7 @@ Supported platforms and profiles:
 
   To add thumbprints one at a time, select **Add**. You can use **Import** to specify a .CSV file that contains multiple thumbprint entries that are all added to the profile at the same time. When you use a .CSV file, each thumbprint must be separated by a comma. For example: `b4e72779a8a362c860c36a6461f31e3aa7e58c14,1b1d49f06d2a697a544a1059bd59a7b058cda924`
 
-  All entries that are listed in the profile are active. You do not need to select a checkbox for a thumbprint entry to make it active. Instead, use the checkboxes to help you manage the entries that have been added to the profile. For example, you can select the checkbox of one or more certificate thumbprint entries and then **Delete** those entries from the profile with a single action.
+  All entries that are listed in the profile are active. You don't need to select a checkbox for a thumbprint entry to make it active. Instead, use the checkboxes to help you manage the entries that have been added to the profile. For example, you can select the checkbox of one or more certificate thumbprint entries and then **Delete** those entries from the profile with a single action.
 
 - **Windows network isolation policy**  
 
@@ -212,7 +212,9 @@ Supported platforms and profiles:
 #### Attack Surface Reduction Rules
 
 > [!NOTE]  
-> This section details the settings in Attack Surface Reduction Rules profiles created before April 5, 2022. Profiles created after that date use a new settings format as found in the Settings Catalog. Although you can no longer create new instances of the original profile, you can continue to edit and use your existing profiles.  
+> This section details the settings in Attack Surface Reduction Rules profiles created before April 5, 2022. Profiles created after that date use a new settings format as found in the Settings Catalog. With this change you can no longer create new versions of the old profile and they are no longer being developed. Although you can no longer create new instances of the older profile, you can continue to edit and use instances of it that you previously created. 
+>
+> For profiles that use the new settings format, Intune no longer maintains a list of each setting by name. Instead, the name of each setting, its configuration options, and its explanatory text you see in the Microsoft Endpoint Manager admin center are taken directly from the settings authoritative content. That content can provide more information about the use of the setting in its proper context. When viewing a settings information text, you can use its *Learn more* link to open that content.
 
 - **Block persistence through WMI event subscription**  
   [Reduce attack surfaces with attack surface reduction rules](/windows/security/threat-protection/microsoft-defender-atp/attack-surface-reduction)
@@ -221,7 +223,7 @@ Supported platforms and profiles:
 
   This rule prevents malware from abusing WMI to attain persistence on a device. Fileless threats employ various tactics to stay hidden, to avoid being seen in the file system, and to gain periodic execution control. Some threats can abuse the WMI repository and event model to stay hidden.
 
-  - **Not configured** (default) – The setting returns to the Windows default, which is off and persistence is not blocked.
+  - **Not configured** (default) – The setting returns to the Windows default, which is off and persistence isn't blocked.
   - **Block** – Persistence through WMI is blocked.
   - **Audit** – Evaluate how this rule affects your organization if it's enabled (set to Block).
   - **Disable** - Turn this rule off. Persistence is not blocked.
@@ -395,6 +397,9 @@ Supported platforms and profiles:
 
 > [!NOTE]  
 > This section details the settings found in Device control profiles created before May 23, 2022. Profiles created after that date use a new settings format as found in the Settings Catalog. Although you can no longer create new instances of the original profile, you can continue to edit and use your existing profiles.  
+>
+> For profiles that use the new settings format, Intune no longer maintains a list of each setting by name. Instead, the name of each setting, its configuration options, and its explanatory text you see in the Microsoft Endpoint Manager admin center are taken directly from the settings authoritative content. That content can provide more information about the use of the setting in its proper context. When viewing a settings information text, you can use its *Learn more* link to open that content.
+
 
 - **Allow hardware device installation by device identifiers**  
   - **Not configured** *(default)*
@@ -549,8 +554,10 @@ Supported platforms and profiles:
 
 #### Exploit protection
 
-  > [!NOTE]  
-  > This  section details the settings you can find in Exploit protection profiles created before April 5, 2022. Profiles created after that date use a new settings format as found in the Settings Catalog. Although you can no longer create new instances of the original profile, you can continue to edit and use your existing profiles.
+> [!NOTE]  
+> This section details the settings you can find in Exploit protection profiles created before April 5, 2022. Profiles created after that date use a new settings format as found in the Settings Catalog. With this change you can no longer create new versions of the old profile and they are no longer being developed. Although you can no longer create new instances of the older profile, you can continue to edit and use instances of it that you previously created.
+>
+> For profiles that use the new settings format, Intune no longer maintains a list of each setting by name. Instead, the name of each setting, its configuration options, and its explanatory text you see in the Microsoft Endpoint Manager admin center are taken directly from the settings authoritative content. That content can provide more information about the use of the setting in its proper context. When viewing a settings information text, you can use its *Learn more* link to open that content.
 
 - **Upload XML**  
   CSP: [ExploitProtectionSettings](/windows/client-management/mdm/policy-csp-exploitguard#exploitguard-exploitprotectionsettings)

memdocs/intune/protect/endpoint-security-firewall-profile-settings.md

@@ -29,9 +29,6 @@ ms.reviewer: aanavath
 ---
 # Firewall policy settings for endpoint security in Intune
 
-> [!NOTE]  
-> Beginning on April 5, 2022, the *Windows 10 and later* platform and profiles for Windows devices were replaced by the *Windows 10, Windows 11, and Windows Server* platform and new instances of those same profiles. Although you can no longer create new instances of the original profile, you can continue to edit and use your existing profiles. The settings details for Windows profiles in this article apply to those deprecated profiles.
-
 View the settings you can configure in profiles for *Firewall* policy in the endpoint security node of Intune as part of an [Endpoint security policy](../protect/endpoint-security-policy.md).
 
 Applies to:
@@ -40,6 +37,13 @@ Applies to:
 - Windows 10
 - Windows 11
 
+> [!NOTE]  
+> Beginning on April 5, 2022, the Firewall profiles for the  *Windows 10 and later* platform were replaced by the *Windows 10, Windows 11, and Windows Server* platform and new instances of those same profiles. Profiles created after that date use a new settings format as found in the Settings Catalog. With this change you can no longer create new versions of the old profile and they are no longer being developed. Although you can no longer create new instances of the older profile, you can continue to edit and use instances of it that you previously created.
+>
+> For profiles that use the new settings format, Intune no longer maintains a list of each setting by name. Instead, the name of each setting, its configuration options, and its explanatory text you see in the Microsoft Endpoint Manager admin center are taken directly from the settings authoritative content. That content can provide more information about the use of the setting in its proper context. When viewing a settings information text, you can use its *Learn more* link to open that content.
+>
+> The settings details for Windows profiles in this article apply to those deprecated profiles.
+
 Supported platforms and profiles:
 
 - **macOS**:

windows-365/enterprise/rdp-shortpath-public-networks.md

@@ -38,7 +38,7 @@ To use RDP Shortpath for public networks with Windows 365, you must meet these r
 
 - Session Host (Cloud PC)
   - UDP outbound to all public IP space (because, in most cases, it’s not possible to know the source IP address of the connecting PC).
-  - STUN server IP ranges on UDP port 347.
+  - STUN server IP ranges on UDP port 3478.
 - Client PC Network  
   - UDP outbound:  
     - To the public IP addresses assigned to NAT gateway or the Azure Firewall in an Azure Hosted Network Scenario.