Sync release-local-disconnectednew with main

sethmanheim · web-flow · commit 9264e83c981b · 2025-07-23T09:56:49.000-07:00
diff --git a/AKS-Arc/TOC.yml b/AKS-Arc/TOC.yml
@@ -13,7 +13,7 @@
     href: data-collection.md
   - name: Blogs and announcements
     href: blogs-announcements.md
-- name: AKS on Azure Local
+- name: AKS Arc on Azure Local
   expanded: true
   items:
   - name: What's new in AKS on Azure Local
@@ -332,7 +332,7 @@
       href: aks-edge-licensing.md
     - name: Microsoft Software License Terms
       href: aks-edge-software-license-terms.md 
-- name: AKS on VMware
+- name: AKS Arc on VMware
   items:
   - name: Overview
     href: aks-vmware-overview.md
@@ -380,7 +380,7 @@
         href: vmsize.yml
       - name: vnet
         href: vnet.yml
-- name: AKS on Windows Server
+- name: AKS Arc on Windows Server
   items:
   - name: AKS on Windows Server retirement
     href: aks-windows-server-retirement.md
@@ -390,7 +390,7 @@
     href: system-requirements.md
   - name: Quickstarts 
     items:
-    - name: Deploy an AKS cluster
+    - name: Deploy an AKS Arc cluster
       items:
       - name: Use PowerShell
         href: kubernetes-walkthrough-powershell.md
diff --git a/AKS-Arc/aks-whats-new-local.md b/AKS-Arc/aks-whats-new-local.md
@@ -2,7 +2,7 @@
 title: What's new in AKS on Azure Local
 description: Learn about what's new in AKS on Azure Local.
 ms.topic: overview
-ms.date: 07/21/2025
+ms.date: 07/22/2025
 author: sethmanheim
 ms.author: sethm 
 ms.reviewer: rcheeran
@@ -34,6 +34,7 @@ The following Kubernetes cluster deployment and management capabilities are avai
 
 - **Disk space exhaustion**: Fixed [issues due to disk space exhaustion on control plane VMs due to accumulation of kube-apiserver audit logs](kube-apiserver-log-overflow.md).  
 - **Cluster upgrade**: Fixed AKS Arc cluster and node pool create, scale, and [upgrade issues due to unavailability of AKS Arc VM images](gallery-image-not-usable.md).
+- **AKS Arc Telemetry pod issue**: Fixed an issue in which the [AKS Arc telemetry pod was consuming excessing CPU and memory](telemetry-pod-resources.md).
 - **New checks**: Added new checks during cluster and node pool operations. These improvements allow the system to proactively detect and handle scenarios where there are insufficient IP addresses in the IP pool.
 - **GPU resource allocation**: Additional pre-checks for resource allocation for GPUs during Kubernetes cluster create operation.
 - **Node pool improvements**: Accurate representation of node pool count and status on the Azure portal. This release also includes improvements to node pool creation and update flows to ensure that the Kubernetes cluster status accounts for corresponding node pool status.
diff --git a/AKS-Arc/aks-windows-server-retirement.md b/AKS-Arc/aks-windows-server-retirement.md
@@ -1,11 +1,11 @@
 ---
-title: Retirement of AKS architecture on Windows Server 2019 and Windows Server 2022
-description: Learn about retirement of AKS on Windows Server 2019 and Windows Server 2022.
+title: Retirement of AKS architecture on Windows Server
+description: Learn about the retirement of AKS on Windows Server.
 ms.topic: how-to
 ms.custom: linux-related-content
 author: sethmanheim
 ms.author: sethm
-ms.date: 07/21/2025
+ms.date: 07/22/2025
 ms.reviewer: rcheeran
 ms.lastreviewed: 07/21/2025
 
@@ -37,7 +37,7 @@ The following Kubernetes cluster deployment and management capabilities are avai
 
 ## If you're using Azure Kubernetes Service on Windows Server 2019 or Windows Server 2022
 
