SecOps SignalSecurity Intelligence Workspace
Collection Degraded30 / 46 Sources HealthyPublic Intel Only
Source: Microsoft Defender for Identity - What's new · Limited verificationCanonical source
RECENTProduct updateAction required

Known limitation: Migration of domain controllers with Windows Server 2025 from sensor v2.x to sensor v3.x is not supported

Analysis / inference: Microsoft Defender for Identity notes a known limitation where migrating Windows Server 2025 domain controllers from sensor v2.x to v3.x is not supported.

Dates
Source and collection dates not recorded
Source
Microsoft Defender for Identity - What's new · Limited verification
Classification
Microsoft Security

Section 01 · Summary analysis

Microsoft has documented a restriction preventing the direct migration of Windows Server 2025 domain controllers running Defender for Identity sensor v2.x to sensor v3.x.

AI summary / analysis; claims are not independently verified. Check the primary source before acting.

Section 02 · Analysis

SecOps Signal analysis
Why it matters

Migrating a domain controller running Windows Server 2025 to Microsoft Defender for Identity sensor v3.x is currently unsupported and can disrupt monitoring or sensor stability.

Operational impact

Attempting to migrate unsupported sensor versions on Windows Server 2025 domain controllers may cause deployment failures or loss of identity monitoring visibility.

Section 03 · Recommended actions

  • Keep Windows Server 2025 domain controllers on sensor v2.x.
  • Postpone any sensor v3.x upgrades for Windows Server 2025 domain controllers until Microsoft releases official support.
What to check
  • Verify the current version of Microsoft Defender for Identity sensors deployed on Windows Server 2025 domain controllers.
  • Check if any planned upgrades from sensor v2.x to v3.x are scheduled for Windows Server 2025 environments.

Affected scope

ProductsDefender for Identity

Section 04 · References

1 public source