Merge pull request #222605 from Shereen-Bhar/Remove-references-to-updatable

Removing references to 'updatable'

Author: ttorble

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

@@ -99,7 +99,7 @@ You may need to reactivate an OT sensor because you want to:
 
 - **Associate the sensor to a new site**:  Re-register the sensor with new site definitions and use the new activation file to activate.
 
-- **Change your plan commitment**: If you make changes to your plan, for example if you change your price plan from a trial to a monthly commitment, you'll need to reactivate your sensors to reflect the new changes.
+- **Change your plan commitment**: If you make changes to your plan, such as changing your price plan from a trial to a monthly commitment, you'll need to reactivate your sensors to reflect the new changes.
 
 In such cases, do the following steps:
 
@@ -126,24 +126,23 @@ This procedure describes how to view sensor health data from the Azure portal. S
 
 1. From Defender for IoT in the Azure portal, select **Sites and sensors** and then check the overall health score in the widget above the grid. For example:
 
-    :::image type="content" source="media/how-to-manage-sensors-on-the-cloud/sensor-widgets.png" alt-text="Screenshot showing the sensor health widgets." lightbox="media/how-to-manage-sensors-on-the-cloud/sensor-widgets.png":::
+    :::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":::
 
-    - **Unhealthy** indicates one of the following scenarios:
+    **Unsupported** means that the sensor has a software version installed that is no longer supported.
 
-        - Sensor traffic to Azure isn't stable
-        - Sensor fails regular sanity tests
-        - No traffic detected by the sensor
-        - Sensor software version is no longer supported
-        - A [remote sensor upgrade from the Azure portal](update-ot-software.md#update-your-sensors) fails
+    **Unhealthy** indicates one of the following scenarios:
 
-        For more information, see our [Sensor health message reference](sensor-health-messages.md).
+    - Sensor traffic to Azure isn't stable
+    - Sensor fails regular sanity tests
+    - No traffic detected by the sensor
+    - Sensor software version is no longer supported
+    - A [remote sensor upgrade from the Azure portal](update-ot-software.md#update-your-sensors) fails
 
-    - **Updatable** means that the sensor has an older version, and there are software updates available to install
-    - **Unsupported** means that the sensor has a software version install that is no longer supported.
+    For more information, see our [Sensor health message reference](sensor-health-messages.md).
 
 1. To check on specific sensor issues, filter the grid by sensor health, and select one or more issues to verify. For example:
 
-    :::image type="content" source="media/how-to-manage-sensors-on-the-cloud/sensor-health-filter.png" alt-text="Screenshot of the sensor health filter." lightbox="media/how-to-manage-sensors-on-the-cloud/sensor-health-filter.png":::
+    :::image type="content" source="media/how-to-manage-sensors-on-the-cloud/sensor-health-filters.png" alt-text="Screenshot of the sensor health filter." lightbox="media/how-to-manage-sensors-on-the-cloud/sensor-health-filters.png":::
 
 1. Expand the filtered sites and sensors now displayed in the grid, and use the **Sensor health** column to learn more at a high level.
 

articles/defender-for-iot/organizations/media/how-to-manage-sensors-on-the-cloud/sensor-health-filter.png

@@ -13,19 +13,17 @@ For more information, see [Understand sensor health (Public preview)](how-to-man
 
 ## Critical messages
 
-
 |Title  |Message  |Description  |Recommendation  |
 |---------|---------|---------|---------|
-|**Disconnected**     |   This sensor is not communicating with Azure     |      Sensor is disconnected   |   Try signing into the sensor to check for errors or networking failures. <br><br>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     |      Sensor fails sanity   |       The sensor is in a degraded state. <br><br>Check the sensor for hardware failures and try restarting the sensor.  If the issue isn't resolved, open a support ticket.  |
+|**Disconnected**     |   This sensor isn't communicating with Azure     |      Sensor is disconnected   |   Try signing into the sensor to check for errors or networking failures. <br><br> 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     |      Sensor fails sanity   |       The sensor is in a degraded state. <br><br> 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      |   No traffic detected      |  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  |Description  |Recommendation  |
 |---------|---------|---------|---------|
-|**Package upload failed** |There was an error uploading the file to the sensor |Upload error |Verify the sensor’s ability to communicate with download.microsoft.com and retry. <br><br>If the problem persists,  open a support ticket.|
+|**Package upload failed** |There was an error uploading the file to the sensor |Upload error |Verify the sensor’s ability to communicate with download.microsoft.com and retry. <br><br> If the problem persists,  open a support ticket.|
 |**Sensor update failed** | There was an error installing the update.| Installation error |Open a support ticket. |
 | **Unstable traffic to Azure**|Sensor’s connection to Azure is unstable |Unstable traffic to Azure | 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.|
 | **Outdated**|Outdated software may result in a non-optimal experience |Sensor version is outdated |Upgrade your sensor software to the latest version to use the most recently available Defender for IoT features.|
@@ -34,9 +32,8 @@ For more information, see [Understand sensor health (Public preview)](how-to-man
 
 |Title  |Message  |Description  |Recommendation  |
 |---------|---------|---------|---------|
-|**Pending activation** |Waiting for sensor to connect for the first time |Pending activation | Upload the activation file to the sensor. If this does not resolve the problem, verify the sensor’s ability to communicate with Azure.|
-|**Pending reactivation** |Waiting for reactivation with new license |Pending reactivation |Upload the new activation file to the sensor. If this does not resolve the problem, verify the sensor’s ability to communicate with Azure. |
-|**Updatable** |A new version is available |Update available | Upgrade your sensor software to the latest version to use the most recently available Defender for IoT features.|
+|**Pending activation** |Waiting for sensor to connect for the first time |Pending activation | 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 |Pending reactivation |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