You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ATPDocs/deploy/activate-capabilities.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ This article describes how to activate and test Microsoft Defender for Identity
13
13
> The capabilities described in this article are currently available as Preview features. Preview features are features that aren't complete, but are made available on a "preview" basis so customers can get early access and provide feedback.
14
14
>
15
15
> Preview features are still in development, have limited or restricted functionality and may be available only in selected geographic areas.
16
-
> For more information, see the [Microsoft Defender XDR preview features](../defender-xdr/preview.md)
16
+
> For more information, see the [Microsoft Defender XDR preview features](defender-xdr/preview.md)
17
17
18
18
> [!IMPORTANT]
19
19
> The new Defender for Identity sensor (version 3.x) 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 [here](quick-installation-guide.md).
@@ -109,10 +109,10 @@ Download the Defender for Identity onboarding package from the [Microsoft Defend
109
109
1. Navigate to **System** > **Settings** > **Identities** > **Activation**
110
110
111
111
1. Select Download onboarding package and save the file in a location you can access from your domain controller.
112
-

112
+

113
113
114
114
1. From the domain controller, extract the zip file you downloaded from the Microsoft Defender portal, and run the `DefenderForIdentityOnlyOnboardingScript.cmd` script as an Administrator.
115
-

115
+

116
116
117
117
## Onboarding Confirmation
118
118
@@ -126,7 +126,7 @@ To confirm the sensor has been onboarded:
126
126
> The onboarding doesn't require a restart/reboot. The first time you activate Defender for Identity capabilities on your domain controller, it may take up to an hour for the first sensor to show as **Running** on the **Sensors** page. Subsequent activations are shown within five minutes.
127
127
128
128
To check the onboarding on the local server you can also review the event log under **Applications and Services Logs** > **Microsoft** > **Windows** > **Sense** > **Operational**. You should receive an onboarding event:
129
-

129
+

130
130
131
131
**Test activated capabilities**
132
132
@@ -239,7 +239,7 @@ If you want to deactivate Defender for Identity capabilities on your domain cont
239
239
240
240
1. Navigate to **Settings** > **Identities** > **Sensors**
241
241
1. Select the domain controller where you want to deactivate Defender for Identity capabilities, select **Delete**, and confirm your selection.
242
-

242
+

243
243
244
244
245
245
Deactivating Defender for Identity capabilities from your domain controller doesn't remove the domain controller from Defender for Endpoint. For more information, see [Defender for Endpoint documentation](/microsoft-365/security/defender-endpoint/).
@@ -252,10 +252,10 @@ Download the Defender for Identity offboarding package from the [Microsoft Defen
252
252
1. Navigate to **Settings** > **Identities** > **Activation**
253
253
254
254
1. Select Download offboarding package and save the file in a location you can access from your domain controller.
255
-

255
+

256
256
1. From the domain controller, extract the zip file you downloaded from the Microsoft Defender portal, and run the `DefenderForIdentityOnlyOffboardingScript_valid_until_YYYY-MM-DD.cmd` script as an Administrator.
257
257
1. To fully remove the sensor, navigate to **Settings** > **Identities** > **Sensors**, select the server and click Delete.
258
-

258
+

0 commit comments