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-sensors-on-the-cloud.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,22 +101,25 @@ Make the downloaded activation file accessible to the sensor console admin so th
101
101
> As opposed to OT sensors, where you define your sensor's site, all Enterprise IoT sensors are automatically added to the **Enterprise network** site.
102
102
103
103
---
104
-
### Viewing current sensors
104
+
##View your sensors
105
105
106
-
Current sensors are listed in the **Sites and sensors** page, with details in the following columns:
106
+
All of your currently cloud-connected sensors, including both OT and Enterprise IoT sensors, are listed in the **Sites and sensors** page. For example:
107
+
IMAGE TBD
108
+
109
+
Details about each sensor are listed in the following columns:
107
110
108
111
|Column name |Description |
109
112
|---------|---------|
110
-
|Sensor name| Displays the name that you assigned to the sensor during the registration. |
113
+
|**Sensor name**| Displays the name that you assigned to the sensor during the registration. |
111
114
|Sensor type| Displays whether the sensor is locally connected or cloud-connected. |
112
115
|Zone| Displays the zone that contains this sensor.|
113
116
|Subscription name| Displays the name of your Microsoft Azure account subscription. |
114
117
|Sensor version| Displays the software version installed on your sensor. |
115
118
|Sensor status| Displays a [sensor health message](sensor-health-messages.md). For more information, see [Understand sensor health (Public preview)](how-to-manage-sensors-on-the-cloud.md#understand-sensor-health-public-preview).|
116
119
|Last connected (UTC)| Displays how long ago the sensor was last connected.|
117
-
|Threat Intelligence version| Displays the Threat Intelligence version installed on the sensor. The name of the version is based on the day the package was built by Defender for IoT. |
118
-
|Threat Intelligence mode| Displays whether the Threat Intelligence mode is manual or automatic. If it's manual, that means that you can push newly released packages directly to sensors as needed. Otherwise, the new packages will be automatically installed on the cloud connected sensors. |
119
-
|Threat Intelligence update status| Displays the update status of the Threat Intelligence package. The status can be either Failed, In Progress, Update Available, or Ok.|
120
+
|Threat Intelligence version| Displays the [Threat Intelligence version](how-to-work-with-threat-intelligence-packages.md) installed on the sensor. The name of the version is based on the day the package was built by Defender for IoT. |
121
+
|Threat Intelligence mode| Displays whether the Threat Intelligence mode is manual or automatic. If it's manual, that means that you can [push newly released packages directly to sensors](how-to-work-with-threat-intelligence-packages.md) as needed. Otherwise, the new packages will be automatically installed on the cloud connected sensors. |
122
+
|Threat Intelligence update status| Displays the update status of the Threat Intelligence package. The status can be either **Failed**, **In Progress**, **Update Available**, or **Ok**.|
0 commit comments