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
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,29 +82,29 @@ Set-MDIConfiguration -Mode Domain -Configuration All
82
82
83
83
After ensuring that your environment is completely configured, activate the Microsoft Defender for Identity capabilities on your domain controller.
84
84
85
-
Activate the Defender for Identity from the Microsoft Defender portal(https://security.microsoft.com)
85
+
Activate the Defender for Identity from the [Microsoft Defender portal](https://security.microsoft.com).
86
86
87
-
1. Navigate to **System > Settings > Identities > Activation**
87
+
1. Navigate to **System** > **Settings** > **Identities** > **Activation**.
88
88
89
-
The Activation page lists servers discovered in Device Inventory and identified as eligible domain controllers.
89
+
The Activation page lists servers discovered in Device Inventory and identified as eligible domain controllers.
90
90
91
-
2. Select the domain controller where you want to activate the Defender for Identity capabilities and then select Activate. Confirm your selection when prompted.
91
+
2. Select the domain controller where you want to activate the Defender for Identity capabilities and then select **Activate**. Confirm your selection when prompted.
92
92
93
-
> [!NOTE]
94
-
> You can choose to activate eligible domain controllers either automatically, where Defender for Identity activates them as soon as they are discovered, or manually, where you select specific domain controllers from the list of eligible servers.
93
+
> [!NOTE]
94
+
>You can choose to activate eligible domain controllers either automatically, where Defender for Identity activates them as soon as they are discovered, or manually, where you select specific domain controllers from the list of eligible servers.
95
95
96
96
3. When the activation is complete, a green success banner shows. In the banner, select **Click here to see the onboarded servers** to jump to the **Settings > Identities > Sensors** page, where you can check your sensor health.
97
97
98
98
## Onboarding Confirmation
99
99
100
100
To confirm the sensor has been onboarded:
101
101
102
-
1. Navigate to System > Settings > Identities > Sensors
102
+
1. Navigate to **System** > **Settings** > **Identities** > **Sensors**.
103
103
104
104
2. Check that the onboarded domain controller is listed.
105
105
106
106
> [!NOTE]
107
-
> 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 Runningon theSensorspage. Subsequent activations are shown within five minutes.
107
+
> 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.
108
108
109
109
## Test activated capabilities
110
110
@@ -122,7 +122,7 @@ Use the following procedures to test your environment for Defender for Identity
122
122
123
123
### Check the ITDR dashboard
124
124
125
-
In the Defender portal, select **Identities > Dashboard** and review the details shown, checking for expected results from your environment.
125
+
In the Defender portal, select **Identities** > **Dashboard**, and review the details shown, checking for expected results from your environment.
126
126
127
127
For more information, see [Work with Defender for Identity's ITDR dashboard](../dashboard.md).
0 commit comments