Use the HCN API at the application-to-host networking boundary

Source facts

Microsoft exposes Host Compute Network as a Win32 API for managing virtual networks, endpoints, and related policies on a Windows host. The API creates, changes, deletes, and enumerates networks, endpoints, namespaces, and policies. Operations use object handles that are implemented internally as RPC context handles. Microsoft identifies developers as the API’s audience; end users do not interact with it directly. Microsoft documentation.

Applicability

Identify the application workflow, Windows platform, networking objects, and schema version the integration will use. Distinguish this host-platform interface from an operator’s tenant-network configuration procedure.

DSE recommendation

Document which application component owns each HCN object and which operations it may perform. Review object lifetimes, error handling, and cleanup with the developers responsible for the host integration. Keep a small representative configuration document and expected object inventory for the implementation review.

Verification

In an isolated development environment, exercise the intended create, inspect, update, and cleanup sequence. Compare the resulting objects and connectivity with the application’s expected state. Record failed operations and remaining objects explicitly, and verify that cleanup affects only the objects owned by the test workflow.

Official references

Microsoft Learn: Host Compute Network (HCN) service API for VMs and containers. Source reviewed September 8, 2026.