Allocate one coherent address plan for a Hyper-V NAT host

Source facts

Microsoft documents a limit of one NAT network per host in this Hyper-V setup. A VM connects to the NAT network through the internal virtual switch created by the procedure. When VMs and containers share one NAT, the internal prefix must cover their assigned ranges, and the configuration must avoid reusing addresses. Microsoft Learn.

Applicability

List the VMs, containers, and applications already managing addresses on the host. Inspect existing NAT and switch configuration before adding another network. Review the documented WinNAT limits alongside the intended topology rather than choosing an isolated range for each tool.

DSE recommendation

Reserve a host-level address plan that shows the overall internal prefix and the ranges assigned by each service. Name the owner of every allocation and the procedure for adding another VM or container. Preserve current switch and NAT settings before the pilot. Require an address-collision check before an application is allowed to introduce its own range.

Verification

Verify that each test endpoint uses the intended switch and a unique address inside the approved range. Exercise the required outbound connection from both a VM and a container when both are in scope. Record the effective NAT configuration and any unexpected address assignment before accepting the shared-host design.

Official references

Microsoft Learn: Set up a NAT network. Source reviewed September 8, 2026.