Updated to address PR build warnings and errors.

Author: LouisBerner

azure-local/concepts/software-defined-networking-23h2.md

@@ -5,7 +5,7 @@ author: AnirbanPaul
 ms.author: anpaul
 ms.topic: conceptual
 ms.service: azure-local
-ms.date: 01/29/2025
+ms.date: 05/28/2025
 ---
 
 # Software Defined Networking (SDN) in Azure Local
@@ -29,7 +29,7 @@ Deploying Network Controller enables the following functionalities:
 - Attach virtual appliances to your virtual networks.
 - Configure Quality of Service (QoS) policies for VMs attached to virtual networks or traditional VLAN-based networks.
 
-You have the option to [deploy SDN Network Controller using SDN Express](../manage/sdn-express.md) PowerShell scripts, or [deploy SDN Network Controller using Windows Admin Center](../deploy/sdn-wizard-23h2.md) after creating a system.
+You have the option to deploy an SDN Network Controller using SDN Express PowerShell scripts, or [deploy SDN Network Controller using Windows Admin Center](../deploy/sdn-wizard-23h2.md) after creating a system.
 
 ## Software Load Balancing
 

azure-local/includes/azure-local-banner-22h2.md

@@ -0,0 +1,11 @@
+---
+author: alkohli
+ms.author: alkohli
+ms.service: azure-local
+ms.topic: include
+ms.date: 01/24/2025
+ms.reviewer: alkohli
+---
+
+> [!IMPORTANT]
+> Azure Stack HCI is now part of Azure Local. However, older versions of Azure Stack HCI, for example 22H2 will continue to reference Azure Stack HCI and won't reflect the name change. [Learn more](https://aka.ms/azloc-promo).

azure-local/includes/hci-applies-to-22h2.md

@@ -0,0 +1,10 @@
+---
+author: alkohli
+ms.author: alkohli
+ms.service: azure-local
+ms.topic: include
+ms.date: 01/08/2025
+ms.reviewer: alkohli
+---
+
+> Applies to: Azure Stack HCI, version 22H2

azure-local/manage/configure-network-security-groups-with-tags.md

@@ -7,7 +7,7 @@ ms.topic: article
 author: alkohli
 ms.subservice: 
 zone_pivot_groups: windows-os
-ms.date: 01/28/2025
+ms.date: 05/28/2025
 ---
 
 # Configure network security groups with tags in Windows Admin Center
@@ -50,7 +50,7 @@ Complete the following prerequisites to use network security groups with tags:
 
 - You have Windows Server 2025 or later. For more information, see [Get started with Windows Server](/windows-server/get-started/get-started-with-windows-server).
 
-- You have a Network Controller installed. For more information, see how to [Deploy an SDN infrastructure using SDN Express](sdn-express.md?context=/windows-server/context/windows-server-edge-networking).
+- You have a Network Controller installed. For more information, see how to Deploy an SDN infrastructure using SDN Express.
 
 - You have a logical network or a virtual network to use. For more information, see how to [Create a logical network](./tenant-logical-networks.md?context=/windows-server/context/windows-server-failover-clustering) or [Create a virtual network](./tenant-virtual-networks.md?context=/windows-server/context/windows-server-failover-clustering).
 

azure-local/manage/manage-default-network-access-policies-virtual-machines-23h2.md

@@ -7,7 +7,7 @@ ms.topic: article
 author: alkohli
 ms.service: azure-local
 zone_pivot_groups: windows-os
-ms.date: 01/28/2025
+ms.date: 05/28/2025
 ---
 
 # Use default network access policies on virtual machines on Azure Local
@@ -106,27 +106,27 @@ Here's an example that explains how you can attach your VM directly to a VLAN wh
 
 1. When creating a VM, attach it to the logical network and logical network subnet created earlier. For more information, see how to [Create a logical network](./tenant-logical-networks.md).
 
-    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines/attach-vm-logical-network-1.png" alt-text="Screenshot showing how to attach VM directly to VLAN." lightbox="./media/manage-default-network-access-policies-virtual-machines/attach-vm-logical-network-1.png":::
+    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines-23h2/attach-vm-logical-network-1.png" alt-text="Screenshot showing how to attach VM directly to VLAN." lightbox="./media/manage-default-network-access-policies-virtual-machines-23h2/attach-vm-logical-network-1.png":::
 
 ### Apply default network policies
 
 When you create a VM through Windows Admin Center, you see a **Security level** setting.
 
-:::image type="content" source="./media/manage-default-network-access-policies-virtual-machines/security-level-2.png" alt-text="Screenshot showing the three security level options for VMs in Windows Admin Center." lightbox="./media/manage-default-network-access-policies-virtual-machines/security-level-2.png":::
+:::image type="content" source="./media/manage-default-network-access-policies-virtual-machines-23h2/security-level-2.png" alt-text="Screenshot showing the three security level options for VMs in Windows Admin Center." lightbox="./media/manage-default-network-access-policies-virtual-machines-23h2/security-level-2.png":::
 
 You have three options:
 
 - **No protection** - Choose this option if you don't want to enforce any network access policies to your VM. When this option is selected, all ports on your VM are exposed to external networks posing a security risk. This option isn't recommended.
 
