Give each SDN appliance adapter an explicit management or traffic role

Source facts

Microsoft describes network appliances used for user-defined routing and port mirroring in tenant virtual networks. User-defined routing can place an appliance in the routing path between virtual subnets. For appliances with multiple adapters, Microsoft requires each interface to be created in Network Controller and the corresponding interface IDs assigned on the hosts. The source distinguishes a management adapter from adapters processing traffic. Microsoft documentation.

Applicability

Identify the appliance’s documented adapter requirements, management network, data subnets, and forwarding purpose. Review the supported appliance deployment and the actual SDN resource identities before adapting the example.

DSE recommendation

Prepare an interface table showing every adapter, controller object, host binding, subnet, and intended role. Have the appliance and SDN owners review the table together. Explicitly identify the management path that should remain available during a forwarding or inspection test.

Verification

Verify each binding and test management separately from the intended data path. Exercise allowed and excluded routes or mirrored traffic according to the approved design. Record the actual path observed and investigate an unbound adapter or unexpected bypass before accepting the appliance deployment.

Official references

Microsoft Learn: Use network virtual appliances on a virtual network. Source reviewed September 8, 2026.