Updated text

Author: ronmiab

.openpublishing.publish.config.json

@@ -22,7 +22,7 @@
       "locale": "en-us",
       "monikers": [],
       "moniker_ranges": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
         "Conceptual": "Content"
       },

azure-local/TOC.yml

@@ -229,9 +229,9 @@ items:
   - name: Deploy workloads
     items:
     - name: Run AKS on Azure Local
-      href: /azure/aks/hybrid/aks-create-clusters-portal?toc=/azure-local/toc.json&bc=/azure-local/breadcrumb/toc.json
+      href: /azure/aks/hybrid/aks-create-clusters-portal?toc=/azure/azure-local/toc.json&bc=/azure/azure-local/breadcrumb/toc.json
     - name: Run Azure Virtual Desktop on Azure Local
-      href: /azure/virtual-desktop/deploy-azure-virtual-desktop?toc=/azure-local/toc.json&bc=/azure-local/breadcrumb/toc.json
+      href: /azure/virtual-desktop/deploy-azure-virtual-desktop?toc=/azure/azure-local/toc.json&bc=/azure/azure-local/breadcrumb/toc.json
     - name: Run Azure Arc VMs
       href: manage/create-arc-virtual-machines.md
     - name: Run SQL Server
@@ -360,14 +360,14 @@ items:
         href: manage/vm-affinity.md
       - name: VM load balancing
         href: manage/vm-load-balancing.md
-    #  - name: Dynamic CPU compatibility
-    #    href: /windows-server/virtualization/hyper-v/manage/dynamic-processor-compatibility-mode?pivots=azure-stack-hci&context=/azure-local/context/context
-    #  - name: Use GPUs with clustered VMs
-    #    href: /windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm?pivots=azure-stack-hci&context=/azure-local/context/context
-    #  - name: GPU Partitioning
-    #    href: /windows-server/virtualization/hyper-v/gpu-partitioning?pivots=azure-stack-hci&context=/azure-local/context/context
-    #  - name: Partition and assign GPUs to a virtual machine
-    #    href: /windows-server/virtualization/hyper-v/partition-assign-vm-gpu?pivots=azure-stack-hci&context=/azure-local/context/context
+      - name: Dynamic CPU compatibility
+        href: /windows-server/virtualization/hyper-v/manage/dynamic-processor-compatibility-mode?pivots=azure-local&context=/azure/azure-local/context/context
+      - name: Use GPUs with clustered VMs
+        href: /windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm?pivots=azure-local&context=/azure/azure-local/context/context
+      - name: GPU Partitioning
+        href: /windows-server/virtualization/hyper-v/gpu-partitioning?pivots=azure-local&context=/azure/azure-local/context/context
+      - name: Partition and assign GPUs to a virtual machine
+        href: /windows-server/virtualization/hyper-v/partition-assign-vm-gpu?pivots=azure-local&context=/azure/azure-local/context/context
       - name: Attach GPU to Linux VM
         href: manage/attach-gpu-to-linux-vm.md
 
@@ -415,7 +415,7 @@ items:
     - name: Use Azure Site Recovery
       href: manage/azure-site-recovery.md
     - name: Use Azure Backup
-      href: /azure/backup/back-up-azure-stack-hyperconverged-infrastructure-virtual-machines?toc=/azure-local/toc.json&bc=/azure-local/breadcrumb/toc.json
+      href: /azure/backup/back-up-azure-stack-hyperconverged-infrastructure-virtual-machines?toc=/azure/azure-local/toc.json&bc=/azure/azure-local/breadcrumb/toc.json
 
   - name: Azure Arc extensions
     items:
@@ -599,9 +599,9 @@ items:
   - name: Migrate using SCVMM (v22H2 only)
     items:
     - name: For Hyper-V VMs
-      href: /system-center/vmm/deploy-manage-azure-stack-hci?toc=/azure-local/toc.json&bc=/azure-local/breadcrumb/toc.json#step-8-migrate-vms-from-windows-server-to-azure-stack-hci-cluster
+      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-stack-hci-cluster
     - name: For VMware VMs
