The Azure Arc team is excited to announce that Azure Arc-enabled servers’ support for private endpoints is now generally available! With private endpoints, you can send traffic from the Azure Connected Machine Agent to Azure over a site-to-site VPN or Express Route circuit instead of the public internet or proxy server. This can help you reduce network exposure and improve security while still allowing you to use Azure Arc to secure, monitor and govern your servers running outside of Azure.
How does it work?
Private endpoints allow you to connect an Azure service to an Azure virtual network using private IP addresses. Servers and other resources in that virtual network can then communicate with the Azure service using the private IP address and instead of sending data over the internet.
Azure Arc uses a Private Link Scope resource to associate a private endpoint with the non-Azure servers that will use the private endpoint. You’ll also need to set up a site-to-site VPN or Express Route circuit to connect your Azure virtual network with the network where your non-Azure servers are connected.
Once configured, the Connected Machine agent on your Arc-enabled servers will send all metadata updates, extension operations, and guest configuration package downloads over the private endpoint. Network traffic between extensions you’ve installed and the Azure services that support them will also route through the internet unless you’ve configured private endpoints for each of those services. Additionally, the Connected Machine agent will still require access to Azure Active Directory and Azure Resource Manager over the internet.
Network architecture diagram of Azure Arc-enabled servers private endpoints