Skip to content

Commit c51fb1e

Browse files
committed
Update onboard-downlevel.md
1 parent fcaf038 commit c51fb1e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

defender-endpoint/onboard-downlevel.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ ms.date: 12/18/2020
3939
4040
Defender for Endpoint extends support to include down-level operating systems, providing advanced attack detection and investigation capabilities on supported Windows versions.
4141

42-
To onboard down-level Windows client endpoints to Defender for Endpoint, you'll need to:
42+
To onboard down-level Windows client endpoints to Defender for Endpoint, you need to:
4343

4444
- [Configure and update System Center Endpoint Protection clients](#configure-and-update-system-center-endpoint-protection-clients)
4545
- [Install and configure Microsoft Monitoring Agent (MMA) to report sensor data](#install-and-configure-microsoft-monitoring-agent-mma)
@@ -50,7 +50,7 @@ For Windows Server 2008 R2 SP1, you have the option of [onboarding through Micro
5050
> Defender for Endpoint standalone server license is required, per node, in order to onboard a Windows server through Microsoft Monitoring Agent (Option 1). Alternatively, a Microsoft Defender for servers license is required, per node, in order to onboard a Windows server through Microsoft Defender for Cloud (Option 2), see [Supported features available in Microsoft Defender for Cloud](/azure/defender-for-cloud/supported-machines-endpoint-solutions-clouds-servers).
5151
5252
> [!TIP]
53-
> After onboarding the device, you can choose to run a detection test to verify that it is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Defender for Endpoint endpoint](run-detection-test.md).
53+
> After onboarding the device, you can choose to run a detection test to verify that it's properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Defender for Endpoint endpoint](run-detection-test.md).
5454
5555
## Configure and update System Center Endpoint Protection clients
5656

@@ -107,7 +107,7 @@ Review the following details to verify minimum system requirements:
107107
- [Configure the agent using a script](/azure/log-analytics/log-analytics-windows-agents#install-agent-using-dsc-in-azure-automation).
108108

109109
> [!NOTE]
110-
> If you are a [US Government customer](gov.md), under "Azure Cloud" you'll need to choose "Azure US Government" if using the setup wizard, or if using a command line or a script - set the "OPINSIGHTS_WORKSPACE_AZURE_CLOUD_TYPE" parameter to 1.
110+
> If you're a [US Government customer](gov.md), under "Azure Cloud", you need to choose "Azure US Government" if using the setup wizard, or if using a command line or a script - set the "OPINSIGHTS_WORKSPACE_AZURE_CLOUD_TYPE" parameter to 1.
111111
112112
4. If you're using a proxy to connect to the Internet see the Configure proxy and Internet connectivity settings section.
113113

@@ -121,7 +121,7 @@ If your servers need to use a proxy to communicate with Defender for Endpoint, u
121121

122122
- [Configure Windows to use a proxy server for all connections](configure-proxy-internet.md)
123123

124-
If a proxy or firewall is in use, please ensure that servers can access all of the Microsoft Defender for Endpoint service URLs directly and without SSL interception. For more information, see [enable access to Microsoft Defender for Endpoint service URLs](configure-environment.md#enable-access-to-microsoft-defender-for-endpoint-service-urls-in-the-proxy-server). Use of SSL interception will prevent the system from communicating with the Defender for Endpoint service.
124+
If a proxy or firewall is in use, ensure that servers can access all of the Microsoft Defender for Endpoint service URLs directly and without SSL interception. For more information, see [enable access to Microsoft Defender for Endpoint service URLs](configure-environment.md#enable-access-to-microsoft-defender-for-endpoint-service-urls-in-the-proxy-server). Use of SSL interception prevents the system from communicating with the Defender for Endpoint service.
125125

126126
Once completed, you should see onboarded Windows servers in the portal within an hour.
127127

@@ -133,7 +133,7 @@ Once completed, you should see onboarded Windows servers in the portal within an
133133

134134
3. Click **Onboard Servers in Microsoft Defender for Cloud**.
135135

136-
4. Follow the onboarding instructions in [Microsoft Defender for Endpoint with Microsoft Defender for Cloud](/azure/security-center/security-center-wdatp) and If you are using Azure ARC, follow the onboarding instructions in [Enabling the Microsoft Defender for Endpoint integration](/azure/security-center/security-center-wdatp#enabling-the-microsoft-defender-for-endpoint-integration).
136+
4. Follow the onboarding instructions in [Microsoft Defender for Endpoint with Microsoft Defender for Cloud](/azure/security-center/security-center-wdatp) and If you're using Azure ARC, follow the onboarding instructions in [Enabling the Microsoft Defender for Endpoint integration](/azure/security-center/security-center-wdatp#enabling-the-microsoft-defender-for-endpoint-integration).
137137

138138
After completing the onboarding steps, you'll need to [Configure and update System Center Endpoint Protection clients](#configure-and-update-system-center-endpoint-protection-clients).
139139

0 commit comments

Comments
 (0)