-      href: /system-center/vmm/deploy-manage-azure-stack-hci?toc=/azure-local/toc.json&bc=/azure-local/breadcrumb/toc.json#step-9-migrate-vmware-workloads-to-azure-stack-hci-cluster-using-scvmm
+      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-stack-hci-cluster-using-scvmm
   - name: Migrate manually (v22H2 only)
     items:
     - name: To same hardware
@@ -681,7 +681,7 @@ items:
       - name: Deploy at system creation
         href: deploy/create-cluster.md#step-5-sdn-optional
     - name: Deploy and manage in VMM
-      href: /system-center/vmm/deploy-manage-azure-stack-hci?toc=/azure-local/toc.json&bc=/azure-local/breadcrumb/toc.json  
+      href: /system-center/vmm/deploy-manage-azure-stack-hci?toc=/azure/azure-local/toc.json&bc=/azure/azure-local/breadcrumb/toc.json  
     - name: Deploy workloads
       items: 
       - name: Branch office and edge
@@ -761,15 +761,15 @@ items:
       - name: Change privacy settings
         href: manage/change-privacy-settings.md
       - name: Use BitLocker with Cluster Shared Volumes
-        href: /windows-server/failover-clustering/bitlocker-on-csv-in-ws-2022?context=/azure-local/context/context
+        href: /windows-server/failover-clustering/bitlocker-on-csv-in-ws-2022?context=/azure/azure-local/context/context
     - name: Manage Azure services
       items:
       - name: Hybrid capabilities with Azure services
         href: hybrid-capabilities-with-azure-services.md
       - name: Register Windows Admin Center with Azure
         href: manage/register-windows-admin-center.md
       - name: Use Windows Admin Center in Azure
-        href: /windows-server/manage/windows-admin-center/azure/manage-hci-clusters?context=/azure-local/context/context
+        href: /windows-server/manage/windows-admin-center/azure/manage-hci-clusters?context=/azure/azure-local/context/context
       - name: Use Azure portal
         href: manage/azure-portal.md
     - name: Manage SDN 
@@ -785,11 +785,11 @@ items:
     - name: Troubleshoot CredSSP
       href: manage/troubleshoot-credssp.md
     - name: Troubleshoot live migration
-      href: /troubleshoot/windows-server/virtualization/troubleshoot-live-migration-issues?context=/azure-local/context/context
+      href: /troubleshoot/windows-server/virtualization/troubleshoot-live-migration-issues?context=/azure/azure-local/context/context
     - name: Troubleshoot Storage Spaces Direct
-      href: /windows-server/storage/storage-spaces/troubleshooting-storage-spaces?context=/azure-local/context/context
+      href: /windows-server/storage/storage-spaces/troubleshooting-storage-spaces?context=/azure/azure-local/context/context
     - name: Troubleshoot storage health
-      href: /windows-server/storage/storage-spaces/storage-spaces-states?context=/azure-local/context/context
+      href: /windows-server/storage/storage-spaces/storage-spaces-states?context=/azure/azure-local/context/context
     - name: Collect diagnostic data
       href: manage/collect-diagnostic-data.md
   - name: Concepts
@@ -916,5 +916,5 @@ items:
   - name: Azure Local product page
     href: https://azure.com/hci
   - name: Pricing
-    href: https://azure.microsoft.com/pricing/details/azure-stack/hci/
+    href: https://azure.microsoft.com/products/local/#Pricing
 

azure-local/concepts/physical-network-requirements.md

@@ -197,12 +197,16 @@ If your switch isn't included, contact your switch vendor to ensure that your sw
 ### 23H2
 |Model |Firmware| Management | Storage | Compute (Standard)| Compute (SDN)|
 |-----  |---| :-:  | :-:  | :-:   | :-:   |
