Sync release-local-disconnectednew with main

Sync release-local-disconnectednew with main

Author: sethmanheim

AKS-Arc/aks-hci-network-system-requirements.md

@@ -2,11 +2,11 @@
 title: AKS enabled by Azure Arc network requirements
 description: Learn about AKS network prerequisites.
 ms.topic: overview
-ms.date: 04/23/2025
+ms.date: 07/02/2025
 author: sethmanheim
 ms.author: sethm
-ms.reviewer: abha
-ms.lastreviewed: 04/02/2024
+ms.reviewer: srikantsarwa
+ms.lastreviewed: 07/10/2025
 ---
 
 # AKS enabled by Azure Arc network requirements
@@ -42,7 +42,7 @@ The following parameters are required in order to use a logical network for AKS
 
 ### Control plane IP
 
-Kubernetes uses a control plane to ensure every component in the Kubernetes cluster is kept in the desired state. The control plane also manages and maintains the worker nodes that hold the containerized applications. AKS enabled by Arc deploys the KubeVIP load balancer to ensure that the API server IP address of the Kubernetes control plane is available at all times. This KubeVIP instance requires a single immutable "control plane IP address" to function correctly. AKS Arc automatically chooses a control plane IP for you from the logical network passed during the Kubernetes cluster create operation.
+Kubernetes uses a control plane to ensure every component in the Kubernetes cluster is kept in the desired state. The control plane also manages and maintains the worker nodes that hold the containerized applications. AKS enabled by Arc deploys the KubeVIP load balancer to ensure that the API server IP address of the Kubernetes control plane is always available. This KubeVIP instance requires a single immutable "control plane IP address" to function correctly. AKS Arc automatically chooses a control plane IP for you from the logical network passed during the Kubernetes cluster create operation.
 
 You also have the option of passing a control plane IP. In such cases, the control plane IP must be within the scope of the address prefix of the logical network. You must ensure that the control plane IP address does not overlap with anything else, including Arc VM logical networks, infrastructure network IPs, load balancers, etc. Overlapping IP addresses can lead to unexpected failures for both the AKS cluster and any other place the IP address is being used. You must plan to reserve one IP address per Kubernetes cluster in your environment.
 
@@ -73,7 +73,7 @@ Firewall requirements for AKS have been consolidated with Azure Local firewall r
 
 ## DNS server settings
 
-You need to ensure that the DNS server of the logical network can resolve the FQDN of the Azure Local cluster. DNS name resolution is required for all Azure Local nodes to be able to communicate with the AKS VM nodes. 
+You need to ensure that the DNS server of the logical network can resolve the FQDN of the Azure Local cluster. DNS name resolution is required for all Azure Local nodes to be able to communicate with the AKS VM nodes.
 
 ## Network port and cross-VLAN requirements
 

AKS-Arc/ssh-connect-to-windows-and-linux-worker-nodes.md

@@ -1,7 +1,7 @@
 ---
 title: Connect to Windows or Linux worker nodes with SSH
 description: Learn how to use SSH to connect to Windows or Linux worker nodes in an AKS Arc cluster.
-ms.date: 07/02/2025
+ms.date: 07/10/2025
 ms.topic: how-to
 author: sethmanheim
 ms.author: sethm
@@ -39,6 +39,8 @@ You can use the Kubernetes CLI, [**kubectl**](https://kubernetes.io/docs/referen
   Install-AzAksCliTool
   ```
 
+---
+
 ## Use SSH to connect to worker nodes
 
 1. To access the Kubernetes cluster with the specified permissions, you must retrieve the certificate-based admin **kubeconfig** file using the [az aksarc get-credentials](/cli/azure/aksarc#az-aksarc-get-credentials) command. For more information, see [Retrieve certificate-based admin kubeconfig](retrieve-admin-kubeconfig.md):

azure-local/includes/hci-vm-image-prerequisites-storage-account.md

@@ -3,7 +3,7 @@ author: alkohli
 ms.author: alkohli
 ms.service: azure-local
 ms.topic: include
-ms.date: 07/18/2024
+ms.date: 07/08/2025
 ---
 
 
@@ -16,4 +16,4 @@ ms.date: 07/18/2024
     - Make sure that you're uploading your VHD or VHDX as a page blob image into the Storage account. Only page blob images are supported to create VM images via the Storage account.
     - If using a VHDX: 
         - The VHDX image must be Gen 2 type and secure boot enabled.
-        - The VHDX image must be prepared using `sysprep /generalize /shutdown /oobe`. For more information, see [Sysprep command-line options](/windows-hardware/manufacture/desktop/sysprep-command-line-options?view=windows-11#oobe&preserve-view=true).
+        - The VHDX image must be prepared using `sysprep /generalize /shutdown /oobe`. For more information, see [Sysprep command-line options](/windows-hardware/manufacture/desktop/sysprep-command-line-options?view=windows-11#oobe&preserve-view=true). This is true for both Windows and Linux VM images.

azure-local/manage/virtual-machine-image-existing-arc-vm.md

@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
 ms.custom: devx-track-azurecli
-ms.date: 03/27/2025
+ms.date: 07/08/2025
 ---
 
 # Create Azure Local VM image using existing Azure Local VMs enabled by Azure Arc
@@ -21,12 +21,17 @@ Before you begin, make sure that:
 
 - You've reviewed and completed the [Azure Local VM management prerequisites](./azure-arc-vm-management-prerequisites.md).
 - You've connected to your Azure Local using the instructions in [Connect to Azure Local via Azure CLI client](./azure-arc-vm-management-prerequisites.md#azure-command-line-interface-cli-requirements).
+- The VHDX image must be prepared using `sysprep /generalize /shutdown /oobe`. For more information, see [Sysprep command-line options](/windows-hardware/manufacture/desktop/sysprep-command-line-options#oobe). This is true for both Windows and Linux VM images.
+- The source VM must be powered off before attempting to create the VM image.
 
 
 ## Create VM image from existing Azure Local VM
 
 You create a VM image starting from the OS disk of the Azure Local VM and then use this image to deploy VMs on your Azure Local.
 
+> [!IMPORTANT]
+> Running Sysprep on an Azure Local VM will render the VM unusable. Sysprep resets system identity, removes user profiles, may invalidate Windows product activation, and can cause instability for applications that rely on machine-specific configuration. This action is irreversible.
+
 Follow these steps to create a VM image using the Azure CLI.
 
 ### Sign in and set subscription