Merge pull request #3450 from MicrosoftDocs/main638711966777780114sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

azure-local/release-information-23h2.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: conceptual
 ms.service: azure-local
-ms.date: 12/17/2024
+ms.date: 12/30/2024
 ---
 
 # Azure Local, version 23H2 release information
@@ -62,7 +62,7 @@ The following table summarizes the release information for Azure Local, version
 
 |Version| OS Build |Security update| What's new | Known issues |
 |------|-------|---------------|------------|--------------|
-| 10.2411.1.10 <br><br> Availability date: 2024-12-17 | 25398.1308 | [December OS security update](./security-update/security-update-dec-2024.md) | [Features and improvements](./whats-new.md#features-and-improvements-in-24111) | [Known issues](./index.yml) |
+| 10.2411.1.10 <br><br> Availability date: 2024-12-17 | 25398.1308 | [December OS security update](./security-update/security-update-dec-2024.md) | [Features and improvements](./whats-new.md#features-and-improvements-in-24111) | [Known issues](./known-issues-2411-1.md) |
 | 10.2411.0.24 <br><br> Availability date: 2024-11-26 | 25398.1251 | [November OS security update](./security-update/security-update-nov-2024.md) | [Features and improvements](./whats-new.md#features-and-improvements-in-2411) | [Known issues](./known-issues-2411.md) |
 | 10.2411.0.22 <br><br> Availability date: 2024-11-14 | 25398.1251 | [November OS security update](./security-update/security-update-nov-2024.md) | [Features and improvements](./whats-new.md#features-and-improvements-in-2411) | [Known issues](./known-issues-2411.md) |
 | 10.2408.2.7 <br><br> Availability date: 2024-10-23 | 25398.1189 | [October OS Security update](./security-update/security-update-oct-2024.md) |[Features and improvements](./whats-new.md#features-and-improvements-in-24082) | [Known issues](./known-issues-2408-2.md) |
@@ -91,4 +91,4 @@ The following table summarizes the release information for Azure Local, version
 
 ## Next steps
 
-- [What's new for Azure Local, version 23H2](./whats-new.md)
+- [What's new for Azure Local, version 23H2](./whats-new.md)

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

@@ -111,6 +111,9 @@ When you install updates for Azure Local, version 23H2 don't use the following i
 
 Using these interfaces can install out-of-band updates, which aren't supported within the lifecycle and may cause various issues on the system. Additionally, billing for update operations like periodic assessment, checking for updates, using the scheduler, and installing updates on the machine resource (Machine-Azure Arc) may occur.
 
+> [!IMPORTANT]
+> Use of 3rd party tools to install updates is not supported.
+
 ## Next steps
 
 Learn to [Understand update phases](./update-phases-23h2.md).

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

@@ -57,6 +57,11 @@ To browse for available system updates using Azure Update Manager, follow these
 
 ## Install system updates
 
+> [!IMPORTANT]
+> Use of 3rd party tools to install updates is not supported.
+
+You can install updates via the Azure Update Manager or from the Azure Local resource page.
+
 # [Azure Update Manager](#tab/azureupdatemanager)
 
 To install system updates using Azure Update Manager, follow these steps:

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

@@ -36,7 +36,7 @@ In addition to installing hardware updates, Solution Builder Extension may also
 | Advanced Solution Builder Extension Capability   |Description    |
 |---------------------------|---------------|
 | Health service integration | The Solution Builder Extension package can extend **Health Check** validation performed by Azure Local before various lifecycle actions (deployment, update, add node, repair node, and others) occur. The validation checks help to ensure issues are resolved before performing any specific lifecycle actions.<br/><br/> Hardware vendors typically use this integration to evaluate if there's a hardware issue that needs immediate attention. For example, it might identify problems with hardware vendor management software, a non-redundant power supply, or higher than expected temperatures. It could also identify SSD drive wear approaching a critical state. Be sure to review your hardware vendor's Solution Builder Extension documentation for details on hardware health checks supported by their extension. |
-| Solution builder extension download | The Solution Builder Extension package can implement **download connector** interfaces that allow Azure Local to download future SBE updates on behalf of the user. This feature enables new updates from your hardware vendor to show a **Ready** state instead of the [AdditionalContentRequired](solution-builder-extension.md#the-additionalcontentrequired-update-state) state mentioned later in this guide. Because these updates are ready to install without needing any files to be [imported](update-via-powershell-23h2.md#step-3-import-and--rediscover-updates) per an Azure Local instance, it makes it easy to install updates across multiple Azure Local instances simultaneously. <br><br> Hardware vendors often require customized SBE credentials for authentication to download their SBE extension files. Refer to your hardware vendor documentation for instructions on providing these credentials during [deployment on the Configuration](../deploy/deploy-via-portal.md#specify-the-deployment-settings) page or starting with Azure Local, version 2411, you can use the `Set-SolutionExtensionSecretLocation` cmdlet to update or add SBE credentials in Key Vault after deployment. |
+| Solution builder extension download | The Solution Builder Extension package can implement **download connector** interfaces that allow Azure Local to download future SBE updates on behalf of the user. This feature enables new updates from your hardware vendor to show a **Ready** state instead of the [AdditionalContentRequired](solution-builder-extension.md#the-additionalcontentrequired-update-state) state mentioned later in this guide. Because these updates are ready to install without needing any files to be [imported](update-via-powershell-23h2.md#step-3-import-and-rediscover-updates) per an Azure Local instance, it makes it easy to install updates across multiple Azure Local instances simultaneously. <br><br> Hardware vendors often require customized SBE credentials for authentication to download their SBE extension files. Refer to your hardware vendor documentation for instructions on providing these credentials during [deployment on the Configuration](../deploy/deploy-via-portal.md#specify-the-deployment-settings) page or starting with Azure Local, version 2411, you can use the `Set-SolutionExtensionSecretLocation` cmdlet to update or add SBE credentials in Key Vault after deployment. |
 | Customized deployment | The Solution Builder Extension package can implement customized steps that are executed automatically as part of the system deployment process. <br/><br/> Hardware vendors typically use this capability to configure or install any value-add software via their Solution Builder Extension for the solution.  |
 | Customized solution update | The Solution Builder Extension package can implement customized steps that are performed both before and after the main portion of the solution update process. Even when it isn't performing a Solution Builder Extension update, Solution Builder Extension packages that implement this capability always run these extra steps. For example, the execution of hardware vendor specific steps before or after Azure Stack HCI Operating System updates, when no updates to the Solution Builder Extension are needed. <br/><br/> Hardware vendors typically use this capability to prepare nodes for any update related tasks that may involve rebooting machines. |
 
@@ -206,5 +206,5 @@ 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).
+- [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).

azure-local/update/update-via-powershell-23h2.md

@@ -45,8 +45,11 @@ The approximate time estimates for a typical single or multi-node system are sum
 
 |System/Time           |Time for health check<br>*hh:mm:ss*  |Time to install update<br>*hh:mm:ss*  |
 |------------------|-------------------------------------|---------|
-|Single node     | 0:01:44	        |1:25:42         |
-|4-nodes    | 0:01:58	        |3:53:09         |
+|Single node     | ~ 03:00        |~ 01:30         |
+|4-nodes    | ~ 05:00       |~ 04:00         |
+
+> [!IMPORTANT]
+> Use of 3rd party tools to install updates is not supported.
 
 ## Prerequisites
 
@@ -152,7 +155,7 @@ Follow these steps to discover the available updates for your system:
 
     Here's an example output:
 
-    ```console    
+    ```console
     PS C:\Users\lcmuser> Get-SolutionUpdate | Where-Object {$_.State -like "Ready*" -or $_.State -like "Additional*"} | FL DisplayName, Description, ResourceId, State, PackageType
 
     DisplayName           : 2024.10 Cumulative Update
@@ -263,11 +266,11 @@ Follow these steps to discover the available updates for your system:
 
 You can now proceed to [Download and install the updates](#step-2-discover-the-updates).
 
-### Step 3: Import and  rediscover updates
+## Step 3: Import and rediscover updates
 
-Importing updates could be required in one of the following scenarios:
+This is an *optional* step. Importing updates could be required in one of the following scenarios:
 
-- The update you wish to install reports an `AdditionalContentRequired` state. Some extra content may be required before you can schedule the update in the `AdditionalContentRequired`state. For details on this state and on solution extension updates, see [Solution  Extension updates on Azure Local, version 23H2](./solution-builder-extension.md).
+- The update you wish to install reports an `AdditionalContentRequired`state. Some extra content may be required before you can schedule the update in the `AdditionalContentRequired`state. For details on this state and on solution extension updates, see [Solution  Extension updates on Azure Local, version 23H2](./solution-builder-extension.md).
 
 - The update you wish to install isn't listed because Support is providing you with a private release to address an issue you're experiencing.
 
@@ -292,7 +295,6 @@ Follow these steps to import and discover your solution updates.
     |-------------------------------------------|---------------------------------|-----------------------------------------------------|
     | SBE_Discovery_\<Manufacturer>\.xml          | SBE_Discovery_Contoso.xml       | A solution extension discovery manifest that enables update discovery.   |
     | SBE_\<Manufacturer>\_\<Family>\_\<Version>\.xml | SBE_Contoso_GenA_4.1.2410.5.xml | A file with solution extension inventory and signed software Bill of Materials |
-    |                                           |
     | SBE_\<Manufacturer>\_\<Family>\_\<Version>\.zip | SBE_Contoso_GenA_4.1.2410.5.zip | A file with solution extension payload                                         |
 
 1. Create a folder for discovery by the update service at the following location in the infrastructure volume of your system.
@@ -393,7 +395,7 @@ $InstanceId = Get-SolutionUpdate -Id <ResourceId>  | Start-SolutionUpdate
 ```
 
 > [!NOTE]
-> If step 3 was skipped (and you did not make a similar call to Start-SolutionUpdate -PrepareOnly) calling Start-SolutionUpdate will first download the updates and perform a set of checks to verify your cluster's update readiness prior to starting the update install.
+> If step 4 was skipped (and you did not make a similar call to `Start-SolutionUpdate -PrepareOnly`) calling `Start-SolutionUpdate` first downloads the updates and performs a set of checks to verify your cluster's update readiness prior to starting the update install.
 
 
 <details>
@@ -429,11 +431,11 @@ Follow these steps to track update progress using PowerShell.
 
     The update progresses through several states as described in [Review update phases](./update-phases-23h2.md#review-update-phases-of-azure-local-version-23h2).
 
-    Using the above command the following examples show how to monitor the update as it progresses through those phases using the State and `UpdateStateProperties` properties.
+    Using the above command the following examples show how to monitor the update as it progresses through those phases using the `State` and `UpdateStateProperties` properties.
 
     - **Downloading state**
     
-        Shortly after Start-SolutionUpdate is called, the download of the updates begins. Depending on the size of the download package and the network bandwidth, the download might take several minutes.
+        Shortly after `Start-SolutionUpdate` is called, the download of the updates begins. Depending on the size of the download package and the network bandwidth, the download might take several minutes.
     
         <details>
         <summary>Expand this section to see an example output.</summary>
@@ -475,7 +477,7 @@ Follow these steps to track update progress using PowerShell.
     
         Once the updates are prepared, readiness checks are performed to assess the update readiness of your cluster. For more information about the readiness checks, see [Update phases](./update-phases-23h2.md#phase-2-readiness-checks-and-staging).
 
-        During this phase, the State of the update shows as `HealthChecking`. If the `State` of the update shows as `HealthCheckFailed`, see [Troubleshoot readiness checks](./update-troubleshooting-23h2.md) before you proceed.
+        During this phase, the `State` of the update shows as `HealthChecking`. If the `State` of the update shows as `HealthCheckFailed`, see [Troubleshoot readiness checks](./update-troubleshooting-23h2.md) before you proceed.
         
         <details>
         <summary>Expand this section to see an example output.</summary>
@@ -494,7 +496,7 @@ Follow these steps to track update progress using PowerShell.
         </details>
 
     - **Installing state**
-        When the system is ready, the update transitions to the installing state. During this phase, the State of the updates shows as Installing and UpdateStateProperties shows the percentage of the installation that was completed.
+        When the system is ready, the update transitions to `Installing`. During this phase, the `State` of the updates shows as `Installing` and `UpdateStateProperties` shows the percentage of the installation that was completed.
 
         <details>
         <summary>Expand this section to see an example output.</summary>
@@ -523,7 +525,7 @@ To resume a previously failed update run via PowerShell, use the following comma
 Get-SolutionUpdate -Id <ResourceId>  | Start-SolutionUpdate
 ```
 
-To resume a previously failed update due to update readiness checks in a Warning state, use the following command:
+To resume a previously failed update due to update readiness checks in a `Warning` state, use the following command:
 
 ```powershell
 Get-SolutionUpdate -Id <ResourceId>  | Start-SolutionUpdate -IgnoreWarnings    

azure-local/upgrade/about-upgrades-23h2.md

@@ -3,7 +3,7 @@ title: About Azure Local upgrade to version 23H2
 description: Learn how to upgrade from Azure Local, version 22H2 to Azure Local, version 23H2.
 author: alkohli
 ms.topic: conceptual
-ms.date: 11/26/2024
+ms.date: 12/30/2024
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-stack-hci
@@ -62,6 +62,7 @@ The following diagram illustrates the Azure Local upgrade process:
 > [!IMPORTANT]
 > - Consult your hardware OEM before you upgrade Azure Local. Validate that your OEM supports the version and the upgrade.
 > - Upgrading your Azure Local from version 22H2 is only supported for regions where Azure Local, version 23H2 is available. For more information, see [Azure Local region availability](../concepts/system-requirements-23h2.md#azure-requirements).
+> - Use of 3rd party tools to install upgrades is not supported.
 
 Azure Local upgrade supports the following services and workloads:
 

azure-local/upgrade/install-solution-upgrade.md

@@ -40,6 +40,11 @@ Before you install the solution upgrade, make sure that you:
 
 You install the solution upgrade via the Azure portal.
 
+> [!IMPORTANT]
+> Use of 3rd party tools to install updates is not supported.
+
+Follow these steps to install the solution upgrade:
+
 1. Go to your Azure Local resource in Azure portal.
 1. In the **Overview** page, you can see a banner indicating that a solution upgrade is available. Select the **Upgrade** link in the banner.
 

azure-local/upgrade/upgrade-22h2-to-23h2-powershell.md

@@ -47,6 +47,9 @@ Before you begin, make sure that:
 
 > [!NOTE]
 > The ISO file is only required if the machines do not have access to Windows Update to download the OS feature update. If using this method, after you [Connect to Azure Local, version 22H2](#step-1-connect-to-azure-local), skip to step 6 under [Step 2: Install new OS using PowerShell](#step-2-install-new-os-using-powershell) and perform the remaining steps.
+> Use of 3rd party tools to install upgrades is not supported.
+
+Follow these steps to install the solution upgrade:
 
 ## Step 1: Connect to Azure Local