Skip to content

Commit 3b93b59

Browse files
authored
Fixed formatting
1 parent 7419be6 commit 3b93b59

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

ATPDocs/deploy/activate-capabilities.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -82,29 +82,29 @@ Set-MDIConfiguration -Mode Domain -Configuration All
8282

8383
After ensuring that your environment is completely configured, activate the Microsoft Defender for Identity capabilities on your domain controller.
8484

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).
8686

87-
1. Navigate to **System > Settings > Identities > Activation**
87+
1. Navigate to **System** > **Settings** > **Identities** > **Activation**.
8888

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.
9090

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.
9292

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.
9595
9696
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.
9797

9898
## Onboarding Confirmation
9999

100100
To confirm the sensor has been onboarded:
101101

102-
1. Navigate to System > Settings > Identities > Sensors
102+
1. Navigate to **System** > **Settings** > **Identities** > **Sensors**.
103103

104104
2. Check that the onboarded domain controller is listed.
105105

106106
> [!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.
108108
109109
## Test activated capabilities
110110

@@ -122,7 +122,7 @@ Use the following procedures to test your environment for Defender for Identity
122122

123123
### Check the ITDR dashboard
124124

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.
126126

127127
For more information, see [Work with Defender for Identity's ITDR dashboard](../dashboard.md).
128128

0 commit comments

Comments
 (0)