Fix unhealthy sensors in Microsoft Defender for Endpoint

Applies to:

Want to experience Microsoft Defender for Endpoint? Sign up for a free trial.

Devices can be categorized as misconfigured or inactive are flagged for varying causes. This section provides some explanations as to what might have caused a device to be categorized as inactive or misconfigured.

Inactive devices

An inactive device is not necessarily flagged because of an issue. The following actions taken on a device can cause a device to be categorized as inactive:

Device is not in use

Any device that is not in use for more than seven days will retain 'Inactive' status in the portal.

Device was reinstalled or renamed

A new device entity is generated in Microsoft 365 Defender for reinstalled or renamed devices. The previous device entity remains, with an 'Inactive' status in the portal. If you reinstalled a device and deployed the Defender for Endpoint package, search for the new device name to verify that the device is reporting normally.

Device was offboarded

If the device was offboarded, it will still appear in devices list. After seven days, the device health state should change to inactive.

Device is not sending signals

If the device is not sending any signals to any Microsoft Defender for Endpoint channels for more than seven days for any reason, a device can be considered inactive; this includes conditions that fall under misconfigured devices classification.

Do you expect a device to be in 'Active' status? Open a support ticket.

Misconfigured devices

Misconfigured devices can further be classified to:

  • Impaired communications
  • No sensor data

Impaired communications

This status indicates that there is limited communication between the device and the service.

The following suggested actions can help fix issues related to a misconfigured device with impaired communications:

If you took corrective actions and the device status is still misconfigured, open a support ticket.

No sensor data

A misconfigured device with status 'No sensor data' has communication with the service but can only report partial sensor data.

Follow theses actions to correct known issues related to a misconfigured device with status 'No sensor data':

If you took corrective actions and the device status is still misconfigured, open a support ticket.

See also