Plan the client address pool for Azure Network Adapter

Source facts

Azure Network Adapter uses a Point-to-Site VPN connection to connect a server with an Azure virtual network. Microsoft describes this option for a small number of servers and states that it needs neither an on-premises VPN device nor a public-facing client address. Its private client address pool must not overlap the connecting on-premises location or destination virtual network. Microsoft Learn.

Applicability

Confirm the active Azure subscription, existing virtual network, server internet access, and Windows Admin Center integration prerequisites. Scope this design to the servers needing the connection, not an assumed site-wide transit service. Review gateway resources and associated charges before creation.

DSE recommendation

Have the network owner compare the proposed client pool against both address plans. Reserve the accepted range and identify the target subscription, network, and gateway in the change record. Agree which server-to-Azure application flow will demonstrate success. Keep connection removal and any newly created Azure resource cleanup under separate, explicit ownership.

Verification

After an approved setup, inspect the address assigned to the server connection and verify it belongs to the reserved pool. Test the named application flow and confirm the intended destination network. Review unexpected routes or overlapping addresses before adding another server to the connection plan.

Official references

Microsoft Learn: Connect server to Azure Virtual Network – Azure Network Adapter. Source reviewed September 8, 2026.