Sync release-hotfixes with main

Sync release-hotfixes with main

Author: sethmanheim

AKS-Arc/disable-windows-nodepool.md

@@ -90,7 +90,7 @@ az k8s-extension update --resource-group $resourceGroup --cluster-name $clusterN
 If for some reason you're not able to use Azure CloudShell or a machine with connectivity to Azure in order to disable Windows nodepool, you can disable Windows nodepool after connecting to any one of the Azure Local physical nodes with Remote Desktop. You must first sign in to Azure.
 
 ```powershell
-az login --use-device-code --tenant-id <Azure tenant ID>
+az login --use-device-code --tenant <Azure tenant ID>
  
 az account set -s <subscription ID>
  

azure-local/TOC.yml

@@ -35,15 +35,15 @@ items:
   - name: Virtual deployment
     href: deploy/deployment-virtual.md
   - name: Azure Local jumpstart
-    href: https://arcjumpstart.com/azure_jumpstart_hcibox/getting_started
+    href: https://jumpstart.azure.com/azure_jumpstart_localbox
 
 - name: Plan
   items:
   - name: Review requirements
     items:
     - name: System requirements
       href: concepts/system-requirements-23h2.md
-    - name: System requirements for Small Form Factor
+    - name: System requirements for low capacity class
       href: concepts/system-requirements-small-23h2.md
     - name: Physical network requirements
       href: concepts/physical-network-requirements.md
@@ -527,9 +527,9 @@ items:
   - name: Migrate using SCVMM
     items:
     - name: For Hyper-V VMs
-      href: /system-center/vmm/manage-azure-stack-hci?toc=/azure/azure-local/toc.json&bc=/azure/azure-local/breadcrumb/toc.json#migrate-vms-from-windows-server-to-azure-local-instance
+      href: /system-center/vmm/manage-azure-stack-hci#migrate-vms-from-windows-server-to-azure-local-instance
     - name: For VMware VMs
-      href: /system-center/vmm/vm-convert-vmware?toc=/azure/azure-local/toc.json&bc=/azure/azure-local/breadcrumb/toc.json
+      href: /system-center/vmm/vm-convert-vmware
   - name: Migrate manually (v22H2 only)
     items:
     - name: To same hardware
@@ -711,9 +711,9 @@ items:
   - name: Migrate using SCVMM
     items:
     - name: For Hyper-V VMs
-      href: /system-center/vmm/deploy-manage-azure-stack-hci?toc=/azure/azure-local/toc.json&bc=/azure/azure-local/breadcrumb/toc.json#step-8-migrate-vms-from-windows-server-to-azure-local-instance
+      href: /system-center/vmm/deploy-manage-azure-stack-hci#step-8-migrate-vms-from-windows-server-to-azure-local-instance
     - name: For VMware VMs
-      href: /system-center/vmm/deploy-manage-azure-stack-hci?toc=/azure/azure-local/toc.json&bc=/azure/azure-local/breadcrumb/toc.json#step-9-migrate-vmware-workloads-to-azure-local-instance-using-scvmm
+      href: /system-center/vmm/deploy-manage-azure-stack-hci#step-9-migrate-vmware-workloads-to-azure-local-instance-using-scvmm
   - name: Concepts
     items:
     - name: Storage and systems

azure-local/concepts/system-requirements-small-23h2.md

@@ -1,68 +1,63 @@
 ---
-title: System requirements for small deployments of Azure Local, version 23H2 (preview)
-description: How to choose machines, storage, and networking components for small deployments of Azure Local, version 23H2 (preview).
+title: System requirements for low capacity deployments of Azure Local (preview)
+description: How to choose machines, storage, and networking components for low capacity deployments of Azure Local (preview).
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
 ms.custom: references_regions
-ms.date: 04/03/2025
+ms.date: 05/07/2025
 ---
 
-# System requirements for small form factor deployments of Azure Local (Preview)
+# System requirements for low capacity deployments of Azure Local (Preview)
 
 ::: moniker range=">=azloc-2411"
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-This article describes the requirements for machines, storage, and networking for building solutions of Azure Local that use the small form factor hardware. If you purchase class *small* hardware from the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog), ensure that these requirements are met before you deploy the Azure Local solutions.
+This article describes the requirements for machines, storage, and networking for building solutions of Azure Local that use lower capacity hardware. If you purchase lower capacity hardware from the [Azure Local Catalog](https://aka.ms/azurelocalcatalog), ensure that these requirements are met before you deploy the Azure Local solutions.
 
 [!INCLUDE [important](../includes/hci-preview.md)]
 
-## About the small hardware class
+## About the low capacity class
 
-Azure Local supports a new class of devices with reduced hardware requirements. This new, low-cost hardware class referenced as *small* is suited for various edge scenarios across the industry horizontals. To ensure compatibility, interoperability, security, and reliability, this class of hardware must meet Azure Local solution requirements.
-
-The certified devices are listed in the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog).
+Azure Local supports a new class of devices with reduced hardware requirements. This new, low-cost hardware class called *low capacity* is suited for various edge scenarios across industry. To ensure compatibility, interoperability, security, and reliability, this class of hardware must meet Azure Local solution requirements.
 
 ## Device requirements
 
 Microsoft Support may only be provided for Azure Local running on hardware listed in the [Azure Local catalog, or successor](https://aka.ms/azurelocalcatalog).
 
-The following table lists the requirements for the small hardware:
+The following table lists the requirements for low capacity hardware:
 
 | Component | Description |
 |-----------|-------|
-| Number of machines | 1 to 3 machines are supported. Each machine must be the same model, manufacturer, have the same network adapters, and have the same number and type of storage drives. |
+| Number of machines | One to three machines are supported. Each machine must be the same model, manufacturer, have the same network adapters, and have the same number and type of storage drives. |
 | CPU | An Intel Xeon or AMD EPYC or later compatible processor with second-level address translation (SLAT). <br> Up to 14 physical cores |
 | Memory | A minimum of 32 GB per machine and a maximum of 128 GB per machine with Error-Correcting Code (ECC). |
-| Host network adapters | 1 network adapter that meets the [Azure Local host network requirements](./host-network-requirements.md)<br> Enabling RDMA on storage intend is not required.<br> Minimum link speed must be 1 Gbit/s. |
+| Host network adapters | One network adapter that meets the [Azure Local host network requirements](./host-network-requirements.md)<br> Enabling RDMA on storage intent isn't required.<br> Minimum link speed must be 1 Gbps for single node deployment.<br>In two or three node deployments, a dedicated network port for storage with minimum 10 Gbps is required.   |
 | BIOS | Intel VT or AMD-V must be turned on.|
 | Boot drive | A minimum size of 200 GB.|
 | Data drives | A minimum single disk of capacity 1 TB. <br> The drives must be all flash single drive type, either Nonvolatile Memory Express (NVME) or Solid-State Drive (SSD). <br> All the drives must be of the same type. <br> No caching. |
 | Trusted Platform Module (TPM) | TPM version 2.0 hardware must be present and enabled. |
 | Secure Boot | Secure Boot must be present and turned on. |
 | Storage Controller | Pass-through. <br> RAID controller cards or SAN (Fibre Channel, iSCSI, FCoE) aren't supported. |
-| GPU | Optional<br>Up to 192 GB GPU memory per machine. |
-
->[!IMPORTANT]
-> For 2411 release, Update, `Add-server`, and `Repair-server` operations aren't supported for the small hardware class.
+| GPU | Optional<br>Up to 192-GB GPU memory per machine. |
 
 ## Storage requirements
 
-The storage subsystem for an Azure Local running Azure Stack HCI OS is layered on top of Storage Space Direct. When building a solution using class *small* hardware:
+The storage subsystem for an Azure Local running the Azure Stack HCI OS is layered on top of Storage Spaces Direct. When building a solution using class *low capacity* hardware:
 
 - A minimum of one data drive is required to create a storage pool.
 - All drives in the pool must be of the same type, either NVMe or SSD.
-- Remember that mixing drive types for caching (NVMe and SSD, or SSD and HDD) isn't supported.
+- Mixing drive types used for caching (NVMe and SSD) isn't supported. It is supported for the boot drive however.  
 
 The supported volume configuration for the system is:
 
 - A single, 250 GB, fixed infrastructure volume.
 
 ### Supported sample storage configurations
 
-| Node count | Disk count | Disk type | Volume resiliency level | Sustain faults |
+| Nodes | Disks | Disk type | Volume resiliency level | Sustain faults |
 |------------|------------|-----------|-------------------------|----------------|
 | 1 | 1 | NVMe or SSD | Simple | None |
 | 2 | 1 | NVMe or SSD | Two way mirror | Single fault (drive or node) |
@@ -75,36 +70,52 @@ The supported volume configuration for the system is:
 
 Network adapters must meet the Azure Local host network requirements. This requirement ensures compatibility and reliability with Hyper-V and also controls how the adapter properties are exposed by the driver (VLAN ID, RSS, VMQ).
 
-The reduced networking requirements are as follows:
+The minimum networking requirements are as follows:
 
-- Storage intent doesn't require RDMA to be enabled.
-- Single link is needed.
-- Minimum link speed of 1 Gbit/s is required.
+- A network adapter that meets the [Azure Local host network requirements](host-network-requirements.md).
 - A Layer 2 switch with VLAN support is required.
+- Storage intent doesn't require RDMA to be enabled.
 
 Removal of RDMA allows the use of a layer 2 network switch with VLAN support. This further simplifies the configuration management and reduces the overall solution cost.
 
+### Minimum speed requirements
+
+| Single node | Two or three nodes,<br>Switched storage | Two or three nodes,<br>Switchless storage |
+| -- | -- | -- |
+| 1 GbE linked to switch* | Dedicated network port for storage - 10 Gbps minimum.<br><br>Switch capable of 10 Gbps minimum (RDMA optional).<br><br>Management and compute network -1 Gpbs minimum. | Dedicated network adapter ports for storage - 10 Gbps minimum.<br><br>RDMA automatically enabled if supported by adapter.<br><br>Management and compute network via switch - 1 Gpbs minimum. |
+
+> [!NOTE]
+> You can't add nodes to the system without redeploying Azure Local. If you need more nodes, use a dedicated storage intent with a minimum of 10 Gbps.
+
+(Optional) If you use a layer 3 switch with RDMA (10 Gpbs minimum), you can group all traffic (management, compute, and storage intent) together across one, two, and three node clusters.  
+
+### Supported network traffic grouping by intent
+
+| Intent grouping | Single node | Two or three nodes |
+| -- | -- | -- |
+| Management and compute (no storage) | yes | n/a |
+| Management and compute (1 Gbps min),<br>And dedicated storage traffic (10 Gbps) | yes | yes|
+| All traffic | RDMA capable switch, 10 Gbps minimum | RDMA capable switch, 10 Gbps minimum |
+
 ### Supported sample network configurations
 
 | Link count | Intent | Switch type | Sustain faults |
 |------------|--------|-------------|----------------|
 | 2 | Single intent | Switch | Single fault |
 | 2 | Two intents | Switch | None |
 | 4 | Two intents | Switch | Single fault |
-| 3 | Three intents | Switch | None |
 | 2 | Two intents | No switch for storage | None |
 | 4 | Two intents | No switch for storage | Single fault |
-| 6 | Three intents | No switch for storage | Single fault |
 
 ## Considerations
 
-Following are some workload considerations for building a solution using the small hardware class:
+The following are some workload considerations for building a solution using the low capacity hardware:
 
-- Baseline workload IOP requirements for sizing storage configuration to see if small hardware class is the right fit.
-- vCPU requirements and target ratio due to lower total physical cores when using small hardware class.
-- Total memory requirement with three servers using small hardware class. Keep capacity work one node free for update runs and failure scenarios.
+- Baseline workload Input Output operations per second (IOPS) require sizing storage configuration to see if the low capacity hardware is the right fit.
+- vCPU requirements and target ratio due to lower total physical cores when using low capacity hardware.
+- The total memory requirement for three servers using low capacity hardware should be calculated. It's important to ensure that there's enough capacity to keep one node free to handle updates and manage failures.
 - Network bandwidth requirements.
-- The VM creation time is critical as it's influenced by network bandwidth.
+- Virtual machine (VM) creation time is critical and is influenced by network bandwidth.
 
 ### Availability