Skip to content

Commit 8599188

Browse files
authored
smoothing instructions
1 parent 332f665 commit 8599188

File tree

1 file changed

+10
-24
lines changed

1 file changed

+10
-24
lines changed

articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md

Lines changed: 10 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -63,43 +63,29 @@ In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defe
6363

6464
For more information, see [Update Defender for IoT OT monitoring software](update-ot-software.md).
6565

66-
## Manage sensor activation files
66+
## Upload a new activation file
6767

68-
Your sensor was onboarded with Microsoft Defender for IoT from the Azure portal. Each sensor was onboarded as either a locally connected sensor or a cloud-connected sensor.
68+
Each OT sensor is onboarded as a cloud-connected or locally-managed OT sensor and activated using a unique activation file. For cloud-connected sensors, the activation file is used to ensure the connection between the sensor and Azure.
6969

70-
A unique activation file is uploaded to each sensor that you deploy. The activation file for cloud-connected sensors is used to ensure the connection to Defender for IoT.
71-
72-
For more information about when and how to use a new file, see [Upload new activation files](#upload-new-activation-files). If you can't upload the file, see [Troubleshoot activation file upload](#troubleshoot-activation-file-upload).
73-
74-
### Upload new activation files
75-
76-
You might need to upload a new activation file for an onboarded sensor when you want to work in a different sensor management mode.
70+
You'll need to upload a new activation file to your senor if you want to switch sensor management modes, such as moving from a locally-managed sensor to a cloud-connected sensor. Uploading a new activation file to your sensor includes deleting your sensor from the Azure portal and onboarding it again.
7771

7872
**To add a new activation file:**
7973

80-
1. Go to [Defender for IoT on the Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started).
81-
1. Use the search bar to find the sensor you need.
82-
83-
1. Select the three dots (...) on the row and select **Delete sensor**.
74+
1. In [Defender for IoT on the Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started) > **Sites and sensors**, locate and [delete](how-to-manage-sensors-on-the-cloud.md#sensor-maintenance-and-troubleshooting) your OT sensor.
8475

85-
1. Onboard the sensor again by selecting **Getting Started**> **Set up OT/ICS Security** > **Register this sensor with Microsoft Defender for IoT**.
76+
1. Select **Onboard OT sensor > OT** to onboard the sensor again from scratch. For more information, see [Onboard OT sensors](onboard-sensors.md)
8677

87-
1. Go to the **Sites and sensors** page.
78+
1. On the **sites and sensors** page locate the sensor you just added.
8879

89-
1. Use the search bar to find the sensor you just added, and select it.
90-
1. Select the three dots (...) on the row and select **Download activation file**.
80+
1. Select the three dots (...) on the sensor's row and select **Download activation file**. Save the file in a location accessible to your sensor.
9181

9282
[!INCLUDE [root-of-trust](includes/root-of-trust.md)]
9383

94-
1. Save the file.
84+
1. Sign in to the Defender for IoT sensor console and select **System Settings** > **Sensor management** > **Subscription & Activation Mode**.
9585

96-
1. Sign in to the Defender for IoT sensor console.
97-
98-
1. Select **System Settings** > **Sensor management** > **Subscription & Activation Mode**.
86+
1. Select **Upload** and browse to the file that you downloaded from the Azure portal.
9987

100-
1. Select **Upload** and select the file that you saved.
101-
102-
1. Select **Activate**.
88+
1. Select **Activate** to upload your new activation file.
10389

10490
### Troubleshoot activation file upload
10591

0 commit comments

Comments
 (0)