-    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines/no-protection-1.png" alt-text="Screenshot showing the No protection option selected for VMs in Windows Admin Center." lightbox="./media/manage-default-network-access-policies-virtual-machines/no-protection-1.png":::
+    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines-23h2/no-protection-1.png" alt-text="Screenshot showing the No protection option selected for VMs in Windows Admin Center." lightbox="./media/manage-default-network-access-policies-virtual-machines-23h2/no-protection-1.png":::
 
 - **Open some ports** - Choose this option to go with default policies. The default policies block all inbound access and allow all outbound access. You can optionally enable inbound access to one or more well defined ports, for example, HTTP, HTTPS, SSH, or RDP as per your requirements.
 
-    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines/ports-to-open-1.png" alt-text="Screenshot showing the ports that can be opened on VMs specified during VM creation in Windows Admin Center." lightbox="./media/manage-default-network-access-policies-virtual-machines/ports-to-open-1.png":::
+    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines-23h2/ports-to-open-1.png" alt-text="Screenshot showing the ports that can be opened on VMs specified during VM creation in Windows Admin Center." lightbox="./media/manage-default-network-access-policies-virtual-machines-23h2/ports-to-open-1.png":::
 
 - **Use existing NSG** - Choose this option to apply custom policies. You specify a Network Security Group (NSG) that you've already created.
 
-    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines/use-existing-nsg-1.png" alt-text="Screenshot showing the existing network security group selected during VM creation in Windows Admin Center." lightbox="./media/manage-default-network-access-policies-virtual-machines/use-existing-nsg-1.png":::
+    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines-23h2/use-existing-nsg-1.png" alt-text="Screenshot showing the existing network security group selected during VM creation in Windows Admin Center." lightbox="./media/manage-default-network-access-policies-virtual-machines-23h2/use-existing-nsg-1.png":::
 
 ## VMs created outside of Windows Admin Center
 
@@ -173,7 +173,7 @@ You might encounter issues when you create VMs outside of Windows Admin Center a
 
     [!INCLUDE [hci-display-correct-default-network-policies-windows](../includes/hci-display-correct-default-network-policies-windows.md)]
 
-    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines/enable-policies-other-vms-1.png" alt-text="Screenshot showing how to enable default network to VLAN." lightbox="./media/manage-default-network-access-policies-virtual-machines/enable-policies-other-vms-1.png":::
+    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines-23h2/enable-policies-other-vms-1.png" alt-text="Screenshot showing how to enable default network to VLAN." lightbox="./media/manage-default-network-access-policies-virtual-machines-23h2/enable-policies-other-vms-1.png":::
 
 ::: zone-end
 
@@ -185,7 +185,7 @@ You might encounter issues when you create VMs outside of Windows Admin Center a
 
     [!INCLUDE [hci-display-correct-default-network-policies-windows](../includes/hci-display-correct-default-network-policies-windows.md)]
 
-    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines/enable-policies-other-vms-1.png" alt-text="Screenshot showing how to enable default network to VLAN." lightbox="./media/manage-default-network-access-policies-virtual-machines/enable-policies-other-vms-1.png":::
+    :::image type="content" source="./media/manage-default-network-access-policies-virtual-machines-23h2/enable-policies-other-vms-1.png" alt-text="Screenshot showing how to enable default network to VLAN." lightbox="./media/manage-default-network-access-policies-virtual-machines-2/enable-policies-other-vms-1.png":::
 
 ::: zone-end
 

azure-local/manage/manage-sdn-multisite.md

@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.subservice: 
 zone_pivot_groups: windows-os
-ms.date: 01/28/2025
+ms.date: 05/28/2025
 ---
 
 # Manage SDN Multisite for Azure Local and Windows Server
@@ -49,7 +49,7 @@ Before you can enable SDN Multisite, ensure the following prerequisites are met:
 
 - There must be an underlying [physical network connectivity](../concepts/plan-software-defined-networking-infrastructure.md#physical-and-logical-network-configuration) between the sites. Additionally, the provider network name must be the same on both sites.
 
-- SDN must be installed on both sites separately, using [Windows Admin Center](../deploy/sdn-wizard.md) or [SDN Express scripts](./sdn-express.md). Separate sites are required so that the SDN components, such as Network Controller VMs, Software Load Balancer Multiplexor VMs, and SDN Gateway VMs are unique to each site.
+- SDN must be installed on both sites separately, using [Windows Admin Center](../deploy/sdn-wizard.md) or SDN Express scripts. Separate sites are required so that the SDN components, such as Network Controller VMs, Software Load Balancer Multiplexor VMs, and SDN Gateway VMs are unique to each site.
 
 ::: zone-end
 
@@ -59,7 +59,7 @@ Before you can enable SDN Multisite, ensure the following prerequisites are met:
 
 - There must be an underlying [physical network connectivity](../concepts/plan-software-defined-networking-infrastructure.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking#physical-and-logical-network-configuration) between the sites. Additionally, the provider network name must be the same on both sites.
 
-- SDN must be installed on both sites separately, using [Windows Admin Center](../deploy/sdn-wizard.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking) or [SDN Express scripts](./sdn-express.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking). Separate sites are required so that the SDN components, such as Network Controller VMs, Software Load Balancer Multiplexor VMs, and SDN Gateway VMs are unique to each site.
+- SDN must be installed on both sites separately, using [Windows Admin Center](../deploy/sdn-wizard.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking) or SDN Express scripts. Separate sites are required so that the SDN components, such as Network Controller VMs, Software Load Balancer Multiplexor VMs, and SDN Gateway VMs are unique to each site.
 
 ::: zone-end