Skip to content

Commit 26d0e16

Browse files
Merge pull request #2904 from rlitinsky/patch-8
Update install-sensor.md
2 parents dd1294e + f8df76d commit 26d0e16

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

ATPDocs/deploy/install-sensor.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,10 @@ ms.topic: how-to
77

88
# Install a Microsoft Defender for Identity sensor
99

10-
This article describes how to install a Microsoft Defender for Identity sensor, including a standalone sensor. The default recommendation is to use the UI. However:
10+
> [!IMPORTANT]
11+
> The new sensor is recommended for customers looking to deploy core identity protections to new domain controllers running Windows Server 2019 or newer. For all other identity infrastructure, or for customers looking to deploy the most robust identity protections available from Microsoft Defender for Identity today, we recommend deploying the classic sensor. [Learn more about the new sensor](/defender-for-identity/deploy/activate-capabilities)
12+
13+
This article describes how to install a Microsoft Defender for Identity classic sensor, including a standalone sensor. The default recommendation is to use the UI. However:
1114

1215
- When you're installing the sensor on Windows Server Core, or to deploy the sensor via a software deployment system, follow the steps for [silent installation](#perform-a-defender-for-identity-silent-installation) instead.
1316

@@ -29,9 +32,9 @@ Before you start, make sure that you have:
2932

3033
- Trusted root certificates on your machine. If your trusted root CA-signed certificates are missing, [you might receive a connection error](../troubleshooting-known-issues.md#proxy-authentication-problem-presents-as-a-connection-error).
3134

32-
## Install the sensor by using the UI
35+
## Install the classic sensor by using the UI
3336

34-
Perform the following steps on the domain controller, Active Directory Federation Services (AD FS) server, or Active Directory Certificate Services (AD CS) server.
37+
Perform the following steps on the domain controller, Active Directory Federation Services (AD FS) server, Active Directory Certificate Services (AD CS) server or Entra Connect server.
3538

3639
1. Verify that the machine has connectivity to the relevant [Defender for Identity cloud service endpoints](configure-proxy.md#enable-access-to-defender-for-identity-service-urls-in-the-proxy-server).
3740

0 commit comments

Comments
 (0)