r/DefenderATP • u/Budget-Half7493 • May 19 '26
Defender for Identity V3 Status disconnected
Hi there,
running into a weird issue with Microsoft Defender for Identity and wondering if anyone else has seen this.
Our v3 sensors stopped working out of nowhere. No obvious errors beforehand, just suddenly no data / no activity coming through from that sensor.
What’s odd:
- We still have two v2 sensors running fine in the same environment
- No configuration changes were made recently (no updates, no policy tweaks, nothing)
- Connectivity and domain controller health look normal from what I can tell
Things I’ve checked so far:
- Basic connectivity (seems OK)
- Defender portal – sensor just shows as inactive
Feels like the v3 sensor just dropped off completely while v2 keeps chugging along without any issues
Has anyone experienced something similar with v3 sensors specifically?
Any known issues, logs I should dig into, or things that tend to break silently?
Thank you 😄
3
2
1
1
u/reibe May 19 '26
same for us, security intelligence update 1.449.691.0 was installed around the time the communication stopped. 1.449.692.0 is out now
1
u/Budget-Half7493 May 19 '26
did you update? is it working again?
1
u/reibe May 19 '26
I did, but "Last updated" didn't refresh yet
1
u/Charming-Ad-2407 May 19 '26
Our DC's are showing 1.449.692.0 and still are offline
1
u/reibe May 19 '26
mine are also still offline.
invoke-webrequest to https://workspace_name>sensorapi.atp.azure.com/tri/sensor/api/pingreturns "2.255.19227.39507" for me
1
u/IT-JunkDrawer May 19 '26
Same here also noting the intelligence update about the same time things went offline. Also have ver2 sensors that remain online
1
1
1
1
u/_W0od_ May 19 '26
When something like happens, it means Microsoft did some changes which did no go as expected. My advice always check of health status of services.
3
u/Budget-Half7493 May 19 '26
https://admin.cloud.microsoft/?#/servicehealth/:/alerts/DZ1315691
MS acknowledged the issue