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

Migrate Defender for Identity sensors from v2.x to v3.x

Analysis / inference: Microsoft Defender for Identity now supports in-portal migration of sensors from version v2.x to v3.x with zero downtime.

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

Section 01 · Summary analysis

Admins can execute sensor version upgrades from v2.x to v3.x seamlessly from the Microsoft Defender portal, maintaining continuous monitoring during the process.

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

Section 02 · Analysis

SecOps Signal analysis
Why it matters

Upgrading core security sensors directly impacts telemetry integrity and support lifecycle compliance for Active Directory monitoring.

Operational impact

Migration processes take up to 20 minutes per eligible server while keeping the original sensor active until the new version is fully initialized.

Section 03 · Recommended actions

  • Review the Sensors page in the Microsoft Defender portal to identify servers eligible for v3.x migration.
  • Initiate migration for eligible servers following standard maintenance procedures.
What to check
  • Check the Microsoft Defender portal Sensors page for servers marked as Ready for migration.

Affected scope

ProductsDefender for Identity

Section 04 · References

1 public source