Skip to content

Commit 54a8079

Browse files
committed
Learn Editor: Update activate-sensor.md
1 parent d7b8397 commit 54a8079

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

ATPDocs/deploy/activate-sensor.md

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

9-
# Activate the Defender for Identity sensor v3.x on a domain controller (Preview)
9+
# Activate the Defender for Identity sensor v3.x on a domain controller
1010

1111
For complete protection of your on-premises deployment, we recommend activating the Defender for Identity sensor on all applicable servers. This article describes onboarding for new domain controllers running Windows Server 2019 or later. For domain controllers running older operating systems, we recommend [deploying the classic Defender for Identity sensor](install-sensor.md).
1212

@@ -40,11 +40,11 @@ The process for activating the sensor depends on your configuration.
4040
1. Select the domain controller where you want to activate Defender for Identity, and select **Activate**. Confirm your selection when prompted.
4141

4242
[![Screenshot that shows how to activate the new sensor.](media/activate-capabilities/activate.png)](media/activate-capabilities/activate.png#lightbox)
43-
43+
4444
1. When the activation is complete, a green success banner shows. In the banner, select **Click here to see the onboarded servers**. This takes you to the **Sensors** page, where you can check your sensor health.
4545

4646
[![Screenshot that shows how to see the onboarded servers.](media/activate-capabilities/successfully-activated.png)](media/activate-capabilities/successfully-activated.png#lightbox)
47-
47+
4848
<!--## Onboard the domain controller
4949
5050
If the domain controller has not been onboarded to Defender for Endpoint for Servers, follow these steps to activate the sensor.

0 commit comments

Comments
 (0)