Skip to content

Commit 26f4c0c

Browse files
committed
implementing feedback + reverting name changes + editing
1 parent 5856051 commit 26f4c0c

File tree

3 files changed

+7
-12
lines changed

3 files changed

+7
-12
lines changed

.openpublishing.redirection.defender-for-iot.json

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -639,11 +639,6 @@
639639
"source_path_from_root": "/articles/defender-for-iot/device-builders/concept-security-agent-authentication.md",
640640
"redirect_url": "/azure/defender-for-iot/device-builders/tutorial-standalone-agent-binary-installation",
641641
"redirect_document_id": false
642-
},
643-
{
644-
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-enhance-port-and-vlan-name-resolution.md",
645-
"redirect_url": "/azure/defender-for-iot/organizations/how-to-customize-port-and-vlan-names",
646-
"redirect_document_id": false
647642
}
648643
]
649644
}

articles/defender-for-iot/organizations/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -245,8 +245,8 @@
245245
items:
246246
- name: Work with device notifications
247247
href: how-to-work-with-device-notifications.md
248-
- name: Customize port and VLAN names
249-
href: how-to-customize-port-and-vlan-names.md
248+
- name: Enhance port and VLAN name resolution
249+
href: how-to-enhance-port-and-vlan-name-resolution.md
250250
- name: Import device information
251251
href: how-to-import-device-information.md
252252
- name: Track sensor activity

articles/defender-for-iot/organizations/how-to-customize-port-and-vlan-names.md renamed to articles/defender-for-iot/organizations/how-to-enhance-port-and-vlan-name-resolution.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Customize port and VLAN names on OT network sensors - Microsoft Defender for IoT
33
description: Learn how to customize port and VLAN names on Microsoft Defender for IoT OT network sensors.
4-
ms.date: 01/09/2023
4+
ms.date: 01/12/2023
55
ms.topic: how-to
66
---
77

@@ -19,9 +19,9 @@ For more information, see [On-premises users and roles for OT monitoring with De
1919

2020
## Customize names of detected ports
2121

22-
Defender for IoT automatically assigns names to most universally reserved ports, such as DHCP or HTTP. However, you might want to customize the name of specific port to highlight it, such as when you're watching a port with unusually high activity detected.
22+
Defender for IoT automatically assigns names to most universally reserved ports, such as DHCP or HTTP. However, you might want to customize the name of a specific port to highlight it, such as when you're watching a port with unusually high detected activity.
2323

24-
Port names are shown in Defender for IoT when [viewing device groups from the OT sensor's device map](hyperlink this), or when you create OT sensor reports that include port information.
24+
Port names are shown in Defender for IoT when [viewing device groups from the OT sensor's device map](how-to-work-with-the-sensor-device-map.md#group-highlight-and-filters-tools), or when you create OT sensor reports that include port information.
2525

2626
**To customize a port name:**
2727

@@ -35,9 +35,9 @@ Port names are shown in Defender for IoT when [viewing device groups from the OT
3535

3636
## Customize a VLAN name
3737

38-
VLANS are either discovered automatically by the OT network sensor or added manually. Automatically discovered VLANs can't be edited or deleted, but manually added VLANs require a unique name. If a VLAN isn't explicitely named, the VLANs number is shown instead.
38+
VLANs are either discovered automatically by the OT network sensor or added manually. Automatically discovered VLANs can't be edited or deleted, but manually added VLANs require a unique name. If a VLAN isn't explicitly named, the VLAN's number is shown instead.
3939

40-
VLANs support is based on 802.1q (up to VLAN ID 4094).
40+
VLAN's support is based on 802.1q (up to VLAN ID 4094).
4141

4242
VLAN names aren't synchronized between the OT network sensor and the on-premises management console. If you want to view customized VLAN names on the on-premises management console, [define the VLAN names](how-to-manage-the-on-premises-management-console.md#define-vlan-names) there as well.
4343

0 commit comments

Comments
 (0)