Merge pull request #302252 from dominicbetts/aio-lnm-note

prmerger-automator[bot] · web-flow · commit 35c90af0f1d0 · 2025-07-04T09:45:02.000Z
AIO: Add LNM retirement notice
diff --git a/articles/iot-operations/manage-layered-network/concept-iot-operations-in-layered-network.md b/articles/iot-operations/manage-layered-network/concept-iot-operations-in-layered-network.md
@@ -15,6 +15,8 @@ ms.service: azure-iot-operations
 
 You can deploy Azure IoT Operations in a layered network environment by using the Azure IoT Layered Network Management (preview) service. This service enables Azure IoT Operations to function in industrial network environments that have multiple isolated network layers.
 
+[!INCLUDE [retirement-notice](includes/retirement-notice.md)]
+
 ## Industrial scenario for Azure IoT Operations
 
 In the basic architecture described in [Azure IoT Operations Architecture Overview](../overview-iot-operations.md#architecture-overview), all the Azure IoT Operations components are deployed to a single internet-connected cluster. In this type of environment, component-to-component and component-to-Azure connections are enabled by default.
diff --git a/articles/iot-operations/manage-layered-network/howto-configure-aks-edge-essentials-layered-network.md b/articles/iot-operations/manage-layered-network/howto-configure-aks-edge-essentials-layered-network.md
@@ -17,6 +17,8 @@ ms.service: azure-iot-operations
 
 This walkthrough is an example of deploying Azure IoT Operations to a special environment that's different than the default [Azure IoT Operations scenario](../get-started-end-to-end-sample/quickstart-deploy.md). By default, Azure IoT Operations is deployed to an Arc-enabled cluster that has direct internet access. In this scenario, you deploy Azure IoT Operations to an isolated network environment. The hardware and cluster must meet the prerequisites of Azure IoT Operations and there are extra configurations for the network, host OS, and cluster. As a result, the Azure IoT Operations components run and connect to Arc through the Azure IoT Layered Network Management (preview) service.
 
+[!INCLUDE [retirement-notice](includes/retirement-notice.md)]
+
 >[!IMPORTANT]
 > This is an advanced scenario for Azure IoT Operations. You should complete the following steps to get familiar with the basic concepts before you start this advanced scenario.
 > - [Deploy Azure IoT Layered Network Management to an AKS cluster](howto-deploy-aks-layered-network.md)
diff --git a/articles/iot-operations/manage-layered-network/howto-configure-l3-cluster-layered-network.md b/articles/iot-operations/manage-layered-network/howto-configure-l3-cluster-layered-network.md
@@ -23,6 +23,8 @@ You'll complete the following tasks:
 - Use a customized DNS setting to direct the network traffic to the Layered Network Management service in parent level.
 - Arc-enable the cluster.
 
+[!INCLUDE [retirement-notice](includes/retirement-notice.md)]
+
 ## Prerequisites
 
 Follow the guidance for **hardware requirements** and **prerequisites** sections in [Prepare your Azure Arc-enabled Kubernetes cluster](../deploy-iot-ops/howto-prepare-cluster.md).
diff --git a/articles/iot-operations/manage-layered-network/howto-configure-l4-cluster-layered-network.md b/articles/iot-operations/manage-layered-network/howto-configure-l4-cluster-layered-network.md
@@ -16,6 +16,8 @@ ms.service: azure-iot-operations
 
 Azure IoT Layered Network Management (preview) is a component to support Azure IoT Operations. However, it needs to be deployed individually to the top network layer for supporting the Azure IoT Operations in the lower layer. In the top level of your network layers (usually level 4 of the ISA-95 network architecture), the cluster and Layered Network Management service have direct internet access. Once the setup is completed, the Layered Network Management (preview) service is ready for receiving network traffic from the child layer and forwards it to Azure Arc.
 
+[!INCLUDE [retirement-notice](includes/retirement-notice.md)]
+
 ## Prerequisites
 Meet the following minimum requirements for deploying the Layered Network Management individually on the system.
 - **AKS Edge Essentials** - *Arc-connected cluster and GitOps* category in [AKS Edge Essentials requirements and support matrix](/azure/aks/hybrid/aks-edge-system-requirements)
diff --git a/articles/iot-operations/manage-layered-network/howto-configure-layered-network.md b/articles/iot-operations/manage-layered-network/howto-configure-layered-network.md
@@ -21,6 +21,8 @@ To use Azure IoT Layered Network Management (preview) service, you need to confi
 
 Both approaches require you to configure a custom DNS in the isolated network layer to direct the network traffic to the Layered Network Management instance in upper layer.
 
+[!INCLUDE [retirement-notice](includes/retirement-notice.md)]
+
 > [!IMPORTANT]
 > The network environments outlined in Layered Network Management documentation are examples for testing the Layered Network Management. It's not a recommendation of how you build your network and cluster topology for production.
 
diff --git a/articles/iot-operations/manage-layered-network/howto-connect-arc-enabled-servers.md b/articles/iot-operations/manage-layered-network/howto-connect-arc-enabled-servers.md
@@ -15,6 +15,8 @@ ms.service: azure-iot-operations
 
 This walkthrough is an example of connecting your host machine to Azure Arc as an [Arc-enabled server](/azure/azure-arc/servers) from an isolated network environment. For example, level 3 of the *Purdue Network*. You connect the host machine to Azure IoT Layered Network Management (preview) at the parent level as a proxy to reach Azure endpoints for the service. You can integrate these steps into your procedure to set up your cluster for Azure IoT Operations. Don't use this guidance independently. For more information, see [Configure Layered Network Management (preview) service to enable Azure IoT Operations in an isolated network](howto-configure-aks-edge-essentials-layered-network.md).
 
+[!INCLUDE [retirement-notice](includes/retirement-notice.md)]
+
 > [!IMPORTANT]
 > **Arc-enabled servers** aren't a requirement for the Azure IoT Operations experiences. You should evaluate your own design and only enable this service if it suits your needs. Before proceeding with these steps, you should also get familiar with the **Arc-enabled servers** by trying this service with a machine that has direct internet access.
 
diff --git a/articles/iot-operations/manage-layered-network/howto-deploy-aks-layered-network.md b/articles/iot-operations/manage-layered-network/howto-deploy-aks-layered-network.md
@@ -21,8 +21,10 @@ In this quickstart, you set up the Azure IoT Layered Network Management (preview
 
 The Layered Network Management architecture requires DNS configuration on the level 3 network, where the allowlisted URLs are repointed to the level 4 network. In this example, this setup is accomplished using an automated setup that's built on CoreDNS, the default DNS resolution mechanism that ships with k3s.
 
+[!INCLUDE [retirement-notice](includes/retirement-notice.md)]
 
 ## Prerequisites
+
 These prerequisites are only for deploying the Layered Network Management independently and Arc-enable the child level cluster.
 
 - An [AKS cluster](/azure/aks/learn/quick-kubernetes-deploy-portal)
