Skip to content

Commit dd2f68f

Browse files
committed
implementing feedback
1 parent 546949c commit dd2f68f

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/defender-for-iot/organizations/how-to-manage-sensors-on-the-cloud.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -116,17 +116,17 @@ This procedure describes how to view sensor health data from the Azure portal. S
116116

117117
:::image type="content" source="media/how-to-manage-sensors-on-the-cloud/sensor-health-widgets.png" alt-text="Screenshot showing the sensor health widgets." lightbox="media/how-to-manage-sensors-on-the-cloud/sensor-health-widgets.png":::
118118

119-
- **Unhealthy** indicates one of the following scenarios:
119+
**Unsupported** means that the sensor has a software version installed that is no longer supported.
120120

121-
- Sensor traffic to Azure isn't stable
122-
- Sensor fails regular sanity tests
123-
- No traffic detected by the sensor
124-
- Sensor software version is no longer supported
125-
- A [remote sensor upgrade from the Azure portal](update-ot-software.md#update-your-sensors) fails
121+
**Unhealthy** indicates one of the following scenarios:
126122

127-
For more information, see our [Sensor health message reference](sensor-health-messages.md).
123+
- Sensor traffic to Azure isn't stable
124+
- Sensor fails regular sanity tests
125+
- No traffic detected by the sensor
126+
- Sensor software version is no longer supported
127+
- A [remote sensor upgrade from the Azure portal](update-ot-software.md#update-your-sensors) fails
128128

129-
- **Unsupported** means that the sensor has a software version install that is no longer supported.
129+
For more information, see our [Sensor health message reference](sensor-health-messages.md).
130130

131131
1. To check on specific sensor issues, filter the grid by sensor health, and select one or more issues to verify. For example:
132132

0 commit comments

Comments
 (0)