remove cm mentions

Author: tarTech23

articles/defender-for-iot/organizations/architecture.md

@@ -21,8 +21,6 @@ Defender for IoT includes the following OT security monitoring components:
 
 - **Operational technology (OT) or Enterprise IoT network sensors**, to detect devices across your network. Defender for IoT network sensors are deployed on either a virtual machine or a physical appliance. OT sensors can be configured as cloud-connected sensors, or fully on-premises, locally managed sensors.
 
-- **An on-premises management console** for centralized OT sensor management and monitoring for local, air-gapped environments.
-
 ## OT and Enterprise IoT network sensors
 
 Defender for IoT network sensors discover and continuously monitor network traffic across your network devices.
@@ -31,7 +29,7 @@ Defender for IoT network sensors discover and continuously monitor network traff
 
 - Network sensors use OT/IoT-aware analytics engines and Layer-6 Deep Packet Inspection (DPI) to detect threats, such as fileless malware, based on anomalous or unauthorized activity.
 
-Data collection, processing, analysis, and alerting takes place directly on the sensor, which can be ideal for locations with low bandwidth or high-latency connectivity. Only telemetry and insights are transferred on for management, either to the Azure portal or an on-premises management console.
+Data collection, processing, analysis, and alerting takes place directly on the sensor, which can be ideal for locations with low bandwidth or high-latency connectivity. Only telemetry and insights are transferred on for management to the Azure portal.
 
 For more information, see [Defender for IoT OT deployment path](ot-deploy/ot-deploy-path.md).
 
@@ -49,13 +47,13 @@ Cloud-connected sensors are sensors that are connected to Defender for IoT in Az
 
 **In contrast, when working with locally managed sensors**:
 
-- View any data for a specific sensor from the sensor console. For a unified view of all information detected by several sensors, use an on-premises management console.
+- View any data for a specific sensor from the sensor console.
 
 - You must manually upload any threat intelligence packages to locally managed sensors.
 
 - Sensor names can be updated in the sensor console.
 
-For more information, see [Manage OT sensors from the sensor console](how-to-manage-individual-sensors.md) and [Manage OT sensors from the management console](legacy-central-management/how-to-manage-sensors-from-the-on-premises-management-console.md).
+For more information, see [Manage OT sensors from the sensor console](how-to-manage-individual-sensors.md).
 
 ### Defender for IoT analytics engines
 
@@ -91,12 +89,6 @@ Defender for IoT provides hybrid network support using the following management
 
     :::image type="content" source="media/release-notes/new-interface.png" alt-text="Screenshot that shows the updated interface." lightbox="media/release-notes/new-interface.png":::
 
-- **The on-premises management console**. In air-gapped environments, you can get a central view of data from all of your sensors from an on-premises management console, using extra maintenance tools and reporting features.
-
-    The software version on your on-premises management console must be equal to that of your most up-to-date sensor version. Each on-premises management console version is backwards compatible to older, supported sensor versions, but cannot connect to newer sensor versions.
-
-    For more information, see [Air-gapped OT sensor management deployment path](ot-deploy/air-gapped-deploy.md).
-
 ## Devices monitored by Defender for IoT
 
 [!INCLUDE [devices-inventoried](includes/devices-inventoried.md)]

articles/defender-for-iot/organizations/cli-ot-sensor.md

@@ -124,7 +124,7 @@ Use the following commands to turn on synchronization for the appliance time wit
 To use these commands, make sure that:
 
 - The NTP server can be reached from the appliance management port
-- You use the same NTP server to synchronize all sensor appliances and the on-premises management console
+- You use the same NTP server to synchronize all sensor appliances
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|

articles/defender-for-iot/organizations/concept-zero-trust.md

@@ -73,12 +73,9 @@ For example, if your growing company has factories and offices in Paris, Lagos,
 |**Dubai office**     |     - Ground floor (Convention center) <br>- Floor 1 (Sales)<br>- Floor 2 (Offices)     |
 |**Tianjin office**     |   - Ground floor (Offices) <br>- Floors 1-2 (Factory)        |
 
