Sync release-hotfixes with main

sethmanheim · web-flow · commit 82b0cbf63591 · 2025-04-10T14:27:47.000-07:00
diff --git a/AKS-Arc/aks-overview.md b/AKS-Arc/aks-overview.md
@@ -2,7 +2,7 @@
 title: What is AKS enabled by Azure Arc?
 description: Learn about AKS enabled by Azure Arc and available deployment options.
 ms.topic: overview
-ms.date: 05/28/2024
+ms.date: 04/10/2025
 author: sethmanheim
 ms.author: sethm 
 ms.reviewer: abha
@@ -41,7 +41,7 @@ The available deployment options are as follows:
 
 - **AKS on Azure Local**: AKS on Azure Local uses Azure Arc to create new Kubernetes clusters on Azure Local directly from Azure. It enables you to use familiar tools like the Azure portal and Azure Resource Manager templates to create and manage your Kubernetes clusters running on Azure Local.
 - **AKS Edge Essentials**: AKS Edge Essentials includes a lightweight Kubernetes distribution with a small footprint and simple installation experience, making it easy for you to deploy Kubernetes on PC-class or "light" edge hardware.
-- **AKS on Windows Server**: Azure Kubernetes Service on Windows Server (and on Azure Local 22H2) is an on-premises Kubernetes implementation of AKS that automates running containerized applications at scale, using Windows PowerShell and Windows Admin Center. It simplifies deployment and management of AKS on Windows Server 2019/2022 Datacenter and Azure Local 22H2.
+- **AKS on Windows Server**: Azure Kubernetes Service on Windows Server (and on Azure Local) is an on-premises Kubernetes implementation of AKS that automates running containerized applications at scale, using Windows PowerShell and Windows Admin Center. It simplifies deployment and management of AKS on Windows Server 2019/2022 Datacenter and Azure Local.
 - **AKS on VMWare (preview)**: AKS on VMware (preview) enables you to use Azure Arc to create new Kubernetes clusters on VMware vSphere. With AKS on VMware, you can manage your AKS clusters running on VMware vSphere using familiar tools like Azure CLI.
 
 ## Next steps
diff --git a/AKS-Arc/deploy-gpu-node-pool.md b/AKS-Arc/deploy-gpu-node-pool.md
@@ -241,5 +241,5 @@ If an upgrade is triggered on a cluster without extra GPU resources to facilitat
 ## Next steps
 
 - [Supported VM sizes](scale-requirements.md)
-- [Use GPUs (AKS on Azure Local 22H2)](deploy-gpu-node-pool-22h2.md)
-- [AKS overview](aks-hybrid-options-overview.md)
+- [Use GPUs in AKS on Windows Server](deploy-gpu-node-pool-22h2.md)
+- [AKS overview](aks-overview.md)
diff --git a/azure-local/TOC.yml b/azure-local/TOC.yml
@@ -484,10 +484,10 @@ items:
   items:
   - name: Migration overview
     href: migrate/migration-options-overview.md
-  - name: What's new in VM migration?
-    href: migrate/migrate-whats-new.md
   - name: Migrate using Azure Migrate
     items:
+    - name: What's new in VM migration?
+      href: migrate/migrate-whats-new.md
     - name: Hyper-V VMs
       items: 
       - name: Overview
diff --git a/azure-local/deploy/deployment-azure-resource-manager-template.md b/azure-local/deploy/deployment-azure-resource-manager-template.md
@@ -3,7 +3,7 @@ title: Azure Resource Manager template deployment for Azure Local, version 23H2
 description: Learn how to prepare and then deploy Azure Local instance, version 23H2 using the Azure Resource Manager template.
 author: alkohli
 ms.topic: how-to
-ms.date: 04/03/2025
+ms.date: 04/10/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -30,52 +30,6 @@ This article details how to use an Azure Resource Manager template in the Azure
 
 Follow these steps to prepare the Azure resources you need for the deployment:
 
