VPN Gateway for hybrid connectivity in Azure - Step-by-Step Execution

Process Flow - VPN Gateway for hybrid connectivity

Start: On-Premises Network

↓

Create VPN Gateway in Azure

↓

Configure VPN Connection

↓

Establish Secure Tunnel

↓

Data Flows Securely Between Networks

↓

End

This flow shows how a VPN Gateway connects an on-premises network to Azure securely, enabling hybrid connectivity.

Execution Sample

Azure

az network vnet-gateway create --resource-group MyRG --name MyVPNGateway --public-ip-address MyPublicIP --vnet MyVNet --gateway-type Vpn --vpn-type RouteBased --sku VpnGw1
az network vpn-connection create --resource-group MyRG --name MyConnection --vnet-gateway1 MyVPNGateway --local-gateway2 MyLocalGateway --shared-key abc123

This code creates an Azure VPN Gateway and then sets up a VPN connection to an on-premises local gateway using a shared key.

Process Table

Step	Action	Resource Created/Configured	Status	Result
1	Create VPN Gateway	VPN Gateway 'MyVPNGateway'	In Progress	Provisioning started
2	VPN Gateway Provisioned	VPN Gateway 'MyVPNGateway'	Succeeded	Gateway ready for connections
3	Create VPN Connection	VPN Connection 'MyConnection'	In Progress	Connection setup started
4	VPN Connection Established	VPN Connection 'MyConnection'	Succeeded	Secure tunnel established
5	Data Transfer	VPN Tunnel	Active	Hybrid connectivity enabled
6	Monitor Connection	VPN Connection 'MyConnection'	Active	Connection healthy

💡 VPN Gateway and VPN Connection are active, enabling secure hybrid network connectivity.

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
VPN Gateway Status	Not created	Succeeded	Succeeded	Succeeded
VPN Connection Status	Not created	Not created	Succeeded	Active
Secure Tunnel	Not established	Not established	Established	Active

Key Moments - 3 Insights

Why does the VPN Gateway take time to be ready after creation?

Because provisioning the VPN Gateway involves allocating resources and configuring network settings, it takes time before the status changes to 'Succeeded' as shown in execution_table step 2.

What does the shared key do in the VPN connection setup?

The shared key is a secret used to authenticate and secure the VPN tunnel between Azure and the on-premises gateway, ensuring only trusted networks connect, as seen in step 4 where the connection is established.

Why is monitoring the VPN connection important after setup?

Monitoring ensures the VPN tunnel stays active and healthy for continuous hybrid connectivity, as indicated in step 6 where the connection status is 'Active'.

Visual Quiz - 3 Questions

Look at the execution_table, what is the VPN Gateway status after step 2?

A In Progress

B Failed

C Succeeded

D Not created

💡 Hint

Check the 'Resource Created/Configured' and 'Status' columns at step 2.

At which step does the secure tunnel get established?

A Step 4

B Step 5

C Step 3

D Step 6

💡 Hint

Look for 'VPN Connection Established' and 'Secure tunnel established' in the 'Result' column.

If the shared key is incorrect, which step would likely fail?

A Step 2

B Step 4

C Step 1

D Step 6

💡 Hint

The shared key is used during VPN connection establishment, see step 4.

Concept Snapshot

VPN Gateway connects Azure VNet to on-premises network securely.
Create VPN Gateway resource, then configure VPN Connection with shared key.
Provisioning takes time; connection establishes secure tunnel.
Monitor connection health for reliable hybrid connectivity.

Full Transcript

This visual execution traces setting up an Azure VPN Gateway for hybrid connectivity. First, the VPN Gateway resource is created and provisioned. Then, a VPN Connection is configured using a shared key to link the Azure gateway with the on-premises local gateway. Once the connection is established, a secure tunnel enables data flow between networks. Monitoring ensures the connection remains active and healthy. Key moments include understanding provisioning delays, the role of the shared key, and the importance of monitoring.