DSE UpdatesDetection Systems & Engineering
DSESecurity.com
GuideInformationITNetworks & Infrastructure

Preserve the VM adapter identity before starting an SDN tenant workload

Which VM network-adapter identity must be established before an SDN-connected VM starts?

DSE Security Editorial TeamPublished · 1 min read · Reviewed
Governed cloud identity system with connected service and lifecycle nodes.
DSE visual intelligenceIdentity & cloudGuide · 1 min read
Executive summary

What you need to know

Which VM network-adapter identity must be established before an SDN-connected VM starts?

Potentially affected

Administrators attaching VMs to Microsoft SDN tenant networks or VLANs.

DSE recommendation

Prepare a binding record linking the VM adapter to its Network Controller interface and tenant network.

Source facts

Microsoft’s procedure attaches a tenant VM either to a virtualized tenant network or to a VLAN. The VM adapter requires a static MAC address for the VM’s lifetime. A MAC change prevents Network Controller from configuring the required adapter policy and stops network communication. For a VM needing connectivity at startup, the source instructs administrators to set the interface identifier on the adapter port before starting it. Microsoft documentation.

Applicability

Identify the VM, adapter, controller interface resource, MAC address, target subnet, and startup dependencies. Replace the source’s sample identifiers with the approved values for this tenant.

DSE recommendation

Prepare a binding record linking the VM adapter to its Network Controller interface and tenant network. Have the platform and network owners review those identities before first boot. Define how the binding will be maintained if the VM is moved or its adapter is recreated.

Verification

Inspect the identities before startup, then test the intended tenant communication from the guest. Compare the observed policy association and network path with the binding record. Treat a changed MAC or missing interface resource as an unresolved configuration issue before allowing the application to depend on that connection.

Official references

Microsoft Learn: Create a VM and connect to a tenant virtual network or VLAN. Source reviewed September 8, 2026.

Primary reference

Review the official source

Create a VM and connect to a tenant virtual network or VLAN · Verified September 8, 2026

Open official reference ↗
Keep learning
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE