Azure Local - Azure Arc Gateway - Series

• Intro
• Articles in the series
• Scope and release status

Intro

Azure Arc Gateway can make Azure Local outbound connectivity much easier to manage. But enabling a gateway is only part of the work. We also need to understand the traffic that stays outside the gateway, prepare the network, and verify infrastructure and workloads separately.

In this series I will walk through that process, including the Azure Local 2610 preview for enabling Arc Gateway after deployment. I will also explain how the public path differs from the Azure Local private path architecture.

Articles in the series

I will publish the articles one at a time and add the links here as they become available.

• Part 1 - What is Azure Arc Gateway, and why use it?
• Part 2 - Prepare for Arc Gateway before Azure Local deployment (Coming later)
• Part 3a - Enable Arc Gateway after deployment (2610 preview) (Coming later)
• Part 3b - Verify post-deployment Arc Gateway enablement (Coming later)
• Part 4 - Harden outbound firewall rules around the local Arc proxy (Coming later)
• Part 5 - Enable Arc Gateway for existing and new virtual machines (Coming later)
• Part 6 - Handle Kubernetes connectivity with Arc Gateway (Coming later)

Scope and release status

The guidance in this series is based on the Microsoft documentation available on 31 October 2026. Arc Gateway for Azure Local infrastructure and Azure Local VMs is generally available. Post-deployment enablement on existing hyperconverged Azure Local instances requires solution version 2610 or later and is in preview. Arc Gateway for AKS on Azure Local is also in preview.

As always, check the current Azure Local Arc Gateway overview before making changes. Endpoint coverage and preview limitations can change between releases.