Skip to main content

Task 04: Point-to-Site VPN Connection

Runbook Azure

DOCUMENT CATEGORY: Runbook
SCOPE: P2S VPN configuration
PURPOSE: Enable remote admin access via P2S VPN
MASTER REFERENCE: Microsoft Learn - P2S VPN

Status: Active

Overview​

This task configures Point-to-Site (P2S) VPN on the existing VPN Gateway (Task 02) to allow individual administrators to connect remotely to the Azure management network. P2S VPN is optional — it provides an alternative to Azure Bastion for remote management scenarios.

Task Classification

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

Optional Task

This task is optional. It is only required when remote administrative VPN access is needed in addition to or instead of Azure Bastion (Task 05).

Terraform Reference

Module: azurelocal-toolkit File: network.tf Mode: Management

Components Configured​

ResourceName PatternPurpose
P2S VPN ConfigurationOn existing VPN GatewayRemote admin VPN access
VPN Client Address PoolPer configIP pool for VPN clients

P2S Configuration​

SettingValueSource
AuthenticationCertificate or Entra IDlanding_zone.connectivity.vpn_gateway.point_to_site.authentication
Tunnel TypeOpenVPNlanding_zone.connectivity.vpn_gateway.point_to_site.protocols
Client Address PoolPer configlanding_zone.connectivity.vpn_gateway.point_to_site.address_pool
Root CertificateKey Vault referencelanding_zone.connectivity.vpn_gateway.point_to_site.root_certificate

Prerequisites​

  • Task 02: VPN Gateway completed — VPN Gateway provisioned
  • Root certificate generated and uploaded to Key Vault (if using certificate auth)
  • Entra ID application registered (if using Entra ID authentication)
  • Client address pool CIDR does not overlap with VNet or on-premises ranges

Values from infrastructure.yml​

The script reads these keys from infrastructure.yml (schema 5). Each key, with its type, default and example, is in the variables reference.

azure.tenant_id, azure.location
landing_zone.connectivity.vpn_gateway.name, .resource_group, .network the gateway
landing_zone.networks[].name, .subscription, .resource_group where the network, and so the gateway, is
landing_zone.subscriptions[].name, .id the subscription that holds the network
landing_zone.connectivity.vpn_gateway.point_to_site.address_pool, .authentication, .protocols, .root_certificate_name, .root_certificate

Single Subscription Model​

Landing Zone Placement​

FieldValueConfig Path
SubscriptionCustomer subscriptionlanding_zone.subscriptions[].id
Resource GroupSame as VPN Gatewaylanding_zone.connectivity.vpn_gateway.resource_group
VPN GatewayExisting gatewaylanding_zone.connectivity.vpn_gateway.name
Client PoolPer configlanding_zone.connectivity.vpn_gateway.point_to_site.address_pool

Execution Options​

Azure Portal​

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

Procedure​

  1. Navigate to VPN Gateway:
  • Search for Virtual network gateways → Select the gateway from Task 02
  1. Configure Point-to-Site:
  • Go to Point-to-site configuration → Configure now | Field | Value | Source | |-------|-------|--------| | Address pool | Client CIDR | landing_zone.connectivity.vpn_gateway.point_to_site.address_pool | | Tunnel type | OpenVPN (SSL) | landing_zone.connectivity.vpn_gateway.point_to_site.protocols | | Authentication type | Azure certificate or Entra ID | landing_zone.connectivity.vpn_gateway.point_to_site.authentication |
  1. Upload Root Certificate (if certificate auth): | Field | Value | Source | |-------|-------|--------| | Name | Root cert name | landing_zone.connectivity.vpn_gateway.point_to_site.root_certificate_name | | Public certificate data | Base64 cert data | From Key Vault |

  2. Configure Entra ID (if Entra ID auth): | Field | Value | Source | |-------|-------|--------| | Tenant | Entra tenant ID | azure.tenant_id | | Audience | Entra app ID | no key (the script or Azure decides it) | | Issuer | https://sts.windows.net/{tenant-id}/ | Derived from tenant |

  3. Save the configuration

  4. Download VPN Client: Click Download VPN client → Distribute to authorized admins

Validation​

  • P2S configuration saved on VPN Gateway
  • VPN client profile downloadable
  • Test client connects successfully
  • Client receives IP from configured pool

Validation​

  • P2S configuration present on VPN Gateway
  • VPN client downloads successfully
  • Client connects and receives IP from pool
  • Client can reach management subnet resources

CAF/WAF Landing Zone Model​

In the CAF/WAF model, the P2S configuration exists on the VPN Gateway in the Connectivity subscription.

Landing Zone Placement​

FieldValueConfig Path
SubscriptionConnectivity subscriptionlanding_zone.subscriptions[].id
Resource GroupConnectivity resource grouplanding_zone.connectivity.vpn_gateway.resource_group
VPN GatewayExisting gatewaylanding_zone.connectivity.vpn_gateway.name

Execution Options​

Azure Portal​

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

Validation​

  • P2S configured on gateway in Connectivity subscription
  • Client receives IP from address pool

Validation​

  • P2S VPN functional from Connectivity subscription
  • No routing conflicts with Hub VNet address space

Troubleshooting​

IssueRoot CauseRemediation
Client cannot connectRoot cert not trustedVerify root cert uploaded correctly
No IP assigned to clientAddress pool exhausted or misconfiguredExpand pool or verify CIDR
Address pool overlapsCIDR conflicts with VNet or on-premChoose non-overlapping CIDR
Entra ID auth failsApp registration misconfiguredVerify tenant ID, audience, and API permissions
OpenVPN not availableGateway SKU too lowUpgrade to VpnGw2AZ or higher


Alternatives​

The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.

PreviousUpNext
Task 03: S2S VPN ConnectionManual Deployment IndexTask 05: Azure Bastion

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, vpn, p2s, remote-access, networking
  • Keywords: point-to-site, P2S VPN, remote access, VPN client, certificate authentication, Entra ID
  • Author: Hybrid Cloud Solutions

Version Control​

VersionDateAuthorChanges
1.0.02025-03-25Azure Local CloudInitial release