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

General availability of sensor v3.x activation without Defender for Endpoint

Analysis / inference: Microsoft Defender for Identity sensor v3.x activation is now generally available for new deployments on Windows Server 2019 or later domain controllers without requiring Defender for Endpoint.

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

Section 01 · Summary analysis

Defender for Identity introduced general availability for deploying sensor version 3.x on eligible domain controllers running Windows Server 2019 or later independently of Microsoft Defender for Endpoint.

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

Section 02 · Analysis

SecOps Signal analysis
Why it matters

Enables new Microsoft Defender for Identity sensor v3.x deployments on Windows Server 2019 or later domain controllers without requiring Microsoft Defender for Endpoint.

Operational impact

Simplifies architecture requirements for new Defender for Identity rollouts by decoupling sensor v3.x deployment dependencies from Defender for Endpoint on supported domain controllers.

Section 03 · Recommended actions

  • Review deployment prerequisites for new Microsoft Defender for Identity v3.x sensors on Windows Server 2019 and later domain controllers.
  • Note that sensor v2.x migrations are unsupported under this activation method.
What to check
  • Verify domain controller OS versions are Windows Server 2019 or later for new v3.x deployments.
  • Confirm whether existing domain controllers are running sensor v2.x which cannot use this migration path.

Affected scope

ProductsDefender for Identity

Section 04 · References

1 public source