changes

Author: tarTech23

articles/defender-for-iot/organizations/cli-ot-sensorOLD.md

@@ -1,11 +1,11 @@
 ---
-title: CLI command reference from OT network sensors- Microsoft Defender for IoT
+title: CLI command reference from OT network sensors- Microsoft Defender for IoT old
 description: Learn about the CLI commands available from Microsoft Defender for IoT OT network sensors.
 ms.date: 12/19/2023
 ms.topic: reference
 ---
 
-# CLI command reference from OT network sensors
+# CLI command reference from OT network sensorsOLD
 
 This article lists the CLI commands available from Defender for IoT OT network sensors.
 

articles/defender-for-iot/organizations/cli-ot-sensornew2.md

@@ -1,11 +1,11 @@
 ---
-title: CLI command reference from OT network sensors- Microsoft Defender for IoT
+title: CLI command reference from OT network sensors- Microsoft Defender for IoT - new2
 description: Learn about the CLI commands available from Microsoft Defender for IoT OT network sensors.
 ms.date: 12/19/2023
 ms.topic: reference
 ---
 
-# CLI command reference from OT network sensors
+# CLI command reference from OT network sensors NEW2
 
 This article lists the CLI commands available from Defender for IoT OT network sensors.
 

articles/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands.md

@@ -6,7 +6,7 @@ ms.topic: concept-article
 ---
 
 # Defender for IoT CLI users and access
-<!-- what to remove from this page?-->
+**Belle remove ??** what to remove from this page? -->
 This article provides an introduction to the Microsoft Defender for IoT command line interface (CLI). The CLI is a text-based user interface that allows you to access your OT sensors and the on-premises management console for advanced configuration, troubleshooting, and support.
 
 To access the Defender for IoT CLI, you'll need access to the sensor or on-premises management console.
