Skip to content

UUF related to Switch Embedded Teaming #3785

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+4 −7
Open

UUF related to Switch Embedded Teaming #3785

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9be1262
UUF related to Switch Embedded Teaming
ManikaDhiman Aug 7, 2025
b4f555e
Fixed build warning
ManikaDhiman Aug 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions azure-local/concepts/host-network-requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Host network requirements for Azure Local
description: Learn the host network requirements for Azure Local
author: dcuomo
ms.topic: how-to
ms.date: 04/07/2025
ms.date: 08/07/2025
ms.author: dacuo
---

Expand Down Expand Up @@ -137,17 +137,14 @@ Guest RDMA is not supported on Azure Local.

### Switch Embedded Teaming (SET)

SET is a software-based teaming technology that has been included in the Windows Server operating system since Windows Server 2016. SET is the only teaming technology supported by Azure Local. SET works well with compute, storage, and management traffic and is supported with up to eight adapters in the same team.
SET is a software-based teaming technology that has been included in the Windows Server operating system since Windows Server 2016. SET is the only teaming technology supported by Azure Local and well with compute, storage, and management traffic. SET supports up to eight adapters in a single team. Other NIC teaming methods, such as [Load Balancing/Failover (LBFO)](https://techcommunity.microsoft.com/t5/networking-blog/teaming-in-azure-stack-hci/ba-p/1070642), aren't supported.

In Azure Local, Network ATC automatically configures both the SET and the vSwitch. You shouldn't manually deploy SET using PowerShell, such as with the [New-VMSwitch](/powershell/module/hyper-v/new-vmswitch) cmdlet. While this command enables Embedded Teaming by default when multiple adapters are listed, the recommended approach is to use Network ATC with intents.

**Applicable traffic types:** compute, storage, and management

**Certifications required:** Compute (Standard) or Compute (Premium)

SET is the only teaming technology supported by Azure Local. SET works well with compute, storage, and management traffic.

> [!IMPORTANT]
> Azure Local doesn't support NIC teaming with the older Load Balancing/Failover (LBFO). See the blog post [Teaming in Azure Local](https://techcommunity.microsoft.com/t5/networking-blog/teaming-in-azure-stack-hci/ba-p/1070642) for more information on LBFO in Azure Local.

SET is important for Azure Local because it's the only teaming technology that enables:

- Teaming of RDMA adapters (if needed).
Expand Down