Skip to content

Commit 9deb520

Browse files
committed
fixing warnings
1 parent 2518162 commit 9deb520

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -279,6 +279,6 @@ For more information, see:
279279

280280
- [Onboard a sensor](tutorial-onboarding.md#onboard-and-activate-the-virtual-sensor)
281281

282-
- [Manage sensor activation files](how-to-manage-individual-sensors.md#manage-sensor-activation-files)
282+
- [Manage sensor activation files](how-to-manage-individual-sensors.md#upload-a-new-activation-file)
283283

284284
- [Control what traffic is monitored](how-to-control-what-traffic-is-monitored.md)

articles/defender-for-iot/organizations/how-to-manage-sensors-on-the-cloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ In such cases, do the following steps:
119119

120120
1. [Delete your existing sensor](#sensor-management-options-from-the-azure-portal).
121121
1. [Onboard the sensor again](onboard-sensors.md#onboard-an-ot-sensor), registering it with any new settings.
122-
1. [Upload your new activation file](how-to-manage-individual-sensors.md#upload-new-activation-files).
122+
1. [Upload your new activation file](how-to-manage-individual-sensors.md#upload-a-new-activation-file).
123123

124124
### Reactivate an OT sensor for upgrades to version 22.x from a legacy version
125125

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,7 @@ Billing changes will take effect one hour after cancellation of the previous sub
150150

151151
- For sensors monitoring overlapping network segments, create the activation file under the same zone. Identical devices that are detected in more than one sensor in a zone, will be merged into one device.
152152

153-
1. [Upload a new activation file](how-to-manage-individual-sensors.md#upload-new-activation-files) for your sensors under the new subscription.
153+
1. [Upload a new activation file](how-to-manage-individual-sensors.md#upload-a-new-activation-file) for your sensors under the new subscription.
154154

155155
1. Delete the sensor identities from the previous subscription. For more information, see [Sensor management options from the Azure portal](how-to-manage-sensors-on-the-cloud.md#sensor-management-options-from-the-azure-portal).
156156

0 commit comments

Comments
 (0)