+| [M4250](https://www.downloads.netgear.com/files/GDC/M4250/M4250_Datasheet.pdf) <br>(1, 2.5, 10 GbE)|Version 13.0.4.26 or later  |&check;| | &check;| |
+| [M4350](https://www.downloads.netgear.com/files/GDC/M4350/M4350_Datasheet.pdf) <br>(1, 2.5, 5, 10, 25, 100 GbE)|Version 14.0.2.26 or later   |&check;| | &check;| |
 | [M4500](https://www.netgear.com/assets/campaign/121401/images/m4500.pdf) <br>(10, 25, 100 GbE)|Version 7.0.3.9 or later  |&check;| | &check;| &check; |
 > [!NOTE]
 > Guest RDMA requires both Compute (Standard) and Storage.
 ### 22H2
 |Model |Firmware| Management | Storage | Compute (Standard)| Compute (SDN)|
 |-----  |---| :-:  | :-:  | :-:   | :-:   |
+| [M4250](https://www.downloads.netgear.com/files/GDC/M4250/M4250_Datasheet.pdf) <br>(1, 2.5, 10 GbE)|Version 13.0.4.26 or later  |&check;| | &check;| |
+| [M4350](https://www.downloads.netgear.com/files/GDC/M4350/M4350_Datasheet.pdf) <br>(1, 2.5, 5, 10, 25, 100 GbE)|Version 14.0.2.26 or later   |&check;| | &check;| |
 | [M4500](https://www.netgear.com/assets/campaign/121401/images/m4500.pdf) <br>(10, 25, 100 GbE)|Version 7.0.3.9 or later  |&check;| | &check;| &check; |
 > [!NOTE]
 > Guest RDMA requires both Compute (Standard) and Storage.

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

@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-stack-hci
 ms.custom: references_regions
-ms.date: 11/14/2024
+ms.date: 11/19/2024
 ---
 
 # System requirements for small form factor deployments of Azure Local, version 23H2 (preview)
@@ -19,13 +19,13 @@ This article describes the requirements for machines, storage, and networking fo
 
 ## About the small hardware 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 the Windows Server certification requirements as well as relaxed requirements from Software Defined Data Center (SDDC) and Windows Server Software-Defined (WSSD) program.
+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) as *small form factor* hardware.
+The certified devices are listed in the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog).
 
 ## Device requirements
 
-The device must be listed in the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog) which indicates that the device has passed the Windows Server certification and the extra qualifications from the SDDC and WSSD program.
+The device must be listed in the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog) which indicates that the device has passed the Windows Server certification and the extra qualifications.
 
 The following table lists the requirements for the small hardware:
 
@@ -34,7 +34,7 @@ The following table lists the requirements for the small hardware:
 | 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. |
 | 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 EEC. |
-| Host network adapters | Two network adapters listed in the [Windows Server Catalog](https://www.windowsservercatalog.com/).<br> RDMA isn't required for storage intent.<br> Minimum link speed must be 1 Gbit/s. |
+| 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. |
 | 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. |
@@ -71,11 +71,11 @@ The supported volume configuration for the system is:
 
 ## Networking requirements
 
-Network adapters must meet the Windows Server certification 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).
+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:
 
-- Storage intent doesn't require RDMA.
+- Storage intent doesn't require RDMA to be enabled.
 - Single link is needed.
 - Minimum link speed of 1 Gbit/s is required.
 - A Layer 2 switch with VLAN support is required.

azure-local/manage/disconnected-operations-overview.md

@@ -40,7 +40,7 @@ Disconnected operations for Azure Local support the following services:
 | Azure portal                      | Delivers an Azure portal experience that's similar to Azure Public. |
 | Azure Resource Manager (ARM)      | Manage and utilize subscriptions, resource groups, ARM templates, and Azure Command-Line Interface (CLI). |
 | Role Based Access Control (RBAC)  | Implement RBAC for subscriptions and resource groups. |
-| Managed Service Identity (MSI)    | Access resources with MSI support for user workloads. |
+| Managed Identity                  | Access resources with Managed Identity support for user workloads. |
 | Arc-enabled servers               | Manage VM Guests for Arc VMs on Azure Local. |
 | Arc VMs for Azure Local           | Set up and manage Windows or Linux virtual machines using the disconnected operations feature for Azure Local. |
 | Arc-enabled Kubernetes (K8s)      | Connect and manage Cloud Native Computing Foundation (CNCF) Kubernetes clusters deployed on Azure Local virtual machines, enabling unified configuration and management. |