3 h 15 (S5.1 : 60 min · S5.2 : 105 min · S5.3 : 30 min)
module 4 (hub-spoke, firewall, UDR), IPsec and BGP basics
hub vnet-stNN-hub and gateway vpngw-stNN-hub ready, spokes peered and filtered by afw-stNN-hub
60 min
Peering = Local link (same region) | Global link (different regions)| Criterion | Local peering | Global peering |
|---|---|---|
| Regions | Same | Different |
| Latency | Within the region | Depends on the distance between regions |
| Billing | GB in + GB out | GB in + GB out, higher rate |
| Arvéo | Hub ↔ spokes (M4) | Hub ↔ DR spoke in West Europe (M5) |
Link = VNet access + Forwarded traffic + Gateway transit + Remote gateway| Property | Role | Hub link | Spoke link |
|---|---|---|---|
allowVirtualNetworkAccess |
Direct communication | Yes | Yes |
allowForwardedTraffic |
Accept relayed traffic (firewall) | Yes | Yes |
allowGatewayTransit |
Lend its gateway | Yes (M5) | No |
useRemoteGateways |
Use the remote gateway | No | Yes (M5) |
useRemoteGateways rejected without transit allowed opposite, or if the spoke has a gateway
Transit = Hub link (allowGatewayTransit) + Spoke link (useRemoteGateways)flowchart LR LYON[Lyon site<br/>10.200.7.0/24] -->|IPsec| GW[vpngw-st07-hub] GW --> APP[App spoke<br/>10.7.4.0/22] GW --> DATA[Data spoke<br/>10.7.8.0/22] GW --> PRA[DR spoke<br/>West Europe]
useRemoteGateways: no gateway of its own allowedaz network vnet peering update -g rg-st07-hub --vnet-name vnet-st07-hub \
-n peer-hub-to-spoke-app --set allowGatewayTransit=true -o none
az network vnet peering update -g rg-st07-spoke --vnet-name vnet-st07-spoke-app \
-n peer-spoke-app-to-hub --set useRemoteGateways=true -o none
az network vnet peering show -g rg-st07-spoke --vnet-name vnet-st07-spoke-app \
-n peer-spoke-app-to-hub \
--query "{State:peeringState, Remote:useRemoteGateways}" -o tableExpected output:
State Remote
--------- --------
Connected Truegateway in Updating = peering update rejected (wait for Succeeded)
Spoke A → Hub → Spoke B = Appliance + UDR | Gateway + UDR | Virtual WAN| Solution | Principle | Arvéo |
|---|---|---|
| Hub firewall + UDR | The appliance relays between spokes | Chosen in M4 (afw-st07-hub) |
| VPN gateway + UDR | The gateway acts as a router | Rejected (throughput, cost) |
| Spoke ↔ spoke peering | Full mesh | Rejected (bypasses the firewall) |
| Virtual WAN Standard | Transit managed by Microsoft | Alternative studied in S5.3 |
New range → Remote link "not in sync" → az network vnet peering syncaz network vnet update -g rg-st07-spoke -n vnet-st07-spoke-pra \
--address-prefixes 10.7.12.0/23 10.7.14.0/23 -o none
az network vnet peering list -g rg-st07-hub --vnet-name vnet-st07-hub \
--query "[].{Name:name, Sync:peeringSyncLevel}" -o table
az network vnet peering sync -g rg-st07-hub --vnet-name vnet-st07-hub \
-n peer-hub-to-spoke-pra -o noneExpected output (before sync, state label [TO VERIFY]):
Name Sync
---------------------- --------------
peer-hub-to-spoke-app FullyInSync
peer-hub-to-spoke-data FullyInSync
peer-hub-to-spoke-pra LocalNotInSync| Criterion | Peering | VNet-to-VNet VPN |
|---|---|---|
| Path | Microsoft backbone, private | IPsec tunnel between gateways |
| Throughput | That of the VMs | Capped by the gateway SKU |
| Latency | Minimal | Encryption overhead |
| Cost | Transferred volume | Gateways (hourly) + outbound volume |
| Setup | Minutes | 30 to 45 min per gateway |
| Encryption | None added | End-to-end IPsec |
peering by default; VNet-to-VNet when compliance requires IPsec between VNets
105 min
GatewaySubnet, at least one public IPVPN gateway = Vpn type + Route-based + SKU + Public IP[TO VERIFY] eligible SKUsvpngw-st07-hub)Before (Lyon): buy two VPN routers + maintenance → several weeks
After (Azure): az network vnet-gateway create → managed service (45 min)
[TO VERIFY] by generation)SKU = Generation + Aggregate throughput + Number of tunnels + Zone redundancy (AZ)| SKU | Aggregate throughput | Max S2S tunnels | BGP |
|---|---|---|---|
| Basic | 100 Mbps | 10 | No |
| VpnGw1AZ | 650 Mbps | 30 | Yes |
| VpnGw2AZ | 1 Gbps | 30 | Yes |
| VpnGw3AZ | 1.25 Gbps | 30 | Yes |
| VpnGw4AZ / VpnGw5AZ | 5 / 10 Gbps | 100 | Yes |
[TO VERIFY] timelineS2S = VPN gateway + Local network gateway + Connection (shared key)flowchart LR VM[vm-st07-lyon-fs<br/>10.200.7.10] --- GWL[vpngw-lyon] GWL <-->|IPsec IKEv2| GWH[vpngw-st07-hub] GWH --- AZ[Hub + spokes<br/>10.7.0.0/20]
lng-st07-lyon (trainee): IP of vpngw-lyon, range 10.200.7.0/24lng-lyon-st07 (trainer): IP of vpngw-st07-hub, range 10.7.0.0/20IPsec connection: identical shared key on both sidesVariables: $PSK = shared key provided by the trainer (Lyon network team)
LYON_IP=$(az network public-ip show -g rg-formation-lyon -n pip-lyon-vpngw \
--query ipAddress -o tsv)
az network local-gateway create -g rg-st07-hub -n lng-st07-lyon -l francecentral \
--gateway-ip-address "$LYON_IP" --local-address-prefixes 10.200.7.0/24 \
--tags Projet=Arveo Environnement=Formation Proprietaire=st07 -o none
az network vpn-connection create -g rg-st07-hub -n cn-st07-hub-to-lyon \
--vnet-gateway1 vpngw-st07-hub --local-gateway2 lng-st07-lyon \
--shared-key "$PSK" \
--tags Projet=Arveo Environnement=Formation Proprietaire=st07 -o noneExpected result: no output, created in 1 to 2 min
in production, a long random key stored in Azure Key Vault
Connected + Inbound and outbound bytes > 0 = Tunnel operationalaz network vpn-connection show -g rg-st07-hub -n cn-st07-hub-to-lyon \
--query "[connectionStatus, ingressBytesTransferred, egressBytesTransferred]" -o tsvExpected output (counters vary):
Connected 2104 3388TunnelDiagnosticLog and IKEDiagnosticLog logs to Log Analytics (M10)Connecting or NotConnected = different key, wrong range or missing Lyon side
Symmetry = GatewaySubnet UDR (to the spokes) + Spoke UDR (0.0.0.0/0)flowchart LR LYON[vm-st07-lyon-fs<br/>10.200.7.10] -->|IPsec| GW[vpngw-st07-hub] GW -->|rt-st07-gateway| FW[afw-st07-hub<br/>10.7.0.68] FW --> WEB[vm-st07-test-web<br/>10.7.4.10] WEB -->|0.0.0.0/0| FW
rt-st07-gateway: gateway → peering → spoke directly (firewall bypassed)0.0.0.0/0 → firewall, no known state → packet DROPPED10.200.7.0/24 learned from the gateway (propagation on in its subnet)rt-st07-gateway = 10.7.4.0/22 → firewall + 10.7.8.0/22 → firewallGatewaySubnet0.0.0.0/0 route not supported on GatewaySubnetVirtualAppliance hop = firewall private IPaz network route-table create -g rg-st07-hub -n rt-st07-gateway -l francecentral \
--disable-bgp-route-propagation false \
--tags Projet=Arveo Environnement=Formation Proprietaire=st07 -o none
az network route-table route create -g rg-st07-hub --route-table-name rt-st07-gateway \
-n spoke-data-via-fw --address-prefix 10.7.8.0/22 \
--next-hop-type VirtualAppliance --next-hop-ip-address 10.7.0.68 -o nonepropagation disabled on GatewaySubnet = VPN connectivity broken
Connection = IPsec (site-to-site) | Vnet2Vnet | VPNClient (point-to-site) | ExpressRoute| Feature | Principle | Arvéo |
|---|---|---|
| BGP | Routes exchanged dynamically (ASN, APIPA) | No: static ranges (LNG) |
| IPsec/IKE policy | Enforced algorithms (AES256, SHA256, DH) | Default policy |
| Active-active | Two tunnels, fast failover | No (cost) |
| Point-to-site | Mobile users: IKEv2, OpenVPN, Entra ID | Sales staff (overview) |
| VNet-to-VNet | Tunnel between two Azure gateways | No (peering) |
30 min
ExpressRoute = Circuit (provider) + Azure private peering + ExpressRoute gatewayflowchart LR DC[Lyon datacenter] -->|Provider link| EDGE[Peering location<br/>Paris] EDGE -->|Circuit, 2 links| MSEE[Microsoft routers] MSEE --> GW[ExpressRoute gateway<br/>in the hub]
| Item | Choice | Use |
|---|---|---|
| Peering | Azure private / Microsoft | VNets / Microsoft 365 and public PaaS |
| Circuit SKU | Local / Standard / Premium | Nearby region / geopolitical area / world |
| Billing | Metered / unlimited data | Based on outbound volume |
| Global Reach | Circuits linked together | Lyon ↔ other site via Microsoft |
| FastPath | Bypasses the ER gateway | Very high throughput to VMs |
GatewaySubnet (/27 minimum)Virtual WAN = Managed virtual hubs + Connections (VNets, VPN, ER, P2S) + Automatic routingflowchart LR AG[Branches<br/>S2S VPN] --> VH1[Virtual hub<br/>France Central] NOM[Mobile users<br/>P2S] --> VH1 VH1 <--> VH2[Virtual hub<br/>West Europe] VH1 --> VN[Application<br/>VNets] ER[Lyon<br/>ExpressRoute] --> VH2
| Feature | Basic | Standard |
|---|---|---|
| Site-to-site VPN | Yes | Yes |
| Point-to-site, ExpressRoute | No | Yes |
| VNet ↔ VNet transit through the hub | No | Yes |
| Hub to hub (inter-region) | No | Yes |
| Azure Firewall (secured hub) | No | Yes |
[TO VERIFY] price listChoice = Requirements (throughput, SLA, confidentiality) + Number of sites + Cost + Lead time
flowchart TD
Q1{Private link<br/>with SLA required?} -->|Yes| ER[ExpressRoute<br/>+ backup VPN]
Q1 -->|No| Q2{Many sites<br/>or global transit?}
Q2 -->|Yes| VW[Virtual WAN Standard]
Q2 -->|No| VPN[S2S VPN<br/>hub-spoke]
name the solution, give two arguments and one risk; group debrief
allowGatewayTransit on the hub first, useRemoteGateways on the spoke nextConnected only when both sides exist with the same keyGatewaySubnet: UDRs to the spokes via the firewall, propagation on, never 0.0.0.0/0allowForwardedTrafficuseRemoteGatewaysallowGatewayTransitallowVirtualNetworkAccessuseRemoteGateways is rejected on a spoke link. Most likely cause?rg-st07-hub?cn-st07-hub-to-lyonlng-st07-lyonvpngw-st07-hubpeer-hub-to-spoke-applng-st07-lyon declare?ConnectedNotConnected or Connecting: tunnel not establishedConnected in degraded modeGatewaySubnet?GatewaySubnet?10.7.8.0/22 → VirtualAppliance0.0.0.0/0 → VirtualAppliance10.7.4.0/22 → VirtualAppliance