Merge pull request #278664 from ElazarK/WI264281-MDE-connectivity

MDE network connection requirements

Author: prmerger-automator[bot]

articles/defender-for-cloud/plan-defender-for-servers-agents.md

@@ -1,11 +1,13 @@
 ---
 title: Plan Defender for Servers agents and extensions deployment
 description: Plan for agent deployment to protect Azure, AWS, GCP, and on-premises servers with Microsoft Defender for Servers.
-ms.topic: conceptual
+ms.topic: concept-article
 ms.author: dacurwin
 author: dcurwin
-ms.date: 03/12/2024
+ms.date: 06/25/2024
+#customer intent: As a reader, I want to understand how to plan the deployment of Defender for Servers agents and extensions.
 ---
+
 # Plan agents, extensions, and Azure Arc for Defender for Servers
 
 This article helps you plan your agents, extensions, and Azure Arc resources for your Microsoft Defender for Servers deployment.
@@ -100,6 +102,8 @@ When you enable Defender for Servers, Defender for Cloud automatically deploys a
 - Machines must meet [minimum requirements](/microsoft-365/security/defender-endpoint/minimum-requirements).
 - Some Windows Server versions have [specific requirements](/microsoft-365/security/defender-endpoint/configure-server-endpoints).
 
+Most Defender for Endpoint services can be reached through `*.endpoint.security.microsoft.com` or through the Defender for Endpoint service tags. Make sure you are [connected to the Defender for Endpoint service and know the requirements for automatic updates and other features.](/defender-endpoint/configure-environment).
+
 ## Verify operating system support
 
 Before you deploy Defender for Servers, verify operating system support for agents and extensions: