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 Stack HCI]]. SET works well with compute, storage, and management traffic and is supported with up to eight adapters in the same team.^[[Host network requirements for Azure Stack HCI - Azure Stack HCI | Microsoft Learn](https://learn.microsoft.com/en-us/azure-stack/hci/concepts/host-network-requirements#switch-embedded-teaming-set)] > [!Note] >  Azure Stack HCI doesn’t support NIC teaming with the older [[Load Balancing/Failover (LBFO)]]. # Load Balancing Mode There are two Load Balancing distribution modes for SET Teams. They are: - Hyper-V Port - Dynamic ## Hyper-V Port When using Hyper-V port mode for SET Teams, VMs are connected to a port on the Hyper-V Switch. This is just like a physical server would be connected to a port on a physical switch. The Hyper-V Virtual Switch port and the VM’s MAC address are used to divide the network traffic between the SET Team members. If you use Switch Embedded Teaming with [[Packet Direct]], you must use the Switch Independent Teaming mode and the Hyper-V port load balancing mode. > Hyper-V port mode is not the best if you are only hosting a few VMs due to it not being granular enough to achieve a well-balanced distribution. This mode also limits each VM to the bandwidth that’s available on a single NIC. - [Veeam](https://www.veeam.com/blog/hyperv-set-management-using-powershell.html) # Create SET Switch Create the SET Switch ```PowerShell New-VMSwitch -Name "SET Team" -NetAdapterName "NIC 1" -EnableEmbeddedTeaming $true ``` ```PowerShell Get-NetAdapter ```