-The AKS Arc current architecture on Windows Server 2019 and Windows Server 2022 will be retired on March 27, 2028. Starting on March 27 2028, you no longer get support, security and quality updates for your existing AKS Arc clusters. You also won't be able to deploy, upgrade or scale the current architecture of Azure Kubernetes Service on Windows Server 2019 and Windows Server 2022.
+The AKS Arc current architecture on Windows Server 2019 and Windows Server 2022 will be retired on March 27, 2028. Starting on March 27 2028, you no longer get support, security and quality updates for your existing AKS Arc clusters. You also won't be able to deploy, upgrade or scale the current architecture of Azure Kubernetes Service on Windows Server 2019 and Windows Server 2022. Between now and March 2028, we will not add support for any new Windows Server SKUs; for example, Windows Server 2025 is not supported on AKS Arc.
 
 ## If you're using Azure Kubernetes Service on Azure Local, version 22H2
 
diff --git a/AKS-Arc/gallery-image-not-usable.md b/AKS-Arc/gallery-image-not-usable.md
@@ -4,8 +4,9 @@ description: Learn about a known issue with Kubernetes cluster create or nodepoo
 ms.topic: troubleshooting
 author: sethmanheim
 ms.author: sethm
-ms.date: 07/17/2025
+ms.date: 07/22/2025
 ms.reviewer: rcheeran
+ms.lastreviewed: 07/22/2025
 
 ---
 
@@ -47,8 +48,8 @@ This issue was fixed in [AKS on Azure Local, version 2507](/azure/azure-local/wh
 
 - Upgrade your Azure Local deployment to the 2507 build.
 - Once updated, confirm that the images were downloaded successfully by running the `az aksarc get-versions` command.
-- For new AKS clusters: new AKS clusters should now be created successfully.
-- For scaling existing AKS clusters: scaling existing AKS clusters continues to encounter issues. Please file a support case.
+- You can now use the specified Kubernetes versions while creating or updating your AKS Arc clusters.
+- If you continue to encounter issues, please file a support ticket.
 
 ## Next steps
 
diff --git a/azure-local/includes/azure-local-end-of-support-banner-23h2.md b/azure-local/includes/azure-local-end-of-support-banner-23h2.md
@@ -3,9 +3,9 @@ author: alkohli
 ms.author: alkohli
 ms.service: azure-local
 ms.topic: include
-ms.date: 04/24/2025
+ms.date: 07/22/2025
 ms.reviewer: alkohli
 ---
 
 > [!IMPORTANT]
-> Azure Local, version 23H2 (releases 2311.2 to 2509) will reach end of support on October 31, 2025. After this date, you won't receive monthly security and quality updates. Support requests will only be available for patching to a supported release.
+> Azure Stack HCI, version 23H2 OS (releases 2311.2 to 2509, OS version 25398.xxxx) will reach end of support on October 31, 2025. After this date, you won't receive monthly security and quality updates. Support requests will only be available for patching to a supported release.
diff --git a/azure-local/known-issues.md b/azure-local/known-issues.md
@@ -135,7 +135,7 @@ The following table lists the known issues in this release:
 | Update <!--33470082--> |  Solution update fails with the error: `Unable to install solution update "11.2506.1001.24" - Type 'UpdateFOD' of Role 'ComposedImageUpdate' raised an exception.` | For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/SolutionUpdate-UpdateFOD.md). |
 | Deployment <!--33471589--> |  After Azure portal deployment, SConfig network settings shows the error: `Set-SCfNetworksetting : Cannot bind argument to parameter 'Value' because it is null.` | There's no known workaround in this release. |
 | Update <!--33448368--> |  Cluster-Aware Updating runs might fail with the error:<br>`Type 'SBEPartnerConfirmCauDone' of Role 'SBE' raised an exception:<br>SBE_MsftCIOnlyCommon_CommonForTesting_4.2.2504.16: ErrorID: SBE-CAU-RUNNING-AFTER-DONE -- CAU run is still in progress when it should be done. See https://aka.ms/AzureLocal/SBE/CauHelp for help. Review full Get-CauRun output it identify if it is progressing or stuck. Wait for it to complete if progressing.` | Wait for CAU run to complete (wait for `Get-CauRun` to report `RunNotInProgress`) and resume the update. |
