Skip to content

Commit e433fab

Browse files
authored
Clarify limitations of Defender for Identity sensor v3.x
Updated sensor version limitations for Defender for Identity v3.x. To clarify the new MDI sensor can run when Defender is running either in active or passive mode as confirmed by PG team.
1 parent 95e8a38 commit e433fab

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

defender-for-identity/deploy/prerequisites-sensor-version-3.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,10 @@ This article describes the requirements for installing the Microsoft Defender fo
1414

1515
Before activating the Defender for Identity sensor v3.x, note that this version of the sensor is still in preview and has some limited functionality compared to version 2.x. Keep these limitations in mind before activating the sensor.
1616
The Defender for Identity sensor v3.x:
17-
- Requires that Defender for Endpoint is deployed
18-
- Can't be activated on a server that has a Defender for Identity sensor V2.x already deployed
19-
- Doesn't currently support VPN integration
20-
- Doesn't currently support ExpressRoute
17+
- Requires that Defender for Endpoint is deployed and that the WDAV (Windows Defender Antivirus) component runs in either active or passive mode.
18+
- Can't be activated on a server that has a Defender for Identity sensor V2.x already deployed.
19+
- Doesn't currently support VPN integration.
20+
- Doesn't currently support ExpressRoute.
2121
- Doesn't currently offer full functionality of health alerts, posture recommendations, security alerts or advanced hunting data.
2222

2323
## Licensing requirements

0 commit comments

Comments
 (0)