Update Network ATC intents when cluster adapters change

Source facts

Microsoft documents ongoing Network ATC administration through PowerShell after deployment. A newly added cluster node receives the same intent and must meet the documented requirements. When physical adapters change, Update-NetIntentAdapter updates the adapters assigned to the relevant intents. Network ATC also permits environment-specific management and storage VLAN values instead of its defaults. Microsoft documentation.

Applicability

Use this review for a cluster already managed by Network ATC. Identify the current intent, node set, adapter mapping, and selected VLANs before changing hardware or membership. Keep initial deployment readiness as a separate prerequisite review.

DSE recommendation

Maintain an intent-to-adapter worksheet and compare it with the physical change request. Have the network and server owners approve the intended mapping on every affected node. Include management access and workload connectivity in the test plan. Record the existing intent configuration and a supported recovery route before using the applicable management operation.

Verification

After the approved update, inspect intent state and adapter membership across the cluster. Test the management and workload paths that depend on the changed adapters. Check a newly added node against the existing nodes rather than reviewing it in isolation. Record inconsistent mappings, failed intents, or unexpected VLAN behavior before proceeding with another hardware change.

Official references

Microsoft Learn: Manage Network ATC. Source reviewed September 8, 2026.