-### Create a service principal and client secret
-
-To authenticate your system, you need to create a service principal and a corresponding **Client secret** for Arc Resource Bridge (ARB).
-
-### Create a service principal for ARB
-
-Follow the steps in [Create a Microsoft Entra application and service principal that can access resources via Azure portal](/entra/identity-platform/howto-create-service-principal-portal) to create the service principal and assign the roles. Alternatively, use the PowerShell procedure to [Create an Azure service principal with Azure PowerShell](/powershell/azure/create-azure-service-principal-azureps).
-
-The steps are also summarized here:
-
-1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/) as at least a Cloud Application Administrator. Browse to **Identity > Applications > App registrations** then select **New registration**.
-
-1. Provide a **Name** for the application, select a **Supported account type**, and then select **Register**.
-
-    :::image type="content" source="./media/deployment-azure-resource-manager-template/create-service-principal-1a.png" alt-text="Screenshot showing Register an application for service principal creation." lightbox="./media/deployment-azure-resource-manager-template/create-service-principal-1a.png":::
-
-1. Once the service principal is created, go to the **Enterprise applications** page. Search for and select the SPN you created.
-
-   :::image type="content" source="./media/deployment-azure-resource-manager-template/create-service-principal-2a.png" alt-text="Screenshot showing search results for the service principal created." lightbox="./media/deployment-azure-resource-manager-template/create-service-principal-2a.png":::
-
-1. Under properties, copy the **Application (client) ID**  and the **Object ID** for this service principal.
-
-   :::image type="content" source="./media/deployment-azure-resource-manager-template/create-service-principal-2b.png" alt-text="Screenshot showing Application (client) ID and the object ID for the service principal created." lightbox="./media/deployment-azure-resource-manager-template/create-service-principal-2b.png":::
-
-    You use the **Application (client) ID** against the `arbDeploymentAppID` parameter and the **Object ID** against the `arbDeploymentSPNObjectID` parameter in the Resource Manager template.
-
-### Create a client secret for ARB service principal
-
-1. Go to the application registration that you created and browse to **Certificates & secrets > Client secrets**.
-1. Select **+ New client** secret.
-
-    :::image type="content" source="./media/deployment-azure-resource-manager-template/create-client-secret-1.png" alt-text="Screenshot showing creation of a new client secret." lightbox="./media/deployment-azure-resource-manager-template/create-client-secret-1.png":::
-
-1. Add a **Description** for the client secret and provide a timeframe when it **Expires**. Select **Add**.
-
-    :::image type="content" source="./media/deployment-azure-resource-manager-template/create-client-secret-2.png" alt-text="Screenshot showing Add a client secret blade." lightbox="./media/deployment-azure-resource-manager-template/create-client-secret-2.png":::
-
-1. Copy the **client secret value** as you use it later.
-
-    > [!Note]
-    > For the application client ID, you will need it's secret value. Client secret values can't be viewed except for immediately after creation. Be sure to save this value when created before leaving the page.
-
-    :::image type="content" source="./media/deployment-azure-resource-manager-template/create-client-secret-3.png" alt-text="Screenshot showing client secret value." lightbox="./media/deployment-azure-resource-manager-template/create-client-secret-3.png":::
-
-    You use the **client secret value** against the `arbDeploymentAppSecret` parameter in the Resource Manager template.
-
 ### Get the object ID for Azure Local Resource Provider
 
 This object ID for the Azure Local RP is unique per Azure tenant.
diff --git a/azure-local/deploy/media/deployment-azure-resource-manager-template/deploy-arm-template-5.png b/azure-local/deploy/media/deployment-azure-resource-manager-template/deploy-arm-template-5.png
diff --git a/azure-local/manage/azure-arc-vm-management-overview.md b/azure-local/manage/azure-arc-vm-management-overview.md
@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
 ms.custom: linux-related-content
-ms.date: 03/18/2025
+ms.date: 04/09/2025
 ---
 
 # What is Azure Local VM management?
