You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-device-inventory-for-organizations.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Manage your device inventory from the Azure portal
3
3
description: Learn how to view and manage OT and IoT devices (assets) from the Device inventory page in the Azure portal.
4
-
ms.date: 05/17/2023
4
+
ms.date: 08/27/2023
5
5
ms.topic: how-to
6
6
ms.custom: enterprise-iot
7
7
---
@@ -23,7 +23,7 @@ Use any of the following options to modify or filter the devices shown:
23
23
|Option |Steps |
24
24
|---------|---------|
25
25
|**Sort devices**| Select a column header to sort the devices by that column. Select it again to change the sort direction. |
26
-
|**Filter devices shown**| Either use the **Search** box to search for specific device details, or select **Add filter** to filter the devices shown. <br><br> In the **Add filter** box, define your filter by column name, operator, and value. Select **Apply** to apply your filter.<br><br> You can apply multiple filters at the same time. Search results and filters aren't saved when you refresh the **Device inventory** page. <br><br> The **Network location (Preview)**filter is on by default. |
26
+
|**Filter devices shown**| Either use the **Search** box to search for specific device details, or select **Add filter** to filter the devices shown. <br><br> In the **Add filter** box, define your filter by column name, operator, and value. Select **Apply** to apply your filter.<br><br> You can apply multiple filters at the same time. Search results and filters aren't saved when you refresh the **Device inventory** page. <br><br> The **Last active time** and **Network location (Preview)**filters are on by default. |
27
27
|**Modify columns shown**| Select **Edit columns** :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/edit-columns-icon.png" border="false":::. In the **Edit columns** pane:<br><br> - Select the **+ Add Column** button to add new columns to the grid.<br> - Drag and drop fields to change the columns order.<br>- To remove a column, select the **Delete** :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/trashcan-icon.png" border="false"::: icon to the right.<br>- To reset the columns to their default settings, select **Reset** :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/reset-icon.png" border="false":::. <br><br>Select **Save** to save any changes made. |
28
28
|**Group devices**| From the **Group by** above the gird, select a category, such as **Class**, **Data source**, **Location**, **Purdue level**, **Site**, **Type**, **Vendor**, or **Zone**, to group the devices shown. Inside each group, devices retain the same column sorting. To remove the grouping, select **No grouping**. |
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-troubleshoot-sensor.md
+33-3Lines changed: 33 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
-
title: Troubleshoot the sensor
3
-
description: Troubleshoot your sensor to eliminate any problems you might be having.
4
-
ms.date: 03/14/2023
2
+
title: Troubleshoot the sensor | Microsoft Defender for IoT
3
+
description: Learn how to troubleshoot your Microsoft Defender for IoT OT sensor.
4
+
ms.date: 09/07/2023
5
5
ms.topic: troubleshooting
6
+
#CustomerIntent: As a Defender for IoT sensor admin, I want to know how to troubleshoot sensor issues so that I can get it back online quickly.
6
7
---
7
8
# Troubleshoot the sensor
8
9
@@ -20,6 +21,35 @@ To perform the procedures in this article, make sure that you have:
20
21
21
22
- Access to the OT network sensor as a **Support** user. For more information, see [Default privileged on-premises users](roles-on-premises.md#default-privileged-on-premises-users).
22
23
24
+
## Check sensor - cloud connectivity issues
25
+
26
+
OT sensors automatically run connectivity checks to ensure that your sensor has access to all required endpoints. If a sensor isn't connected, an error is indicated in the Azure portal, on the **Sites and sensors** page, and on the sensor's **Overview** page. For example:
27
+
28
+
:::image type="content" source="media/release-notes/connectivity-error.png" alt-text="Screenshot of a connectivity error on the Overview page." lightbox="media/release-notes/connectivity-error.png":::```
29
+
30
+
Use the **Cloud connectivity troubleshooting** page in your OT sensor to learn more about the error that occurred and recommended mitigation actions you can take.
31
+
32
+
**To troubleshoot connectivity errors**, sign into your OT sensor and do one of the following:
33
+
34
+
- From the sensor's **Overview** page, select the **Troubleshoot*** link in the error at the top of the page
35
+
- Select **System settings > Sensor management > Health and troubleshooting > Cloud connectivity troubleshooting**
36
+
37
+
The **Cloud connectivity troubleshooting** pane opens on the right. If the sensor is connected to the Azure portal, the pane indicates that **The sensor is connected to cloud successfully**. If the sensor isn't connected, a description of the issue and any mitigation instructions are listed instead. For example: <!--need new image-->
38
+
39
+
:::image type="content" source="media/how-to-troubleshoot-the-sensor-and-on-premises-management-console/connectivity-troubleshooting.png" alt-text="Screenshot of the Connectivity troubleshooting pane.":::
40
+
41
+
The **Cloud connectivity troubleshooting** pane covers the following types of issues:
42
+
43
+
|Issue |Description |
44
+
|---------|---------|
45
+
|**Errors establishing secure connections**| Occurs for SSL errors, which typically means that the sensor doesn't trust the certificate found. <br><br>This might occur due to an incorrect sensor time configuration, or using an SSL inspection service. SSL inspection services are often found in proxies and can lead to potential certificate errors. <br><br>For more information, see [Manage SSL/TLS certificates](how-to-manage-individual-sensors.md#manage-ssltls-certificates) and [Synchronize time zones on an OT sensor](how-to-manage-individual-sensors.md#synchronize-time-zones-on-an-ot-sensor).|
46
+
|**General connection errors**| Occurs when the sensor can't connect with one or more required endpoints. <br><br>In such cases, ensure that all required endpoints are accessible from your sensor, and consider configuring more endpoints in your firewall. For more information, see [Provision sensors for cloud management](ot-deploy/provision-cloud-management.md). |
47
+
|**Unreachable DNS server errors**| Occurs when the sensor can't perform name resolution due to an unreachable DNS server. In such cases, verify that your sensor can access the DNS server. For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration)|
48
+
|**Proxy authentication issues**| Occurs when a proxy demands authentication, but no credentials, or incorrect credentials, are provided. <br><br>In such cases, make sure that you've configured the proxy credentials correctly. For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration). |
49
+
|**Name resolution failures**| Occurs when the sensor can't perform name resolution for a specific endpoint. <br><br>In such cases, if your DNS server is reachable, make sure that the DNS server is configured on your sensor correctly. If the configuration is correct, we recommend reaching out to your DNS administrator. <br><br>For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration). |
50
+
|**Unreachable proxy server errors**| Occurs when the sensor can't establish a connection with the proxy server. In such cases, confirm the reachability of your proxy server with your network team. <br><br>For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration). |
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/release-notes.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: OT monitoring software versions - Microsoft Defender for IoT
3
3
description: This article lists Microsoft Defender for IoT on-premises OT monitoring software versions, including release and support dates and highlights for new features.
4
4
ms.topic: release-notes
5
-
ms.date: 08/09/2023
5
+
ms.date: 09/14/2023
6
6
---
7
7
8
8
# OT monitoring software versions
@@ -38,6 +38,7 @@ Cloud features may be dependent on a specific sensor version. Such features are
38
38
| Version / Patch | Release date | Scope | Supported until |
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/roles-on-premises.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: On-premises users and roles for Defender for IoT - Microsoft Defender for IoT
3
3
description: Learn about the on-premises user roles available for OT monitoring with Microsoft Defender for IoT network sensors and on-premises management consoles.
4
-
ms.date: 09/19/2022
4
+
ms.date: 08/27/2023
5
5
ms.topic: concept-article
6
6
---
7
7
@@ -44,7 +44,7 @@ Permissions applied to each role differ between the sensor and the on-premises m
0 commit comments