Skip to content

Add Windows Server 2025 sensor known issue #511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rlitinsky wants to merge 9 commits into from
Closed

Add Windows Server 2025 sensor known issue #511

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
f98802f
Add Windows Server 2025 sensor known issue documentation
rlitinsky May 19, 2026
b62edeb
Add Cause section and fix wording in WS2025 known issue
rlitinsky May 19, 2026
eb91a29
Align WS2025 note to migration-not-supported framing
rlitinsky May 19, 2026
7a1f287
Align WS2025 known issue to migration-not-supported framing
rlitinsky May 19, 2026
c4194a6
Align WS2025 whats-new entry to migration-not-supported framing
rlitinsky May 19, 2026
aa8d80f
Remove future date promises from WS2025 known issue
rlitinsky May 19, 2026
345826c
Remove future date promise from deploy-sensor-v3
rlitinsky May 19, 2026
cc7ea4c
Remove future date promise from whats-new
rlitinsky May 19, 2026
032f9ac
Remove Cause and Resolution subsections from WS2025 known issue
rlitinsky May 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions defender-for-identity/deploy/deploy-sensor-v3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,9 @@ Make sure that the server on which you're activating the sensor:
- Is running Windows Server 2019 or later.
- Includes the [March 2026 or later](https://support.microsoft.com/en-us/topic/march-10-2026-kb5078766-os-build-20348-4893-fa3ee26a-0877-47d7-a4b2-9dd632ea8cea) cumulative update.

> [!IMPORTANT]
> Migrating domain controllers running Windows Server 2025 to sensor v3.x isn’t currently supported. Windows Server 2025 domain controllers should continue using the v2.x sensor.

#### Supported server types

The v3.x sensor supports domain controllers, including domain controllers with these identity roles:
Expand Down
4 changes: 4 additions & 0 deletions defender-for-identity/troubleshooting-known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -486,6 +486,10 @@ If permissions need to be reconfigured, follow the steps outlined in this [guide

In some v3 sensor environments, auditing health alerts might persist even when Windows auditing is correctly configured. This primarily occurs with manual auditing configuration, such as using Group Policy or PowerShell. The sensor remains healthy and detections aren't affected. To resolve, enable **Automatic Windows auditing configuration** in the Defender for Identity portal under **Settings** > **Advanced features**.

## Windows Server 2025 sensor v3.x migration not supported

Migrating domain controllers running Windows Server 2025 to sensor v3.x isn't currently supported. Windows Server 2025 domain controllers should continue using the v2.x sensor until full v3.x support is available.

## Next steps

- [Defender for Identity sensor v2.x prerequisites](deploy/prerequisites-sensor-version-2.md) and [Defender for Identity sensor v3.x prerequisites](deploy/deploy-sensor-v3.md)
Expand Down
6 changes: 6 additions & 0 deletions defender-for-identity/whats-new.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,12 @@ These new alerts were added to the Defender for Identity security alerts:
- [Suspected Conditional Access bypass via non-compliant device](alerts-xdr.md#suspected-conditional-access-bypass-via-non-compliant-device)
- [Suspicious addition of default third‑party MFA method to user account](alerts-xdr.md#suspicious-addition-of-default-thirdparty-mfa-method-to-user-account)

### Known limitation: Windows Server 2025 sensor v3.x migration not supported

Migrating domain controllers running Windows Server 2025 to sensor v3.x isn't currently supported. Windows Server 2025 domain controllers should continue using the v2.x sensor.

For more information, see [Windows Server 2025 sensor v3.x migration not supported](troubleshooting-known-issues.md#windows-server-2025-sensor-v3x-migration-not-supported).

## April 2026

### **Identity Explorer (Preview)**
Expand Down
Loading