Skip to content

Commit 9dce8b1

Browse files
authored
Inbal's comments
1 parent be6486b commit 9dce8b1

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

articles/defender-for-iot/organizations/configure-sensor-settings-portal.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,12 @@ Your new setting is now listed on the **Sensor settings (Preview)** page under i
5252

5353
:::image type="content" source="media/configure-sensor-settings-portal/sensor-details-setting.png" alt-text="Screenshot of a sensor details page showing a setting applied.":::
5454

55+
> [!TIP]
56+
> You may want to configure exceptions to your settings for a specific OT sensor or zone. In such cases, create an extra setting for the exception.
57+
>
58+
> Settings override eachother in a hierarchical manner, so that if your setting is applied to a specific OT sensor, it overrides any related settings that are applied to the entire zone or site. To create an exception for an entire zone, add a setting for that zone to override any related settings applied to the entire site.
59+
>
60+
5561
## View and edit current OT sensor settings
5662

5763
**To view the current settings already defined for your subscription**:
@@ -115,6 +121,8 @@ For a bandwidth cap, define the maximum bandwidth you want the sensor to use for
115121

116122
### Subnet
117123

124+
Configuring subnets from the Azure portal overwrites any subnets already configured on the OT sensors.
125+
118126
To define your sensor's subnets do any of the following:
119127

120128
- Select **Import subnets** to import a comma-separated list of subnet IP addresses and masks. Select **Export subnets** to export a list of currently configured data, or **Clear all** to start from scratch.
@@ -123,7 +131,10 @@ To define your sensor's subnets do any of the following:
123131

124132
### VLAN naming
125133

126-
To define a VLAN for your sensor, enter the VLAN ID and a meaningful name.
134+
Configuring VLANs from the Azure portal overwrites any VLANs already configured on the OT sensors.
135+
136+
To define a VLAN for your OT sensor, enter the VLAN ID and a meaningful name.
137+
127138
Select **Add VLAN** to add more VLANs as needed.
128139

129140
## Next steps
@@ -132,4 +143,4 @@ Select **Add VLAN** to add more VLANs as needed.
132143
> [Manage sensors from the Azure portal](how-to-manage-sensors-on-the-cloud.md)
133144
134145
> [!div class="nextstepaction"]
135-
> [Manage OT sensors from the sensor console](how-to-manage-individual-sensors.md)
146+
> [Manage OT sensors from the sensor console](how-to-manage-individual-sensors.md)

0 commit comments

Comments
 (0)