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: .acrolinx-config.edn
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ For more information about the exception criteria and exception process, see [Mi
39
39
40
40
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. _You should fix all spelling errors regardless of your total score_. Fixing spelling errors helps maintain customer trust in overall content quality.
41
41
42
-
| Article | Total score<br>(Required: 80) | Words + phrases<br>(Brand, terms) | Correctness<br>(Spelling, grammar) | Clarity<br>(Readability) |
42
+
| Article | Total score<br>(Required: 80) | Terminology | Spelling and Grammar| Clarity<br>(Readability) |
Copy file name to clipboardExpand all lines: ATADocs/index.yml
-1Lines changed: 0 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,6 @@ metadata:
8
8
description: Protect your enterprise using information from multiple network data-sources to learn the behavior of users and entities in your organization.
Copy file name to clipboardExpand all lines: ATPDocs/deploy/remote-calls-sam.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Microsoft Defender for Identity mapping for [potential lateral movement paths](/
11
11
12
12
> [!NOTE]
13
13
> This feature can potentially be exploited by an adversary to obtain the Net-NTLM hash of the DSA account due to a Windows limitation in the SAM-R calls that allows downgrading from Kerberos to NTLM.
14
-
> The new Defender for Identity sensor is not affected by this issue as it uses different detection methods.
14
+
> The new Defender for Identity sensor (version 3.x) is not affected by this issue as it uses different detection methods.
15
15
>
16
16
> It is recommended to use a [low privileged DSA account](directory-service-accounts.md#grant-required-dsa-permissions). You can also [contact support](../support.md) to open a case and request to completely disable the [Lateral Movement Paths](../security-assessment-riskiest-lmp.md) data collection capability.
17
17
> Please note that this will result in reduced data available for the [attack path feature in Exposure Management](/security-exposure-management/review-attack-paths).
Copy file name to clipboardExpand all lines: ATPDocs/deploy/test-connectivity.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,9 @@ After preparing the server that you're going to use for your Microsoft Defender
14
14
15
15
For more information, see [Required ports](../prerequisites.md#ports).
16
16
17
+
> [!NOTE]
18
+
> To get the name and other important details about your Defender for Identity workspace, see the [About page](../settings-about.md) in the [Microsoft Defender XDR](https://security.microsoft.com/) portal.
19
+
17
20
## Test connectivity using a browser
18
21
19
22
1. Open a browser. If you're using a proxy, make sure that your browser uses the same proxy settings being used by the sensor.
Copy file name to clipboardExpand all lines: ATPDocs/health-alerts.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Microsoft Defender for Identity health issues
3
3
description: This article describes all the health issues that can occur for each component, listing the cause and the steps needed to resolve the problem
4
-
ms.date: 07/09/2024
4
+
ms.date: 01/16/2025
5
5
ms.topic: how-to
6
6
---
7
7
@@ -191,6 +191,12 @@ Sensor-specific health issues are displayed in the **Sensor health issues** tab
191
191
|----|----|----|----|----|
192
192
|Radius accounting (VPN integration) data ingestion failures.|The listed Defender for Identity sensors have radius accounting (VPN integration) data ingestion failures.|Validate that the shared secret in the Defender for Identity configuration settings matches your VPN server, according to the guidance described [Configure VPN in Defender for Identity](vpn-integration.md#configure-vpn-in-defender-for-identity) section, in the [Defender for Identity VPN integration](vpn-integration.md) page.|Low|Health issues page|
193
193
194
+
### Auditing for AD CS servers is not enabled as required
|Auditing for AD CS servers is not enabled as required. (This configuration is validated once a day, per sensor).|The Advanced Auditing Policy Configuration or AD CS auditing is not enabled as required.|Enable the Advanced Auditing Policy Configuration and AD CS auditing according to the guidance as described in the [Configure auditing on AD CS](configure-windows-event-collection.md#configure-auditing-on-ad-cs) section, in the [Configure Windows Event collection](configure-windows-event-collection.md) page.|Medium|Sensors health issues tab|
199
+
194
200
### Sensor failed to retrieve Microsoft Entra Connect service configuration
0 commit comments