Merge pull request #3262 from MicrosoftDocs/main638586467979033444sync_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]

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

@@ -26,7 +26,8 @@ In this conceptual article, the following key components are introduced. These c
 Kubernetes nodes are deployed as specialized virtual machines in AKS enabled by Arc. These VMs are allocated IP addresses to enable communication between Kubernetes nodes. AKS Arc uses Azure Stack HCI logical networks to provide IP addresses and networking for the underlying VMs of the Kubernetes clusters. For more information about logical networks, see [Logical networks for Azure Stack HCI](/azure-stack/hci/manage/create-logical-networks?tabs=azurecli). You must plan to reserve one IP address per AKS cluster node VM in your Azure Stack HCI environment.
 
 > [!NOTE]
-> Static IP is the only supported mode for assigning an IP address to AKS Arc VMs. This is because Kubernetes requires the IP address assigned to a Kubernetes node to be constant throughout the lifecycle of the Kubernetes cluster.
+> Static IP is the only supported mode for assigning an IP address to AKS Arc VMs. This is because Kubernetes requires the IP address assigned to a Kubernetes node to be constant throughout the lifecycle of the Kubernetes cluster. 
+> Software defined virtual networks and SDN related features are currently not supported on AKS on Azure Stack HCI 23H2. 
 
 The following parameters are required in order to use a logical network for AKS Arc cluster create operation:
 

azure-stack/hci/update/update-troubleshooting-23h2.md

@@ -98,13 +98,13 @@ We highly recommend using the Azure portal, to browse to your failed update and
 If you're using PowerShell and need to resume a previously failed update run, use the following command:
 
 ```powershell
-get-solutionupdate | start-solutionupdate
+Get-SolutionUpdate | Start-SolutionUpdate
 ```
 
 To resume a previously failed update due to update health checks in a **Warning** state, use the following command:
 
 ```powershell
-get-solutionUpdate | start-solutionUpdate -IgnoreWarnings
+Get-SolutionUpdate | Start-SolutionUpdate -IgnoreWarnings
 ```
 
 ## Next steps

azure-stack/hci/update/update-via-powershell-23h2.md

@@ -357,7 +357,7 @@ You can download the updates, perform a set of checks to verify your cluster's u
     - To download and install the update, run the following command:
 
         ```powershell
-        Get-SolutionUpdate | ? version -eq "10.2302.0.31"
+        Get-SolutionUpdate | ? version -eq "10.2302.0.31" | Start-SolutionUpdate
         ```
 
     - To only download the updates without starting the installation, use the `-PrepareOnly` flag with `Start-SolutionUpdate`.
@@ -469,13 +469,13 @@ After the updates are installed, verify the solution version of the environment
 To resume a previously failed update run via PowerShell, use the following command:
 
 ```powershell
-get-solutionupdate | start-solutionupdate
+Get-SolutionUpdate | Start-SolutionUpdate
 ```
 
 To resume a previously failed update due to update health checks in a **Warning** state, use the following command:
 
 ```powershell
-get-solutionUpdate | start-solutionUpdate -IgnoreWarnings
+Get-SolutionUpdate | Start-SolutionUpdate -IgnoreWarnings
 ```
 
 To troubleshoot other update run issues, see [Troubleshoot updates](./update-troubleshooting-23h2.md).

azure-stack/zone-pivot-groups.yml

@@ -74,7 +74,14 @@ groups:
     title: Version 23H2
   - id: aks-22h2
     title: Version 22H2
-
+- id: windows-os
+  title: Products
+  prompt: "Choose your product:"
+  pivots:
+  - id: windows-server
+    title: Windows Server
+  - id: azure-stack-hci
+    title: Azure Stack HCI
 # BELOW: entries inherited from github.com/microsoftdocs/azure-docs-pr/articles/zone-pivot-groups.yml for reuse.
 # For consistency across Docs. This includes: client OSes, languages, etc.