Merge pull request #263259 from tarTech23/removeL60

remove l60 from articles

Author: v-regandowner

articles/defender-for-iot/organizations/legacy-central-management/back-up-sensors-from-management.md

@@ -38,13 +38,13 @@ For more information, see [Set up backup and restore files](../back-up-restore-s
 1. Enter the number of GB you want to allocate for backup storage. When the configured limit is exceeded, the oldest backup file is deleted.
 
     **If you're storing backup files on the on-premises management console**, supported values are defined based on your [hardware profiles](../ot-appliance-sizing.md). For example:
-    
+
     |Hardware profile  |Backup storage availability  |
     |---------|---------|
     |**E1800**     |Default storage is 40 GB; limit is 100 GB.        |
     |**L500**     |   Default storage is 20 GB; limit is 50 GB.     |
     |**L100**     |  Default storage is 10 GB; limit is 25 GB.       |
-    |**L60** [*](../ot-appliance-sizing.md#l60)        |    Default storage is 10 GB; limit is 25 GB.     |
+    |**L60**      |    Default storage is 10 GB; limit is 25 GB.     |
 
     **If you're storing backup files on an external server**, there's no maximum storage. However, keep in mind:
 

articles/defender-for-iot/organizations/ot-appliance-sizing.md

@@ -48,12 +48,11 @@ Use the following hardware profiles for production line monitoring, typically in
 |---------|---------|---------|---------|
 |L500   | Up to 200 Mbps        |   1,000      |Physical / Virtual         |
 |L100    | Up to 60 Mbps        |   800      | Physical / Virtual        |
-|L60    | Up to 10 Mbps        |   100      |Physical / Virtual|
 
 > [!IMPORTANT]
-> <a name="l60"></a>Upcoming Defender for IoT software versions are planned to require a minimum disk size of 100 GB. When that happens, the L60 hardware profile, which supports 60 GB of hard disk, will be deprecated.
+> Defender for IoT software versions require a minimum disk size of 100 GB. The L60 hardware profile, which only supports 60 GB of hard disk, has been deprecated.
 >
-> We recommend that you plan any new deployments accordingly, using hardware profiles that support at least 100 GB. Migration steps from the L60 hardware profile will be provided together with the L60 deprecation.
+> If you have a legacy sensor, such as the L60 hardware profile, you can migrate it to a supported profile can be found by following the [back up and restore a sensor](back-up-restore-sensor.md) process.
 
 ## On-premises management console systems
 

articles/defender-for-iot/organizations/ot-virtual-appliances.md

@@ -59,7 +59,6 @@ For all deployments, bandwidth results for virtual machines may vary, depending
 |**E500**     |    **Max bandwidth**: 800 Mb/sec <br>**Max monitored assets**: 10,000      | **vCPU**: 8 <br>**Memory**: 32 GB <br>**Storage**: 500 GB (300 IOPS)        |
 |**L500**     |   **Max bandwidth**: 160 Mb/sec <br>**Max monitored assets**: 1,000      | **vCPU**: 4 <br>**Memory**: 8 GB <br>**Storage**: 500 GB (150 IOPS)        |
 |**L100**     |    **Max bandwidth**: 100 Mb/sec <br>**Max monitored assets**: 800      | **vCPU**: 4 <br>**Memory**: 8 GB <br>**Storage**: 100 GB (150 IOPS)        |
-|**L60** [*](ot-appliance-sizing.md#l60) |     **Max bandwidth**: 10 Mb/sec <br>**Max monitored assets**: 100      | **vCPU**: 4 <br>**Memory**: 8 GB <br>**Storage**: 60 GB (150 IOPS)        |
 
 > [!NOTE]
 > There is no need to pre-install an operating system on the VM, the sensor installation includes the operating system image.

articles/defender-for-iot/organizations/references-data-retention.md

@@ -40,7 +40,7 @@ The following table lists how long PCAP data is stored in each Defender for IoT
 | Storage type | Details |
 |---------|---------|
 | **Azure portal** | PCAP files are available for download from the Azure portal for as long as the OT network sensor stores them. <br><br> Once downloaded, the files are cached on the Azure portal for 48 hours. <br><br> For more information, see [Access alert PCAP data](how-to-manage-cloud-alerts.md#access-alert-pcap-data). |
-| **OT network sensor** | Dependent on the sensor's storage capacity allocated for PCAP files, which is determined by its [hardware profile](ot-appliance-sizing.md): <br><br>- **C5600**:   130 GB  <br>- **E1800**:   130 GB  <br>-  **E1000** :   78 GB<br>- **E500**:    78 GB <br>- **L500**: 7 GB   <br>- **L100**:    2.5 GB<br>- **L60** [*](ot-appliance-sizing.md#l60):    2.5 GB    <br><br> If a sensor exceeds its maximum storage capacity, the oldest PCAP file is deleted to accommodate the new one. <br><br> For more information, see [Access alert PCAP data](how-to-view-alerts.md#access-alert-pcap-data) and [Pre-configured physical appliances for OT monitoring](ot-pre-configured-appliances.md). |
+| **OT network sensor** | Dependent on the sensor's storage capacity allocated for PCAP files, which is determined by its [hardware profile](ot-appliance-sizing.md): <br><br>- **C5600**:   130 GB  <br>- **E1800**:   130 GB  <br>-  **E1000** :   78 GB<br>- **E500**:    78 GB <br>- **L500**: 7 GB   <br>- **L100**:    2.5 GB<br><br> If a sensor exceeds its maximum storage capacity, the oldest PCAP file is deleted to accommodate the new one. <br><br> For more information, see [Access alert PCAP data](how-to-view-alerts.md#access-alert-pcap-data) and [Pre-configured physical appliances for OT monitoring](ot-pre-configured-appliances.md). |
 | **On-premises management console** | PCAP files aren't stored on the on-premises management console and are only accessed from the on-premises management console via a direct link to the OT sensor. |
 
 The usage of available PCAP storage space depends on factors such as the number of alerts, the type of the alert, and the network bandwidth, all of which affect the size of the PCAP file.
@@ -72,7 +72,6 @@ The following table lists the maximum number of events that can be stored for ea
 | **E500** | 6M events |
 | **L500** | 3M events |
 | **L100** | 500-K events |
-| **L60** [*](ot-appliance-sizing.md#l60) | 500-K events |
 
 For more information, see [Track sensor activity](how-to-track-sensor-activity.md) and [Pre-configured physical appliances for OT monitoring](ot-pre-configured-appliances.md).
 
@@ -105,7 +104,6 @@ The retention of backup files depends on the sensor's architecture, as each hard
 
 | Hardware profile  | Allocated hard disk space  |
 |---------|---------|
-| **L60** [*](ot-appliance-sizing.md#l60)    |  Backups are not supported       |
 | **L100**     |  Backups are not supported       |
 | **L500**     |  20 GB   |
 | **E1000** |   60 GB  |

articles/defender-for-iot/organizations/release-notes.md

@@ -113,9 +113,10 @@ This version includes the following updates and enhancements:
 
 - [Alert suppression rules from the Azure portal](how-to-accelerate-alert-incident-response.md#suppress-irrelevant-alerts)
 - [Focused alerts in OT/IT environments](alerts.md#focused-alerts-in-otit-environments)
-- [Alert ID (Id field) is now aligned on the Azure portal and sensor console](how-to-manage-cloud-alerts.md#view-alerts-on-the-azure-portal)
+- [Alert ID (ID field) is now aligned on the Azure portal and sensor console](how-to-manage-cloud-alerts.md#view-alerts-on-the-azure-portal)
 - [New setting to focus local networks in the device inventory](configure-sensor-settings-portal.md#configure-subnets-in-the-azure-portal)
 - [Newly supported protocols](concept-supported-protocols.md)
+- [L60 hardware profile is no longer supported](ot-appliance-sizing.md#production-line-monitoring-medium-and-small-deployments)
 
 ## Versions 23.2.x
 
@@ -475,5 +476,5 @@ This version includes the following new updates and fixes:
 
 ## Next steps
 
-For more information about the features listed in this article, see [What's new in Microsoft Defender for IoT?](whats-new.md) and [What's new archive for in Microsoft Defender for IoT for organizations](release-notes-archive.md).
+For more information about the features listed in this article, see [What's new in Microsoft Defender for IoT](whats-new.md) and [What's new archive for in Microsoft Defender for IoT for organizations](release-notes-archive.md).
 

articles/defender-for-iot/organizations/whats-new.md

@@ -20,7 +20,7 @@ Features released earlier than nine months ago are described in the [What's new
 
 |Service area  |Updates  |
 |---------|---------|
-| **OT networks** | - [Alert suppression rules from the Azure portal (Public preview)](#alert-suppression-rules-from-the-azure-portal-public-preview)<br>- [Focused alerts in OT/IT environments](#focused-alerts-in-otit-environments)<br>- [Alert ID now aligned on the Azure portal and sensor console](#alert-id-now-aligned-on-the-azure-portal-and-sensor-console)<br>- [New setting to focus local networks in the device inventory](#new-setting-to-focus-local-networks-in-the-device-inventory)<br>- [Newly supported protocols](#newly-supported-protocols)|
+| **OT networks** | - [Alert suppression rules from the Azure portal (Public preview)](#alert-suppression-rules-from-the-azure-portal-public-preview)<br>- [Focused alerts in OT/IT environments](#focused-alerts-in-otit-environments)<br>- [Alert ID now aligned on the Azure portal and sensor console](#alert-id-now-aligned-on-the-azure-portal-and-sensor-console)<br>- [New setting to focus local networks in the device inventory](#new-setting-to-focus-local-networks-in-the-device-inventory)<br>- [Newly supported protocols](#newly-supported-protocols)<br>- [L60 hardware profile is no longer supported](#l60-hardware-profile-is-no-longer-supported)|
 
 ### Alert suppression rules from the Azure portal (Public preview)
 
@@ -68,6 +68,12 @@ We now support these protocols:
 
 [See the updated protocol list](concept-supported-protocols.md).
 
+### L60 hardware profile is no longer supported
+
+The L60 hardware profile is no longer supported and is removed from support documentation. Hardware profiles now require a minimum of 100GB (the minimum hardware profile is now [L100](ot-virtual-appliances.md)).
+
+To migrate from the L60 profile to a supported profile follow the [Back up and restore OT network sensor](back-up-restore-sensor.md) procedure.
+
 ## January 2024
 
 |Service area  |Updates  |