Unable to receive tagged VLAN traffic on VMs connected through switch embedded teaming (SET)

Foil Benny 20 Reputation points
2026-07-29T01:25:46.7766667+00:00

Hello Microsoft Support team,

We have virtual machines running on a Hyper-V host configured with Switch Embedded Teaming (SET). However, the VMs are not receiving VLAN-tagged traffic as expected, even though the network configuration appears to be in place.

Could you please advise which SET and virtual switch port profile VLAN settings should be verified to ensure tagged VLAN traffic is handled correctly? We would also appreciate any recommended configuration checks or best practices for validating the VLAN configuration in this scenario.

Windows for business | Windows 365 Enterprise
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Nam Bui (WICLOUD CORPORATION) 1,195 Reputation points Microsoft External Staff Moderator
    2026-07-29T03:55:42.8933333+00:00

    Hi Foil Benny,  

    Thanks for reaching out.

    When using Switch Embedded Teaming (SET), VLAN tagging is handled at the virtual switch port (vPort) level, not on the SET team itself. Therefore, I would recommend verifying the following areas:

    • Physical switch configuration
      • Ensure all switch ports connected to the SET member NICs are configured as 802.1Q trunk ports.
      • Verify that the required VLANs are included in the allowed VLAN list on every uplink port.
    • VM network adapter VLAN configuration
      • If the VM should belong to a single VLAN, verify that the adapter is configured in Access mode with the correct VLAN ID.
      • If the guest OS is expected to receive and process multiple VLAN tags, verify that the adapter is configured in Trunk mode with the appropriate allowed VLAN list.
    • Physical NIC VLAN filters
      • Check the advanced properties of the physical adapters used by SET and ensure no vendor-specific VLAN ID is configured.
      • VLAN filtering on the physical NIC can prevent VLAN-tagged traffic from reaching the VM. VLAN management should be performed by the Hyper-V vSwitch/vPort instead.
    • SET team health
    • Confirm all team members are up and participating in the SET switch: 
        Get-VMSwitchTeam  
  Get-VMSwitch

    Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.  

    Best regards,

    Titus Bui

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.