@@ -36,7 +36,7 @@ For more information, see [On-premises users and roles for OT monitoring with De
 The following tables list the activities available by CLI and the privileged users supported for each activity. The *cyberx* and *cyberx_host* users are only supported in versions earlier than [23.1.x](release-notes.md).
 
 ### Appliance maintenance commands
-<!-- remove  and change restart and shutdown - restore?? -->
+**Belle remove ??** remove  and change restart and shutdown - restore?? 
 |Service area  |Users  |Actions  |
 |---------|---------|---------|
 |Sensor health     |   *admin*, *cyberx*      | [Check OT monitoring services health](cli-ot-sensor.md#check-ot-monitoring-services-health)        |
@@ -46,15 +46,17 @@ The following tables list the activities available by CLI and the privileged use
 |NTP     | *admin*, *cyberx*        | [Turn on NTP time sync](cli-ot-sensor.md#turn-on-ntp-time-sync)<br>[Turn off NTP time sync](cli-ot-sensor.md#turn-off-ntp-time-sync)        |
 
 ### Backup and restore commands
-<!-- remove  and change bnackup disk - restore?? -->
+
+**Belle remove ??** remove  and change bnackup disk - restore??
 |Service area  |Users  |Actions  |
 |---------|---------|---------|
 |Backup files     | *admin*, *cyberx*        | [List current backup files](cli-ot-sensor.md#list-current-backup-files)    <br>[Start an immediate, unscheduled backup](cli-ot-sensor.md#start-an-immediate-unscheduled-backup)    |
 |Restore     | *admin*, *cyberx*        | [Restore data from the most recent backup](cli-ot-sensor.md#restore-data-from-the-most-recent-backup)        |
 |Backup disk space     |  *cyberx*       |  [Display backup disk space allocation](cli-ot-sensor.md#display-backup-disk-space-allocation)       |
 
 ### TLS/SSL certificate commands
-<!-- remove  ??-->
+
+**Belle remove ??**
 |Service area  |Users  |Actions  |
 |---------|---------|---------|
 |Certificate management     | *cyberx*        | [Import TLS/SSL certificates to your OT sensor](cli-ot-sensor.md#import-tlsssl-certificates-to-your-ot-sensor)<br>[Restore the default self-signed certificate](cli-ot-sensor.md#restore-the-default-self-signed-certificate)        |
@@ -74,24 +76,25 @@ The following tables list the activities available by CLI and the privileged use
 | Network setting configuration | *cyberx_host* | [Change networking configuration or reassign network interface roles](cli-ot-sensor.md#change-networking-configuration-or-reassign-network-interface-roles) |
 |Network setting configuration     |  *admin*       |  [Validate and show network interface configuration](cli-ot-sensor.md#validate-and-show-network-interface-configuration)       |
 |Network connectivity     |  *admin*, *cyberx*       |  [Check network connectivity from the OT sensor](cli-ot-sensor.md#check-network-connectivity-from-the-ot-sensor)       |
-|Network connectivity      |  *cyberx*       | [Check network interface current load](cli-ot-sensor.md#check-network-interface-current-load) <br>[Check internet connection](cli-ot-sensor.md#check-internet-connection)         |
-|Network bandwidth limit     |    *cyberx*     | [Set bandwidth limit for the management network interface](cli-ot-sensor.md#set-bandwidth-limit-for-the-management-network-interface)        |
+**Belle remove ??**|Network connectivity      |  *cyberx*       | [Check network interface current load](cli-ot-sensor.md#check-network-interface-current-load) <br>[Check internet connection](cli-ot-sensor.md#check-internet-connection)         |**Belle remove ??**
+|Network bandwidth limit     |    *cyberx*     | [Set bandwidth limit for the management network interface](cli-ot-sensor.md#set-bandwidth-limit-for-the-management-network-interface)        |**Belle remove ??**
 |Physical interfaces management     | *admin*        | [Locate a physical port by blinking interface lights](cli-ot-sensor.md#locate-a-physical-port-by-blinking-interface-lights)        |
 |Physical interfaces management    | *admin*, *cyberx*        |     [List connected physical interfaces](cli-ot-sensor.md#list-connected-physical-interfaces)    |
 
 ### Traffic capture filter commands
-<!-- remove this as well?-->
+**Belle remove ??**
 |Service area  |Users  |Actions  |
 |---------|---------|---------|
 | Capture filter management    |  *admin*, *cyberx*       | [Create a basic filter for all components](cli-ot-sensor.md#create-a-basic-filter-for-all-components)<br>[Create an advanced filter for specific components](cli-ot-sensor.md#create-an-advanced-filter-for-specific-components)  <br>[List current capture filters for specific components](cli-ot-sensor.md#list-current-capture-filters-for-specific-components)  <br> [Reset all capture filters](cli-ot-sensor.md#reset-all-capture-filters)   |
-<!--
+**Belle remove ??**
 ### Alert commands
 
 |Service area  |Users  |Actions  |
 |---------|---------|---------|
 |Alert functionality testing     |  *cyberx*       |   [Trigger a test alert](cli-ot-sensor.md#trigger-a-test-alert)      |
 | Alert exclusion rules | *admin*, *cyberx* | [Show current alert exclusion rules](cli-ot-sensor.md#show-current-alert-exclusion-rules) <br>[Create a new alert exclusion rule](cli-ot-sensor.md#create-a-new-alert-exclusion-rule)<br>[Modify an alert exclusion rule](cli-ot-sensor.md#modify-an-alert-exclusion-rule)<br>[Delete an alert exclusion rule](cli-ot-sensor.md#delete-an-alert-exclusion-rule)
--->
+**Belle remove until here??**
+
 ## Defender for IoT CLI access
 
 To access the Defender for IoT CLI, sign in to your OT or Enterprise IoT sensor or your on-premises management console using a terminal emulator and SSH.
@@ -104,7 +107,7 @@ Each CLI command on an OT network sensor or on-premises management console is su
 
 ## Access the system root as an *admin* user
 
-When signing in as the *admin* user, run the following command to access the host machine as the root user. Access the host machine as the root user enables you to run CLI commands that aren't available to the *admin* user. 
+When signing in as the *admin* user, run the following command to access the host machine as the root user. Access the host machine as the root user enables you to run CLI commands that aren't available to the *admin* user.
 
 Run: