Merge pull request #8034 from MicrosoftDocs/main

Publish 07/18/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/configmgr/protect/deploy-use/defender-advanced-threat-protection.md

@@ -2,7 +2,7 @@
 title: Microsoft Defender for Endpoint
 titleSuffix: Configuration Manager
 description: Learn how to manage and monitor Microsoft Defender for Endpoint, a new service that helps enterprises respond to advanced attacks.
-ms.date: 12/02/2021
+ms.date: 07/18/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-protect
 ms.topic: conceptual
@@ -29,7 +29,7 @@ Microsoft Defender for Endpoint's cloud-based portal is [Microsoft Defender Secu
 ### <a name="bkmk_os"></a> Supported client operating systems
 
 <!--5229962-->
-You can onboard the following operating systems:
+You can onboard the following operating systems using Configuration Manager:
 
 - Windows 8.1
 - Windows 10, version  1709 or later
@@ -40,6 +40,9 @@ You can onboard the following operating systems:
 - Windows Server 2019
 - Windows Server 2022<!-- 10200029 -->
 
+> [!IMPORTANT]
+> Operating systems that have reached the end of their [product lifecycle](/lifecycle/faq/general-lifecycle) aren't typically supported for onboarding unless they have been enrolled into the [Extended Security Updates (ESU program)](/lifecycle/faq/extended-security-updates). For more information about supported operating systems and capabilities with Microsoft Defender for Endpoint, see [Minimum requirements for Microsoft Defender for Endpoint](/microsoft-365/security/defender-endpoint/minimum-requirements#supported-windows-versions). <!-- MAX 6198973-->
+
 ## About onboarding to Microsoft Defender for Endpoint with Configuration Manager
 
 Different operating systems have different needs for onboarding to Microsoft Defender for Endpoint. Windows 8.1 and other down-level operating system devices need the **Workspace key** and **Workspace ID** to onboard. Up-level devices, such as Windows Server version 1803, need the onboarding configuration file. Configuration Manager also installs the Microsoft Monitoring Agent (MMA) when needed by onboarded devices but it doesn't update the agent automatically.

memdocs/configmgr/tenant-attach/atp-onboard.md

@@ -22,7 +22,7 @@ Microsoft Endpoint Manager is an integrated solution for managing all of your de
 
 [!INCLUDE [Prerequisites for Configuration Manager tenant attached devices](./includes/configmgr-endpoint-security-prerequisties.md)]
 - [Microsoft Intune and Microsoft Defender for Endpoint integration enabled](../../intune/protect/advanced-threat-protection-configure.md#enable-microsoft-defender-for-endpoint-in-intune)
-- Client onboarded to [Microsoft Defender for Endpoint](/windows/security/threat-protection/microsoft-defender-atp/minimum-requirements#licensing-requirements).<!--Adding MDE License Requirement-->
+- Client which meets the minimum requirements for, and is onboarded to [Microsoft Defender for Endpoint](/windows/security/threat-protection/microsoft-defender-atp/minimum-requirements#licensing-requirements).<!--Adding MDE License Requirement & MAX 6198973-->
 
 ## <a name="bkmk_onboard"></a> Create Microsoft Defender for Endpoint policies