Merge pull request #17189 from ManikaDhiman/md-remove-23h2-update

Removed 23H2 references from articles under the Update TOC node

Author: prmerger-automator[bot]

azure-local/update/about-updates-23h2.md

@@ -5,10 +5,10 @@ author: ronmiab
 ms.author: robess
 ms.topic: overview
 ms.reviewer: thoroet
-ms.date: 11/13/2024
+ms.date: 02/25/2025
 ---
 
-# About updates for Azure Local, version 23H2
+# About updates for Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
@@ -63,7 +63,7 @@ Microsoft might release the following types of updates for the Azure Local:
 
 ² The Original Equipment Manufacturer determines the frequency of Solution Builder Extension updates.
 
-Sometimes you might see updates to the latest patch level of your current baseline. If a new baseline is available, you might see the baseline update itself or the latest patch level of the baseline. Your system must stay within six months of the most recent baseline to consider it supported. For more information and a visualization of supported releases, see [About Azure Local, version 23H2 releases](../release-information-23h2.md#about-azure-local-releases).
+Sometimes you might see updates to the latest patch level of your current baseline. If a new baseline is available, you might see the baseline update itself or the latest patch level of the baseline. Your system must stay within six months of the most recent baseline to consider it supported. For more information and a visualization of supported releases, see [About Azure Local releases](../release-information-23h2.md#about-azure-local-releases).
 
 The next sections provide an overview of components, along with methods and interfaces for updating your solution.
 
@@ -93,15 +93,15 @@ There are two interfaces you can use to apply available updates.
 
 ### PowerShell
 
-The PowerShell procedures apply to both single-node and multi-node systems that run with the orchestrator installed. For more information, see [Update your Azure Local, version 23H2 via PowerShell](update-via-powershell-23h2.md).
+The PowerShell procedures apply to both single-node and multi-node systems that run with the orchestrator installed. For more information, see [Update Azure Local via PowerShell](update-via-powershell-23h2.md).
 
 ### The Azure portal
 
-You can install Azure Local updates using the Azure Update Manager in the Azure portal. For more information, see [Use Azure Update Manager to update your Azure Local, version 23H2](./azure-update-manager-23h2.md).
+You can install Azure Local updates using the Azure Update Manager in the Azure portal. For more information, see [Use Azure Update Manager to update Azure Local](./azure-update-manager-23h2.md).
 
 ### Unsupported interfaces for updates
 
-When you install updates for Azure Local, version 23H2 don't use the following interfaces:
+When you install updates for Azure Local, don't use the following interfaces:
 
 - SConfig
 - Windows Admin Center

azure-local/update/azure-update-manager-23h2.md

@@ -5,17 +5,17 @@ author: ronmiab
 ms.author: robess
 ms.topic: how-to
 ms.reviewer: mindydiep
-ms.date: 01/23/2025
+ms.date: 02/25/2025
 #customer intent: As a Senior Content Developer, I want provide customers with information and guidance on using Azure Update Manager to manage and keep their Azure Local instances up to date.
 ---
 
-# Use Azure Update Manager to update your Azure Local, version 23H2
+# Use Azure Update Manager to update Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
 [!INCLUDE [IMPORTANT](../includes/hci-applies-to-23h2-cluster-updates.md)]
 
-This article describes how to use Azure Update Manager to find and install available updates on Azure Local. Additionally, we provide guidance on how to review, track progress, and browse the history of system updates.
+This article describes how to use Azure Update Manager to find and install available updates on Azure Local. It also describes how to review, track progress, and browse the history of system updates.
 
 ## About Azure Update Manager
 
@@ -35,7 +35,7 @@ Here are some benefits of the Azure Update Manager:
 
 ## Prerequisites
 
-- An Azure Local, version 23H2 system deployed and registered with Azure.
+- An Azure Local system deployed and registered with Azure.
 - Make sure to apply updates via supported navigation paths in Azure portal. Microsoft only supports updates applied from the **Azure Local** resource page or via the **Azure Update Manager > Resources > Azure Local**. Additionally, use of 3rd party tools to install updates is not supported. 
 
 For Azure Local, Azure Update Manager is supported only in the regions where Azure Local is supported. For more information, see [List of supported Azure Local regions](../concepts/system-requirements-23h2.md#azure-requirements).

azure-local/update/solution-builder-extension.md

@@ -5,7 +5,7 @@ author: ronmiab
 ms.author: robess
 ms.topic: overview
 ms.reviewer: dandefolo
-ms.date: 12/11/2024
+ms.date: 02/25/2025
 
 #customer intent: As a Senior Content Developer, I want provide customers with the highest level of content for the Solution Builder Extension so that customers gain knowledge and keep their Azure Local up to date in the most efficient way.
 
@@ -15,17 +15,17 @@ ms.date: 12/11/2024
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-This article provides an overview of the Solution Builder Extension updates and explains how to identify and install them on your Azure Local, version 23H2 systems. Additionally, it offers insights into the extension’s advanced capabilities.
+This article provides an overview of the Solution Builder Extension updates and explains how to identify and install them on your Azure Local systems. Additionally, it offers insights into the extension’s advanced capabilities.
 
 ## About the extension
 
-The Solution Builder Extension (referred to as SBE in the Azure CLI) allows you to apply updates from your hardware vendor to your Azure Local, version 23H2 system. In addition to Microsoft Azure Local solution updates, many hardware vendors release regular updates for your Azure Local hardware. These updates may include driver and firmware updates, hardware monitoring enhancements, and diagnostic tools. Additionally, you can receive updates related to supplemental policies for Windows Defender Application Control (WDAC) and validation logic integrated into Azure Local pre-update health checks.
+The Solution Builder Extension (referred to as SBE in the Azure CLI) allows you to apply updates from your hardware vendor to your Azure Local system. In addition to Microsoft Azure Local solution updates, many hardware vendors release regular updates for your Azure Local hardware. These updates may include driver and firmware updates, hardware monitoring enhancements, and diagnostic tools. Additionally, you can receive updates related to supplemental policies for Windows Defender Application Control (WDAC) and validation logic integrated into Azure Local pre-update health checks.
 
-Starting with Azure Local, version 23H2, these types of updates are packaged into **Solution Builder Extension** or **Solution Builder Extension packages**.
+Starting with Azure Local 2311.2, all these updates are packaged into Solution Builder Extension or Solution Builder Extension packages.
 
 ## Solution Builder Extension package updates
 
-Solution Builder Extension package updates are integrated into the solution update process for Azure Local, version 23H2. You can install these updates as part of a combined (full solution) update with other Azure Local updates using orchestration within Azure Local. For example, if a Solution Builder Extension update that matches your system's hardware becomes available, it appears as an update option in the Azure portal or can be retrieved using the `Get-SolutionUpdate` PowerShell cmdlet. For more information, see [About updates for Azure Local, version 23H2](../update/about-updates-23h2.md#user-interfaces-for-updates).
+Solution Builder Extension package updates are integrated into the solution update process for Azure Local. You can install these updates as part of a combined (full solution) update with other Azure Local updates using orchestration within Azure Local. For example, if a Solution Builder Extension update that matches your system's hardware becomes available, it appears as an update option in the Azure portal or can be retrieved using the `Get-SolutionUpdate` PowerShell cmdlet. For more information, see [About updates for Azure Local](../update/about-updates-23h2.md#user-interfaces-for-updates).
 
 By installing such combined updates, you can keep your entire solution up to date with less impact and minimal effect on running workloads.
 
@@ -42,20 +42,20 @@ In addition to installing hardware updates, Solution Builder Extension may also
 
 ## Identify a Solution Builder Extension update for your hardware
 
-Starting with Azure Local, version 23H2, any new Integrated Systems or Premier Solution hardware added to the Azure Local catalog must implement a Solution Builder Extension that supports firmware and driver updates. Microsoft recommends purchasing newer Integrated Systems and Premier Solutions to fully utilize the update-at-scale capabilities enabled by the Solution Builder Extension.
+Starting with Azure Local 2311.2, any new Integrated Systems or Premier Solution hardware added to the Azure Local catalog must implement a Solution Builder Extension that supports firmware and driver updates. Microsoft recommends purchasing newer Integrated Systems and Premier Solutions to fully utilize the update-at-scale capabilities enabled by the Solution Builder Extension.
 
 > [!NOTE]
-> A solution builder extension might not be implemented for your hardware if:
+> A Solution Builder Extension might not be implemented for your hardware if:
 >
-> - It was added to the Azure Local catalog before Azure Local, version 23H2.
+> - It was added to the Azure Local catalog before Azure Local 2311.2.
 >
 > - Your hardware was purchased as a Validated Node.
 >
 > Consult with your hardware vendor’s Azure Local documentation to determine if your machine model supports a Solution Builder Extension.
 
 If your hardware doesn't support a Solution Builder Extension update experience, the process for updating your hardware is like that of Azure Local, version 22H2. This means that your hardware updates may be available using Windows Admin Center. For more information, see  [Update Azure Local, version 22H2](../manage/update-cluster.md#install-operating-system-and-hardware-updates-using-windows-admin-center).
 
-Here's an example of the Windows Admin Center updates tool for systems running Azure Local, version 23H2.
+Here's an example of the Windows Admin Center updates tool for systems running Azure Local.
 
 [![Screenshot to install hardware updates in Windows Admin Center.](./media/solution-builder-extension/updates-os-windows-admin-center-23h2.png)](media/solution-builder-extension/updates-os-windows-admin-center-23h2.png#lightbox)
 
@@ -104,7 +104,7 @@ To discover and install SBE or your SBE updates, use one of the methods in the n
 
 ### Discover Solution Builder Extension updates via the Azure portal
 
-To discover and select updates via the Azure portal, see [Use Azure Update Manager to update your Azure Local, version 23H2](../update/azure-update-manager-23h2.md#browse-for-system-updates).
+To discover and select updates via the Azure portal, see [Use Azure Update Manager to update Azure Local](../update/azure-update-manager-23h2.md#browse-for-system-updates).
 
 ### Discover Solution Builder Extension updates via PowerShell
 
@@ -207,4 +207,4 @@ For more information, see [Discover Solution Builder Extension updates](#discove
 ## Next steps
 
 - [Import and discover solution updates](../update/update-via-powershell-23h2.md#step-3-import-and-rediscover-updates).
-- [Understand update phases of Azure Local, version 23H2](../update/update-phases-23h2.md).
+- [Understand update phases of Azure Local](../update/update-phases-23h2.md).

azure-local/update/update-phases-23h2.md

@@ -4,20 +4,20 @@ description: Understand the various phases of solution updates applied to Azure
 author: alkohli
 ms.author: alkohl
 ms.topic: conceptual
-ms.date: 10/21/2024
+ms.date: 02/25/2025
 ---
 
-# Review update phases of Azure Local, version 23H2
+# Review update phases of Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-This article describes the various phases of solution updates that are applied to your Azure Local to keep it up-to-date. This information is applicable to Azure Local, version 23H2.
+This article explains the different phases of solution updates that you apply to Azure Local to keep it up to date.
 
 The procedure in this article applies to both single node and multi-node systems that are running the latest version of Azure Local with the orchestrator installed.
 
 ## About update phases
 
-The Azure Local solution updates can consist of OS, agents and service, and solution extension updates. For more information on these solution updates, see [About updates for Azure Local, version 23H2](about-updates-23h2.md).
+The Azure Local solution updates can consist of OS, agents and service, and solution extension updates. For more information on these solution updates, see [About updates for Azure Local](about-updates-23h2.md).
 
 The new update feature automates the update process for agents, services, operating system content, and Solution Extension content, with the goal of maintaining availability by shifting workloads around throughout the update process when needed.
 

azure-local/update/update-troubleshooting-23h2.md

@@ -4,19 +4,19 @@ description: Learn how to troubleshoot solution updates applied to Azure Local,
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
-ms.date: 12/11/2024
+ms.date: 02/25/2025
 #customer intent: As a Principal Content Developer, I want provide customers with information and guidance on how to troubleshoot solution updats for their Azure Local intances.
 ---
 
-# Troubleshoot solution updates for Azure Local, version 23H2
+# Troubleshoot solution updates for Azure Local
 
 [!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
 
 This article describes how to troubleshoot solution updates that are applied to your Azure Local to keep it up-to-date.
 
 ## About troubleshooting updates
 
-If your system was created via a new deployment of Azure Local, version 23H2, then an orchestrator was installed during the deployment. The orchestrator manages all of the updates for the platform - OS, drivers and firmware, agents and services.
+If your system was created via a new deployment of Azure Local, then an orchestrator was installed during the deployment. The orchestrator manages all of the updates for the platform - OS, drivers and firmware, agents and services.
 
 The new update solution includes a retry and remediation logic. This logic attempts to fix update issues in a non-disruptive way, such as retrying a Cluster-Aware Update (CAU) run. If an update run can't be remediated automatically, it fails. When an update fails, Microsoft recommends inspecting the details for the failure message to determine the appropriate next action. You can attempt to resume the update, if appropriate, to determine if a retry will resolve the issue.
 
@@ -247,15 +247,15 @@ See the table below for update failure scenarios and remediation guidelines.
 | --- | --- | --- |
 | Any | Power loss or other similar interruption to system during the update. | 1. Restore power.<br>2. Run a system health check.<br>3. Resume the update.  |
 | CAU updates | Cluster Aware Update (CAU) update run fails with a `max retries exceeded` failure. | If there is an indication that multiple CAU attempts have been made and that they have all failed, it is often best to investigate the first failure.<br><br>Use the start and end time of the first failure to match up with the correct `Get-CauReport` output to further investigate the failure.  |
-| Any | Memory, power supply, boot driver, or similar critical failure on one or more nodes. | See [Repair a node on Azure Local, version 23H2](../manage/repair-server.md) for how to repair the failing node.<br>Once the node has been repaired the update can be resumed. |
+| Any | Memory, power supply, boot driver, or similar critical failure on one or more nodes. | See [Repair a node on Azure Local](../manage/repair-server.md) for how to repair the failing node.<br>Once the node has been repaired the update can be resumed. |
 
 ## Collect update logs
 
 You can also collect diagnostic logs to help Microsoft identify and fix the issues.
 
 To collect logs for updates using the Azure portal, see [Resume an update](#the-azure-portal).
 
-To collect logs for the update failures see [Collect diagnostic logs for Azure Local, version 23H2](../manage/collect-logs.md?tabs=azureportal.md).
+To collect logs for the update failures see [Collect diagnostic logs for Azure Local](../manage/collect-logs.md?tabs=azureportal.md).
 
 ## View update summary report