Merge pull request #3959 from MicrosoftDocs/main638978042481046607sync_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/concepts/rack-aware-cluster-reference-architecture.md

@@ -68,7 +68,7 @@ The following switch capabilities are required:
 
 > [!IMPORTANT]
 > **RDMA QoS requirement:**
-> All interfaces that support RDMA (SMB) traffic are **required** to implement [QoS policies](https://github.com/ebmarquez/AzureLocal-Supportability/blob/main/TSG/Networking/Top-Of-Rack-Switch/Reference-TOR-QOS-Policy-Configuration.md). This includes both host-facing storage interfaces and room-to-room links carrying storage VLANs (711, 712). Proper QoS configuration is essential for maintaining lossless, low-latency RDMA performance across the cluster.
+> All interfaces that support RDMA (SMB) traffic are **required** to implement [QoS policies](https://github.com/azure/AzureLocal-Supportability/blob/main/TSG/Networking/Top-Of-Rack-Switch/Reference-TOR-QOS-Policy-Configuration.md). This includes both host-facing storage interfaces and room-to-room links carrying storage VLANs (711, 712). Proper QoS configuration is essential for maintaining lossless, low-latency RDMA performance across the cluster.
 
 **Design considerations:**
 
@@ -381,13 +381,13 @@ The QoS configuration uses the Data Center Bridging (DCB) framework to establish
 
 For environments supporting RoCEv2, ECN is implemented to prevent incast situations. When congestion is detected along the connection path between nodes, the DSCP field is marked, and the destination device instructs senders to reduce their traffic flow.
 
-For more information, see [Azure Local QoS policy](https://github.com/ebmarquez/AzureLocal-Supportability/blob/main/TSG/Networking/Top-Of-Rack-Switch/Reference-TOR-QOS-Policy-Configuration.md).
+For more information, see [Azure Local QoS policy](https://github.com/azure/AzureLocal-Supportability/blob/main/TSG/Networking/Top-Of-Rack-Switch/Reference-TOR-QOS-Policy-Configuration.md).
 
 ## Software defined networking
 
 Azure Local rack aware clusters support Software Defined Networking (SDN) implementations for advanced network virtualization and micro-segmentation requirements. SDN integration enables centralized network policy management and enhanced security isolation between workloads across availability zones.
 
-For more information, see the [Software Defined Networking configuration guide](https://github.com/ebmarquez/AzureLocal-Supportability/blob/main/TSG/Networking/SDN-Express/HowTo-SDNExpress-SDN-Layer3-Gateway-Configuration.md).
+For more information, see the [Software Defined Networking configuration guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Networking/SDN-Express/HowTo-SDNExpress-SDN-Layer3-Gateway-Configuration.md).
 
 ## Next steps
 

azure-local/plan/cloud-deployment-network-considerations.md

@@ -235,6 +235,12 @@ Rename-NetAdapter -Name "vEthernet (ConvergedSwitch(MgmtCompute))" -NewName "vMa
 
 ```
 
+> [!NOTE]
+> During deployment validation, all vSwitches on nodes must have corresponding vNICs. If there are vSwitches present but no matching vNICs, the operation fails with the following error:  
+> *"Could not complete the operation. 200: There are vSwitches present on the nodes but no vnics, this scenario is not supported."*  
+> Ensure the names of the adapters match between the outputs of `Get-NetAdapter` and `Get-VMNetworkAdapter -ManagementOS`. If they don’t match, rename the NICs before retrying deployment.
+
+
 #### 3. Configure VLAN ID to management virtual network adapter for all nodes
 
 Once the virtual switch and the management virtual network adapter are created, you can specify the required VLAN ID for this adapter. Although there are different options to assign a VLAN ID to a virtual network adapter, the only supported option is to use the `Set-VMNetworkAdapterIsolation` command.