Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article lists the sensor health messages displayed in the Sites and sensors page in the Azure portal.
For more information, see Understand sensor health.
Critical messages
| Title | Message | Recommendation |
|---|---|---|
| Disconnected | This sensor isn't communicating with Azure | Try signing into the sensor to check for errors or networking failures. We also recommend reviewing the sensor networking configuration and verifying the sensor’s ability to communicate with Azure. |
| Sanity failed | This sensor failed an internal consistency check | The sensor is in a degraded state. Check the sensor for hardware failures and try restarting the sensor. If the issue isn't resolved, open a support ticket. |
| No traffic detected | No traffic detected on the monitored network interfaces | Check that the monitoring ports are connected to SPAN/monitor ports on the adjacent switch and that traffic is active on the link. At least one link with network traffic should be connected to the monitor ports. |
Warning messages
| Title | Message | Recommendation |
|---|---|---|
| Failed to send update | There was an error uploading the file to the sensor | Verify the sensor’s ability to communicate with download.microsoft.com and retry. If the problem persists, open a support ticket. |
| Sensor update failed | There was an error installing the update. | Open a support ticket. |
| Unstable traffic to Azure | Sensor’s connection to Azure is unstable | We recommend that you check the sensor WAN connection, the BW limit settings, and validate network equipment that might be on the route between the sensor and the cloud. |
| Unsupported | Outdated software may result in a non-optimal experience | Upgrade your sensor software to the latest version to use the most recently available Defender for IoT features. |
| Sensor is partially connected | See Sensor partially connected messages | |
| Backup error | Failed to backup to Azure storage. | The primary causes of backup failures are issues with the sensor's network connectivity or an overly large backup file. Please verify the sensor's network connection and ensure it is not overloaded. |
Sensor partially connected messages
The "Sensor is partially connected" message includes one of the following endpoint errors:
| Title | Message | Recommendation |
|---|---|---|
| General endpoint error | Failed to establish a connection with the endpoint/endpoints (specifying the ___domain name). | Verify that all the required endpoints are allowed in the firewall with your network team. |
| DNS endpoint error | Failed to resolve the DNS name of the endpoint/endpoints (specifying the ___domain name). | If the DNS server is reachable, verify the DNS server configured on the sensor is correct. If it is, reach out to your DNS administrator. |
| SSL endpoint error | Failed to establish a secure connection with the endpoint/endpoints (specifying the ___domain name). The presented certificate is not trusted. | - Make sure the time is configured correctly. - Check if you are using SSL inspection service (usually in the proxy). If so, make sure to upload the relevant certificate in the System Settings screen. |
| Proxy authentication endpoint error | - For one endpoint: The proxy requires authentication but none or incorrect credentials were provided. - For multiple endpoints: Verify the authentication credentials with your proxy administrator. Provide the required credentials in the System Settings screen. |
Verify the authentication credentials with your proxy administrator. Provide the required credentials in the System Settings screen. |
| Proxy unnecessary endpoint error | - For one endpoint: Unnecessary credentials were provided to the proxy. - For multiple endpoints: Remove the username and password provided in the proxy configuration. |
Remove the username and password provided in the proxy configuration. |
Healthy messages
| Title | Message | Recommendation |
|---|---|---|
| Pending activation | Waiting for sensor to connect for the first time | Upload the activation file to the sensor. If this doesn't resolve the problem, verify the sensor’s ability to communicate with Azure. |
| Pending reactivation | Waiting for reactivation with new license | Upload the new activation file to the sensor. If this doesn't resolve the problem, verify the sensor’s ability to communicate with Azure. |
Next steps
Remediate each error as recommended. For more information, see Manage sensors with Defender for IoT in the Azure portal.