Skip to main content
Version: 1.0.0

Task 08: Arc Gateway

Runbook Azure

DOCUMENT CATEGORY: Runbook
SCOPE: Arc Gateway deployment
PURPOSE: Create Arc Gateway for hybrid server connectivity
MASTER REFERENCE: Microsoft Learn - Arc Gateway

Status: Active

Overview

This task deploys an Azure Arc Gateway resource. The Arc Gateway provides a centralized network endpoint that Arc-enabled servers use to communicate with Azure services, reducing the number of required firewall rules for on-premises infrastructure.

Task Classification

Execution Target: Azure-Only (control-plane API operation) Tab Profile: 3 tabs — Azure Portal · Azure CLI / PowerShell · Standalone Script

Azure API Resource

The Arc Gateway uses the Microsoft.HybridCompute/gateways resource type. As of this writing, it requires the AzAPI provider in Terraform (not yet in azurerm).

Terraform Reference

Module: azurelocal-toolkit File: arcgw.tf Mode: Cluster

Components Created

ResourceName PatternPurpose
Arc Gatewayarcgw-{instance}{env}{location}-{env}-{region}-01Centralized Arc connectivity

Arc Gateway Configuration

SettingValueSource
NamePer naming conventioncluster.deployment.arc_gateway.name
Resource GroupCluster RGcluster.deployment.arc_gateway.resource_group
Gateway TypePublicOnly valid value currently
Allowed FeaturesAll (*)Default

Prerequisites

  • Microsoft.HybridCompute resource provider registered
  • Resource group for Arc Gateway exists
  • Contributor role on target resource group

Variables from variables.yml

VariableConfig PathExample (IIC)
Subscription IDazure.subscriptions.<name>.id(per environment)
Resource Groupcluster.deployment.arc_gateway.resource_grouprg-c01-azl-eus-01
Arc Gateway Namecluster.deployment.arc_gateway.namearcgw-c01azleus-azl-eus-01

Single Subscription Model

Landing Zone Placement

FieldValueConfig Path
SubscriptionCustomer subscriptionazure.subscriptions.<name>.id
Resource Grouprg-{cluster}-{env}-{region}-01cluster.deployment.arc_gateway.resource_group
Arc Gateway NamePer configcluster.deployment.arc_gateway.name

Execution Options

Azure Portal

When to use: Learning Azure Local, single deployment, prefer visual interface

Procedure

  1. Register Resource Provider (if not already):
  • Subscription → Resource providers → Search Microsoft.HybridComputeRegister
  1. Create Arc Gateway:
  • Search for Arc Gateways (or Azure ArcArc Gateways)
  • Click + Create | Field | Value | Source | |-------|-------|--------| | Name | Per config | cluster.deployment.arc_gateway.name | | Subscription | Target subscription | azure.subscriptions.<name>.id | | Resource Group | Cluster RG | cluster.deployment.arc_gateway.resource_group | | Region | Your region | azure.region | | Gateway Type | Public | Only option |
  1. Review + create: Verify → Click Create → Record the Gateway Endpoint URL

  2. Note the Gateway ID: Copy the full resource ID — it will be needed during Azure Local cluster deployment:

/subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.HybridCompute/gateways/{name}

Validation

  • Arc Gateway provisioning state: Succeeded
  • Gateway endpoint URL recorded
  • Resource ID saved in variables.yml at cluster.deployment.arc_gateway.id

Validation

  • Arc Gateway provisioning state: Succeeded
  • Gateway endpoint URL available
  • Resource ID recorded for cluster deployment

CAF/WAF Landing Zone Model

In the CAF/WAF model, the Arc Gateway is typically deployed in the Management or Identity subscription, depending on governance structure.

Landing Zone Placement

FieldValueConfig Path
SubscriptionManagement subscriptionazure.subscriptions.management.id
Resource GroupPer configcluster.deployment.arc_gateway.resource_group
Arc Gateway NamePer configcluster.deployment.arc_gateway.name

Execution Options

Azure Portal

Follow the same procedure as Single Subscription → Azure Portal, targeting the Management subscription.

Validation

  • Arc Gateway in Management subscription
  • Gateway endpoint URL accessible from on-premises network

Validation

  • Arc Gateway in correct subscription
  • Endpoint reachable for cluster registration

Troubleshooting

IssueRoot CauseRemediation
Resource provider not registeredMicrosoft.HybridCompute not enabledRegister via Subscription → Resource providers
403 Forbidden on REST APIInsufficient permissionsNeed Contributor on resource group
Gateway endpoint not availableDeployment still propagatingWait 5 minutes and query again
Arc agent cannot reach gatewayFirewall blocking gateway endpointAllow *.gw.arc.azure.net on port 443


Alternatives

The procedures in this task use the scripted methods shown in the tabs above. Additional deployment methods including Azure CLI and Bash scripts are available in the azurelocal-toolkit repository under scripts/deploy/.

MethodDescription
Azure CLIPowerShell-based Azure CLI scripts for Azure resource operations
BashLinux/macOS compatible shell scripts for pipeline environments
PreviousUpNext
Task 07: NAT GatewayManual Deployment IndexTask 09: Log Analytics Workspace

Version Control

  • Created: 2025-09-15 by Hybrid Cloud Solutions
  • Last Updated: 2026-03-03 by Hybrid Cloud Solutions
  • Version: 4.0.0
  • Tags: azure-local, arc-gateway, hybrid, connectivity
  • Keywords: Arc Gateway, Azure Arc, hybrid compute, gateway endpoint, Arc-enabled servers
  • Author: Hybrid Cloud Solutions

Version Control

VersionDateAuthorChanges
1.0.02025-03-25Azure Local CloudInitial release