-
 ## Next steps
 
-Create sites and zones as you onboard OT sensors in the Azure portal, and assign site-based access policies to your Azure users. 
-
-If you're working in an air-gapped environment with an on-premises management console, create OT site and zones directly on the on-premises management console.
+Create sites and zones as you onboard OT sensors in the Azure portal, and assign site-based access policies to your Azure users.
 
 Use built-in Defender for IoT workbooks and create custom workbooks of your own to monitor your security perimeter over time.
 

articles/defender-for-iot/organizations/detect-windows-endpoints-script.md

@@ -11,7 +11,7 @@ ms.topic: how-to
 > This feature is in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include other legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 >
 
-In addition to detecting OT devices on your network, use Defender for IoT to discover Microsoft Windows workstations and servers and enrich workstation and server data for devices already detected. Same as other detected devices, detected Windows workstations and servers are displayed in the Device inventory. The **Device inventory** pages on the sensor and on-premises management console show enriched data about Windows devices, including data about the Windows operating system and applications installed, patch-level data, open ports, and more.
+In addition to detecting OT devices on your network, use Defender for IoT to discover Microsoft Windows workstations and servers and enrich workstation and server data for devices already detected. Same as other detected devices, detected Windows workstations and servers are displayed in the Device inventory. The **Device inventory** pages on the sensor show enriched data about Windows devices, including data about the Windows operating system and applications installed, patch-level data, open ports, and more.
 
 This article describes how to use a Defender for IoT Windows-based WMI tool to get extended information from Windows devices, such as workstations, servers, and more. Run the WMI script on your Windows devices to get extended information, increasing your device inventory and security coverage. While you can also use [scheduled WMI scans](configure-windows-endpoint-monitoring.md) to obtain this data, scripts can be run locally for regulated networks with waterfalls and one-way elements if WMI connectivity isn't possible.
 

articles/defender-for-iot/organizations/device-inventory.md

@@ -1,6 +1,6 @@
 ---
 title: Device inventory - Microsoft Defender for IoT
-description: Learn about the Defender for IoT device inventory features available from the Azure portal, OT sensor console, and the on-premises management console.
+description: Learn about the Defender for IoT device inventory features available from the Azure portal, and OT sensor console.
 ms.date: 02/19/2023
 ms.topic: conceptual
 ---
