Merge pull request #3632 from MicrosoftDocs/main638818214260835625sync_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-Arc/auto-scale-aks-arc.md

@@ -5,9 +5,9 @@ ms.topic: how-to
 ms.custom: devx-track-azurecli
 author: sethmanheim
 ms.author: sethm
-ms.date: 08/01/2024
+ms.date: 05/02/2025
 ms.reviewer: abha
-ms.lastreviewed: 08/01/2024
+ms.lastreviewed: 05/02/2025
 
 # Intent: As a Kubernetes user, I want to use cluster autoscaling to grow my nodes to keep up with application demand.
 # Keyword: cluster autoscaling Kubernetes
@@ -19,6 +19,9 @@ ms.lastreviewed: 08/01/2024
 
 To keep up with application demands in Kubernetes, you might need to adjust the number of nodes that run your workloads. The cluster autoscaler component watches for pods in your cluster that can't be scheduled because of resource constraints. When the cluster autoscaler detects issues, it scales up the number of nodes in the node pool to meet the application demands. It also regularly checks nodes for a lack of running pods and scales down the number of nodes as needed. This article shows you how to enable and manage the cluster autoscaler in AKS Arc.
 
+> [!NOTE]
+> Before enabling autoscaling on your Azure Local cluster, review the [Scale requirements for AKS on Azure Local](/azure/aks/aksarc/scale-requirements#scale-requirements-when-using-autoscaler-with-aks-on-azure-local) to ensure your environment meets the required limits.
+
 ## Enable the cluster autoscaler on a new cluster
 
 Create an AKS Arc cluster using the [`az aksarc create`](/cli/azure/aksarc#az-aksarc-create) command, and enable and configure the cluster autoscaler on the node pool for the cluster using the `--enable-cluster-autoscaler` parameter and specifying `--min-count` and `--max-count` for a node. The following example command creates a cluster with a single node, enables the cluster autoscaler, and sets a minimum of one and maximum of three nodes:

AKS-Arc/scale-requirements.md

@@ -2,7 +2,7 @@
 title: Scale requirements for AKS on Azure Local
 description: Learn about scale requirements for AKS on Azure Local.
 ms.topic: conceptual
-ms.date: 03/25/2025
+ms.date: 05/02/2025
 author: sethmanheim
 ms.author: sethm 
 ms.reviewer: abha
@@ -25,17 +25,34 @@ This article describes the maximum and minimum supported scale count for AKS on
 | Number of nodes in default node pool created during cluster create  | 1 | 200 |
 | Number of node pools in an AKS cluster  | 1  | 16  |
 | Number of nodes in a node pool (empty node pools not supported)  | 1 | 64 |
-| Total number of nodes in an AKS cluster across nodepools | 1 | 200 |
-| Number of AKS clusters per Azure Local cluster | 0| 32 |
+| Total number of nodes in an AKS cluster across node pools | 1 | 200 |
+| Number of AKS clusters per Azure Local cluster | 0 | 32 |
 
-## Concurrency for AKS enabled by Arc
+## Concurrency for AKS on Azure Local
 
 | Scale item  | Count  |
 |-------------|--------|
 | Number of concurrent AKS cluster creations on an ARB  | 8 |
 | Number of concurrent node pool creations on an ARB  | 8  |
-| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pool or clusters per ARB  | 32  |
-| Number of long running operations that can be run simultaneously on an AKS cluster  | 1 per cluster.  |
+| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pools or clusters  | 32 |
+| Number of long running operations that can be run simultaneously on an AKS cluster  | 1 per cluster |
+
+## Scale requirements when using autoscaler with AKS on Azure Local
+
+> [!NOTE]
+> When the autoscaler is enabled, AKS on Azure Local currently supports a maximum of 12 clusters per Azure Local environment. If this limit is exceeded, operations such as creating additional clusters or node pools might not succeed. To manage capacity, we recommend deleting unused clusters using the [az aksarc delete](/cli/azure/aksarc#az-aksarc-delete) command.
+>
+> If the autoscaler is enabled in an environment that already exceeds the supported cluster count, performance might be impacted. Managing within supported limits is recommended.
+
+| Scale item  | Count  |
+|-------------|--------|
+| Maximum number of AKS clusters with autoscaler enabled | 12 |
+| Number of concurrent AKS cluster creations | 4 |
+| Number of concurrent node pool creations | 4 |
+
+For more information, see [autoscaling with AKS on Azure Local](/azure/aks/aksarc/auto-scale-aks-arc).
+
+If you operate at enterprise scale and have scenarios that require higher cluster counts with the autoscaler enabled, contact your Microsoft account team or support to discuss potential options.
 
 ## Default values for virtual machine sizes
 

azure-local/deploy/deployment-arc-register-server-permissions.md

@@ -3,7 +3,7 @@ title: Register your Azure Local machines with Azure Arc and assign permissions
 description: Learn how to Register your Azure Local machines with Azure Arc and assign permissions for deployment. 
 author: alkohli
 ms.topic: how-to
-ms.date: 04/03/2025
+ms.date: 05/02/2025
 ms.author: alkohli
 ms.service: azure-local
 ms.custom: devx-track-azurepowershell
@@ -119,10 +119,10 @@ Before you begin, make sure you complete the following prerequisites:
 
     ```powershell
     #Invoke the registration script. Use a supported region.
-    Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region $Region -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id -Proxy $ProxyServer
+    Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region $Region -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id
     ```
 
-    If you're accessing the internet via a proxy server, you need to pass the `-proxy` parameter and provide the proxy server as `http://<Proxy server FQDN or IP address>:Port` when running the script.
+    If you're accessing the internet using a proxy server, you need to add the `-Proxy` parameter and provide the proxy server in the format `http://<Proxy server FQDN or IP address>:Port` when running the script.
 
     For a list of supported Azure regions, see [Azure requirements](../concepts/system-requirements-23h2.md#azure-requirements).
 

azure-managed-lustre/create-file-system-portal.md

@@ -4,9 +4,9 @@ description: Learn how to create an Azure Managed Lustre file system from the Az
 ms.topic: how-to
 author: pauljewellmsft
 ms.author: pauljewell
-ms.date: 11/11/2024
+ms.date: 05/02/2025
 ms.lastreviewed: 06/06/2023
-ms.reviewer: mayabishop
+ms.reviewer: brlepore
 
 #customer intent: As an IT pro, I want to use a Lustre file system to process files that involve a heavy computation load.
 
@@ -66,9 +66,9 @@ Currently, the following throughput configurations are available:
 
 | Throughput per TiB storage | Storage minimum | Storage maximum | Increment |
 |-----------|-----------|-----------|-----------|
-| 40 MBps | 48 TiB | 768 TiB | 48 TiB |
-| 125 MBps | 16 TiB | 128 TiB | 16 TiB |
-| 250 MBps | 8 TiB | 128 TiB | 8 TiB |
+| 40 MBps | 48 TiB | 1536 TiB | 48 TiB |
+| 125 MBps | 16 TiB | 512 TiB | 16 TiB |
+| 250 MBps | 8 TiB | 256 TiB | 8 TiB |
 | 500 MBps | 4 TiB | 128 TiB | 4 TiB |
 
 > [!NOTE]