-|Azure Local VMs <!--33811472-->| When no storage path is specified during deployment, resources (VMs, data disks, and images) are automatically placed on the first storage path of the cluster, even when other storage paths are also available. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. | Update to Azure Local 2507, which includes a fix for this issue. Or, create resources with a specified storage path. For more information, see [Troubleshoot Azure Local Virtual Machines enabled by Azure Arc](../azure-local/manage/troubleshoot-arc-enabled-vms.md#resource-deployment-failure-due-to-insufficient-disk-space-on-the-first-storage-path). |
+|Azure Local VMs <!--33811472-->| When no storage path is specified during deployment, resources (VMs, data disks, and images) are automatically placed on the first storage path of the cluster, even when other storage paths are also available. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. | Create resources with a specified storage path. For more information, see [Troubleshoot Azure Local Virtual Machines enabled by Azure Arc](../azure-local/manage/troubleshoot-arc-enabled-vms.md#resource-deployment-failure-due-to-insufficient-disk-space-on-the-first-storage-path). |
 
 ## Known issues from previous releases
 
diff --git a/azure-local/manage/gpu-manage-via-partitioning.md b/azure-local/manage/gpu-manage-via-partitioning.md
@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 04/29/2025
+ms.date: 07/22/2025
 ---
 
 # Manage GPUs using partitioning (preview)
@@ -33,7 +33,7 @@ Consider the following limitations when using the GPU-P feature:
 
 - Partitions are autoassigned to the VMs. You can't choose a specific partition for a specific VM.
 
-- GPU partitioning on Azure Local supports live migration. However, the host and VMs must be on NVIDIA virtual GPU software version 18 and later. For more information, see [Microsoft Azure Local - NVIDIA Docs](https://docs.nvidia.com/vgpu/18.0/grid-vgpu-release-notes-microsoft-azure-stack-hci/index.html).
+- GPU partitioning on Azure Local supports live migration. The OS build must be 26100.xxxx or later. The host and VMs must be on NVIDIA virtual GPU software version 18 and later. For more information, see [Microsoft Azure Local - NVIDIA Docs](https://docs.nvidia.com/vgpu/18.0/grid-vgpu-release-notes-microsoft-azure-stack-hci/index.html).
 
 - You can partition your GPU using Azure Command-Line Interface (CLI). We recommend that you use Azure CLI to configure and assign GPU partitions. You must manually ensure that the homogeneous configuration is maintained for GPUs across all the machines in your system.
 
diff --git a/azure-local/release-information-23h2.md b/azure-local/release-information-23h2.md
@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: article
 ms.service: azure-local
-ms.date: 07/21/2025
+ms.date: 07/22/2025
 ---
 
 # Azure Local release information
@@ -20,6 +20,9 @@ This article provides the release information for Azure Local, including the rel
 
 ## About Azure Local releases
 
+> [!NOTE]
+> Azure Local previously followed an annual release cadence for OS and feature updates, with versions like 23H2 and 22H2. The versioning model has now changed to align with a monthly release train, like 2507, 2506. However, references to older versioning might still appear in some documentation.
+
 The Azure Local includes multiple release trains: 2411, 2503, 2504, 2505, and so forth. Each release train after 2411 is either a feature build or cumulative update.
 
 - **Feature build**: The feature update build is the initial version of the software in a release train. Feature releases go beyond quality and security fixes, incorporating product enhancements, including updates for Azure Local services and agents.
@@ -80,7 +83,7 @@ The following tables summarize the release information for Azure Local across al
 
 | Solution version | OS build | Security update | What's new | Known issues |
 |------|-------|---------------|------------|--------------|
-| 12.2507.1001.8 <br><br> 10.2507.0.6 <br></br> Availability date: 2025-07-21 | 26100.4652 | [July OS security update](security-update/security-update.md?view=azloc-2507&preserve-view=true&tabs=new-deployments) | [Features and improvements](./whats-new.md?view=azloc-2507&preserve-view=true#features-and-improvements-in-2507) | [Known issues](./known-issues.md?view=azloc-2507&preserve-view=true) |
+| 12.2507.1001.8 <br><br> Availability date: 2025-07-21 | 26100.4652 | [July OS security update](security-update/security-update.md?view=azloc-2507&preserve-view=true&tabs=new-deployments) | [Features and improvements](./whats-new.md?view=azloc-2507&preserve-view=true#features-and-improvements-in-2507) | [Known issues](./known-issues.md?view=azloc-2507&preserve-view=true) |
 | 12.2506.1001.29 <br><br> Availability date: 2025-07-02 | 26100.4349 | [June OS security update](security-update/security-update.md?view=azloc-2506&preserve-view=true&tabs=new-deployments) | [Features and improvements](./whats-new.md?view=azloc-2506&preserve-view=true#features-and-improvements-in-2506) | [Known issues](./known-issues.md?view=azloc-2506&preserve-view=true) |
 | 12.2505.1001.23 <br><br> Availability date: 2025-05-28 | 26100.4061 | [May OS security update](security-update/security-update.md?view=azloc-2505&preserve-view=true&tabs=new-deployments) | [Features and improvements](./whats-new.md?view=azloc-2505&preserve-view=true#features-and-improvements-in-2505) | [Known issues](./known-issues.md?view=azloc-2505&preserve-view=true) |
 | 12.2504.1001.20 <br><br> Availability date: 2025-04-29 | 26100.3775 | [April OS security update](security-update/security-update.md?view=azloc-2504&preserve-view=true&tabs=new-deployments) | [Features and improvements](./whats-new.md?view=azloc-2504&preserve-view=true#features-and-improvements-in-2504) | [Known issues](./known-issues.md?view=azloc-2504&preserve-view=true) |
diff --git a/azure-local/update/import-discover-updates-offline-23h2.md b/azure-local/update/import-discover-updates-offline-23h2.md
@@ -43,7 +43,7 @@ For more information on the release cadence, see [Azure Local release informatio
 
 | OS Build | Download URI | SHA256 |
 |--|--|--|
-| 25398.1732 | [11.2507.0.3027](https://azurestackreleases.download.prss.microsoft.com/dbazure/AzureLocal/CombinedSolutionBundle/11.2507.1001.7/CombinedSolutionBundle.11.2507.1001.7.zip) <br><br> Availability date: <br><br> 2025-07-21 | F3E288E1854253E25AD063D3DA4B766CF634FE294BD6814F4A4A1551FB855773 |
+| 25398.1732 | [11.2507.1001.7](https://azurestackreleases.download.prss.microsoft.com/dbazure/AzureLocal/CombinedSolutionBundle/11.2507.1001.7/CombinedSolutionBundle.11.2507.1001.7.zip) <br><br> Availability date: <br><br> 2025-07-21 | F3E288E1854253E25AD063D3DA4B766CF634FE294BD6814F4A4A1551FB855773 |
 | 25398.1665 | [11.2506.1001.28](https://azurestackreleases.download.prss.microsoft.com/dbazure/AzureLocal/CombinedSolutionBundle/11.2506.1001.28/CombinedSolutionBundle.11.2506.1001.28.zip) <br><br> Availability date: <br><br> 2025-07-02 | 18975A06372192DD7249B5DCF8844EA0A68AD08B1C9F3C554FABF79EA74CB290 |
 | 25398.1611 | [11.2505.1001.22](https://azurestackreleases.download.prss.microsoft.com/dbazure/AzureLocal/CombinedSolutionBundle/11.2505.1001.22/CombinedSolutionBundle.11.2505.1001.22.zip) <br><br> Availability date: <br><br> 2025-05-28 | AB2C7CE74168BF9FD679E7CE644BC57A20A0A3A418C5E8663EBCF53FC0B45113 |
 | 25398.1551 | [11.2504.1001.19](https://azurestackreleases.download.prss.microsoft.com/dbazure/AzureLocal/CombinedSolutionBundle/11.2504.1001.19/CombinedSolutionBundle.11.2504.1001.19.zip) <br><br> Availability date: <br><br> 2025-04-21 | 7658C5CBAE241951C786D06D35E8B09A1160FDC5E9B8CAEDEB374ECC22A2CB68 |
diff --git a/azure-local/whats-new.md b/azure-local/whats-new.md
@@ -47,6 +47,7 @@ This release has the following features and improvements:
  
 ::: moniker-end
 
+::: moniker range="=azloc-2506"
 
 ## Features and improvements in 2506
 
@@ -239,7 +240,7 @@ This release has the following features and improvements:
 
 ::: moniker-end
 
-moniker range="=azloc-previous"
+::: moniker range="=azloc-previous"
 
 ## Features and improvements in 2411.3
 
