Skip to content

Commit 85fc5ab

Browse files
committed
1 parent 821e7bd commit 85fc5ab

File tree

2 files changed

+3
-8
lines changed

2 files changed

+3
-8
lines changed

articles/defender-for-iot/organizations/how-to-activate-and-set-up-your-on-premises-management-console.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,8 +70,7 @@ After activating an on-premises management console, you'll need to apply new act
7070
|Location |Activation process |
7171
|---------|---------|
7272
|**On-premises management console** | Apply a new activation file on your on-premises management console if you've [modified the number of committed devices](how-to-manage-subscriptions.md#edit-a-plan-for-ot-networks) in your subscription. |
73-
|**Cloud-connected sensors** | Cloud-connected sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active. <br><br>If you're [updating an OT sensor from a legacy version](update-ot-software.md#update-legacy-ot-sensor-software), you'll need to re-activate your updated sensor. |
74-
| **Locally-managed** | Apply a new activation file to locally managed sensors every year. After a sensor's activation file has expired, the sensor will continue to monitor your network, but you'll see a warning message when signing in to the sensor. |
73+
|**Cloud-connected and locally-managed sensors** | Cloud-connected and locally-managed sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active. <br><br>If you're [updating an OT sensor from a legacy version](update-ot-software.md#update-legacy-ot-sensor-software), you'll need to re-activate your updated sensor. |
7574

7675
For more information, see [Manage Defender for IoT subscriptions](how-to-manage-subscriptions.md).
7776

articles/defender-for-iot/organizations/how-to-activate-and-set-up-your-sensor.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -131,16 +131,12 @@ For information about uploading a new certificate, supported certificate paramet
131131

132132
### Activation expirations
133133

134-
After activating a sensor, you'll need to apply new activation files as follows:
134+
After activating a sensor, cloud-connected and locally-managed sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active.
135135

136-
|Location |Activation process |
137-
|---------|---------|
138-
|**Cloud-connected sensors** | Cloud-connected sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active. <br><br>If you're [updating an OT sensor from a legacy version](update-ot-software.md#update-legacy-ot-sensor-software), you'll need to re-activate your updated sensor. |
139-
| **Locally managed** | Apply a new activation file to locally managed sensors every year. After a sensor's activation file has expired, the sensor will continue to monitor your network, but you'll see a warning message when signing in to the sensor. |
136+
If you're [updating an OT sensor from a legacy version](update-ot-software.md#update-legacy-ot-sensor-software), you'll need to re-activate your updated sensor.
140137

141138
For more information, see [Manage Defender for IoT subscriptions](how-to-manage-subscriptions.md) and [Manage the on-premises management console](how-to-manage-the-on-premises-management-console.md).
142139

143-
144140
### Activate an expired license (versions under 10.0)
145141

146142
For users with versions prior to 10.0, your license may expire, and the following alert will be displayed.

0 commit comments

Comments
 (0)