@@ -43,7 +43,9 @@ Consider the following limitations when you're managing VMs on Azure Local:
 - Taking checkpoints on VMs running on Azure Local by using on-premises tools, such as Windows Admin Center or Hyper-V Manager, will adversely affect the management of these VMs from Azure.
 - Updates to VM configurations, such as vCPU, memory, network interface, or data disk via on-premises tools, won't be reflected on the Azure management plane.
 - Moving a resource group isn't supported for VMs on Azure Local and its associated resources (such as network interfaces and disks).
-- Creation of VMs by using Windows Server 2012 and Windows Server 2012 R2 images isn't supported via the Azure portal. You can do it only via the Azure CLI. For more information, see [Additional parameters for Windows Server 2012 and Windows Server 2012 R2 images](./create-arc-virtual-machines.md#additional-parameters-for-windows-server-2012-and-windows-server-2012-r2-images).  
+- Creation of VMs by using Windows Server 2012 and Windows Server 2012 R2 images isn't supported via the Azure portal. You can do it only via the Azure CLI. For more information, see [Additional parameters for Windows Server 2012 and Windows Server 2012 R2 images](./create-arc-virtual-machines.md#additional-parameters-for-windows-server-2012-and-windows-server-2012-r2-images).
+
+- Azure Local VMs only support IPv4 addresses. IPv6 addresses aren't supported.
 
 ## Components of Azure Local VM management
 
diff --git a/azure-local/manage/create-logical-networks.md b/azure-local/manage/create-logical-networks.md
@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 03/30/2025
+ms.date: 04/09/2025
 ---
 
 # Create logical networks for Azure Local VMs enabled by Azure Arc
@@ -14,6 +14,9 @@ ms.date: 03/30/2025
 
 This article describes how to create or add logical networks for your Azure Local instance. Any Azure Local virtual machines (VMs) that you create use these logical networks.
 
+> [!NOTE]
+> Azure Local VMs only support IPv4 addresses. IPv6 addresses aren't supported.
+
 ## Prerequisites
 
 Before you begin, make sure to complete the following prerequisites:
diff --git a/azure-local/whats-new.md b/azure-local/whats-new.md
@@ -5,7 +5,7 @@ ms.topic: overview
 author: alkohli
 ms.author: alkohli
 ms.service: azure-local
-ms.date: 04/03/2025
+ms.date: 04/09/2025
 ---
 
 # What's new in Azure Local?
@@ -34,12 +34,14 @@ This is a baseline release with the following features and improvements:
   - Environment checker validates the composed image used for bootstrap.
   - Environment checker validates PowerShell modules as per the validated solution recipe in the Pre-Update checks.
 - **Updates and upgrade improvements**
-  - The differentiation of SKUs is supported when considering the applicability of a Solution Builder Extension update.
-  - A tag is added to indicate a superseded update.
-  - The Download Service is now used to download HTTP content.
-  - A URL-based platform update package is now supported.
-  - Azure Local rebranding changes were made for Update.
+  - The Solution Builder Extension update now supports both supported and non-supported SKUs for a given model.
+  - A tag has been added to indicate whether an update is the latest or has been superseded.
+  - HTTP content will now be downloaded using a more resilient service (Download Service).
+  - OS content will be packaged with the release, rather than determining appliable content on the device at runtime. This change is aimed at minimizing failure points and supporting [sideloading](update/update-via-powershell-23h2.md#step-3-import-and-rediscover-updates).
+  - OS content will be installed using the CAU plug-ins that are shipped with OS.
+  - Azure Local rebranding changes were made for this update.
 - **Azure Local VM changes**: You can now connect to an Azure Local VM using the SSH/RDP protocol without the need for line of sight (inside the host network). For more information, see [Connect to an Azure Local VM using SSH](./manage/connect-arc-vm-using-ssh.md).
+- **What's new for migration**: Documentation for improvements and features for VM migration to Azure Local is now available. For more information, see [What's new in migration](./migrate/migrate-whats-new.md).
 
 
 ::: moniker-end