@@ -47,14 +47,12 @@ Defender for IoT device inventory is available in the following locations:
 |**Azure portal**     | OT devices detected from all cloud-connected OT sensors.      |     - If you also use [Microsoft Sentinel](iot-solution.md), incidents in Microsoft Sentinel are linked to related devices in Defender for IoT. <br><br>- Use Defender for IoT [workbooks](workbooks.md) for visibility into all cloud-connected device inventory, including related alerts and vulnerabilities.    <br><br>- If you have a [legacy Enterprise IoT plan](whats-new.md#enterprise-iot-protection-now-included-in-microsoft-365-e5-and-e5-security-licenses) on your Azure subscription, the Azure portal also includes devices detected by Microsoft Defender for Endpoint agents. If you have an [Enterprise IoT sensor](eiot-sensor.md), the Azure portal also includes devices detected by the Enterprise IoT sensor.   |
 | **Microsoft Defender XDR** | Enterprise IoT devices detected by Microsoft Defender for Endpoint agents | Correlate devices across Microsoft Defender XDR in purpose-built alerts, vulnerabilities, and recommendations. |
 |**OT network sensor consoles**     |   Devices detected by that OT sensor      |    - View all detected devices across a network device map<br><br>- View related events on the **Event timeline** |
-|**An on-premises management console**     |  Devices detected across all connected OT sensors          | Enhance device data by importing data manually or via script  |
 
 For more information, see:
 
 - [Manage your device inventory from the Azure portal](how-to-manage-device-inventory-for-organizations.md)
 - [Defender for Endpoint device discovery](/microsoft-365/security/defender-endpoint/device-discovery)
 - [Manage your OT device inventory from a sensor console](how-to-investigate-sensor-detections-in-a-device-inventory.md)
-- [Manage your OT device inventory from an on-premises management console](legacy-central-management/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md)
 
 ## Automatically consolidated devices
 
@@ -158,6 +156,5 @@ For more information, see:
 
 - [Manage your device inventory from the Azure portal](how-to-manage-device-inventory-for-organizations.md)
 - [Manage your OT device inventory from a sensor console](how-to-investigate-sensor-detections-in-a-device-inventory.md)
-- [Manage your OT device inventory from an on-premises management console](legacy-central-management/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md)
 - [Microsoft Defender for IoT - supported IoT, OT, ICS, and SCADA protocols](concept-supported-protocols.md)
 - [Investigate devices on a device map](how-to-work-with-the-sensor-device-map.md)

articles/defender-for-iot/organizations/how-to-control-what-traffic-is-monitored.md

@@ -21,7 +21,7 @@ Before performing the procedures in this article, you must have:
 
 - An OT network sensor [installed](ot-deploy/install-software-ot-sensor.md), [configured, and activated](ot-deploy/activate-deploy-sensor.md).
 
-- Access to your OT network sensor and on-premises management console as an **Admin** user.  For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
+- Access to your OT network sensor as an **Admin** user.  For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
 
 This step is performed by your deployment teams.
 
@@ -142,9 +142,6 @@ VLANs are either discovered automatically by the OT network sensor or added manu
 
 VLAN's support is based on 802.1q (up to VLAN ID 4094).
 
-> [!NOTE]
-> 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](legacy-central-management/how-to-manage-the-on-premises-management-console.md#define-vlan-names) there as well.
-
 **To configure VLAN names on an OT network sensor:**
 
 1. Sign in to your OT sensor as an **Admin** user.

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

@@ -10,7 +10,7 @@ ms.custom: enterprise-iot
 
 Microsoft Defender for IoT alerts enhance your network security and operations with real-time details about events logged in your network. This article describes how to manage Microsoft Defender for IoT alerts on the Azure portal, including alerts generated by OT and Enterprise IoT network sensors.
 
-- OT alerts are also available on each [OT network sensor console](how-to-view-alerts.md), or a connected [on-premises management console](legacy-central-management/how-to-work-with-alerts-on-premises-management-console.md)
+- OT alerts are also available on each [OT network sensor console](how-to-view-alerts.md).
 
 - [Integrate with Microsoft Sentinel](iot-solution.md) to view Defender for IoT alerts in Microsoft Sentinel and manage them together with security incidents.
 

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

@@ -81,7 +81,6 @@ Use the options on the **Sites and sensor** page and a sensor details page to do
 |Task |Description  |
 |---------|---------|
 |:::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/icon-recover.png" border="false"::: **Recover a OT sensor password**     | Individual, OT sensors only. <br><br>Available from the **...** options menu or a sensor details page. Enter the secret identifier obtained on the sensor's sign-in screen.      |
-| **Recover an on-premises management console password** | Available from the **Sites and sensors** toolbar **More actions** menu. <br><br>For more information, see [Manage the on-premises management console](legacy-central-management/how-to-manage-the-on-premises-management-console.md). |
 |:::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/icon-export.png" border="false"::: **Download an activation file**     |   Individual, OT sensors only. <br><br>Available from the **...** options menu or a sensor details page.      |
 |:::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/icon-edit.png" border="false"::: **Edit a sensor zone**     |    For individual sensors only, from the **...** options menu or a sensor details page.  <br><br>Select **Edit**, and then select a new zone from the **Zone** menu or select **Create new zone**. Select **Submit** to save your changes.    |
 | **Download SNMP MIB file** | Available from the **Sites and sensors** toolbar **More actions** menu. <br><br>For more information, see [Set up SNMP MIB health monitoring on an OT sensor](how-to-set-up-snmp-mib-monitoring.md).|
@@ -92,7 +91,7 @@ Use the options on the **Sites and sensor** page and a sensor details page to do
 
 |Task |Description  |
 |---------|---------|
-| :::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/icon-settings.png" border="false"::: **Sensor settings (Preview)** | OT sensors only. <br><br> Define selected sensor settings for one or more cloud-connected OT network sensors. For more information, see [Define and view OT sensor settings from the Azure portal (Public preview)](configure-sensor-settings-portal.md). <br><br>Other settings are also available directly from the [OT sensor console](how-to-manage-individual-sensors.md), or the [on-premises management console](legacy-central-management/how-to-manage-sensors-from-the-on-premises-management-console.md).|
+| :::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/icon-settings.png" border="false"::: **Sensor settings (Preview)** | OT sensors only. <br><br> Define selected sensor settings for one or more cloud-connected OT network sensors. For more information, see [Define and view OT sensor settings from the Azure portal (Public preview)](configure-sensor-settings-portal.md). <br><br>Other settings are also available directly from the [OT sensor console](how-to-manage-individual-sensors.md).|
 |:::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/icon-export.png" border="false"::: **Export sensor data**     |  Available from the **Sites and sensors** toolbar only, to download a CSV file with details about all the sensors listed.       |
 |:::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/icon-delete.png" border="false"::: **Delete a sensor**    |   For individual sensors only, from the **...** options menu or a sensor details page.      |
 | :::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/icon-diagnostics.png" border="false"::: **Send diagnostic files to support** | Individual, locally managed OT sensors only. <br><br>Available from the **...** options menu. <br><br>For more information, see [Upload a diagnostics log for support](#upload-a-diagnostics-log-for-support).|

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

@@ -62,14 +62,9 @@ This procedure describes how to add an OT plan for Defender for IoT in the Azure
 
 1. Select **Next** and review the details for any of your licensed sites. The details listed on the **Review and purchase** pane reflect any licenses you've purchased from the Microsoft 365 admin center.
 
-1. Do one or both of the following:
+1. Select the terms and conditions.
 
-   - Select the terms and conditions.
-   - If you're working with an on-premises management console, select **Download OT activation file (Optional)**.
-
-   When you're finished, select **Save**. If you've selected to download the on-premises management console activation file, the file is downloaded and you're prompted to save it locally. You'll use it later, when [activating your on-premises management console](legacy-central-management/activate-deploy-management.md#activate-the-on-premises-management-console).
-
-   [!INCLUDE [on-premises-management-deprecation](includes/on-premises-management-deprecation.md)]
+1. When you're finished, select **Save**.
 
 Your new plan is listed under the relevant subscription on the **Plans and pricing** > **Plans** page.
 
@@ -182,9 +177,8 @@ If you have multiple legacy subscriptions and are migrating to a Microsoft 365 p
 
 1. After any changes are made, make sure to reactivate your sensors. For more information, see [Reactivate an OT sensor](how-to-manage-sensors-on-the-cloud.md#reactivate-an-ot-sensor).
 
-1. If you have an on-premises management console, make sure to upload a new activation file, which reflects the changes made. For more information, see [Upload a new activation file](legacy-central-management/how-to-manage-the-on-premises-management-console.md#upload-a-new-activation-file).
-
 Changes to your plan will take effect one hour after confirming the change. This change appears on your next monthly statement, and you're charged based on the length of time each plan was in effect.
+
 ## Next steps
 
 For more information, see:

articles/defender-for-iot/organizations/how-to-view-alerts.md

@@ -9,7 +9,7 @@ ms.topic: how-to
 
 Microsoft Defender for IoT alerts enhance your network security and operations with real-time details about events logged in your network. OT alerts are triggered when OT network sensors detect changes or suspicious activity in network traffic that needs your attention.
 
-This article describes how to view Defender for IoT alerts directly on an OT network sensor. You can also view OT alerts on the [Azure portal](how-to-manage-cloud-alerts.md) or an [on-premises management console](legacy-central-management/how-to-work-with-alerts-on-premises-management-console.md).
+This article describes how to view Defender for IoT alerts directly on an OT network sensor. You can also view OT alerts on the [Azure portal](how-to-manage-cloud-alerts.md).
 
 For more information, see [Microsoft Defender for IoT alerts](alerts.md).