3 h 15 (S4.1 : 45 min · S4.2 : 45 min · S4.3 : 60 min · S4.4 : 45 min)
module 3, TCP/IP basics (CIDR, routing, DNS)
rg-stNN-shared foundation in place, rg-stNN-hub and rg-stNN-spoke empty
45 min
VNet = Address space + Subnets + Region + SubscriptionBefore (on-premises): VLAN + router + switch → purchase and cabling (weeks)
After (Azure): az network vnet create → network available (seconds)
VNet range = Sum of subnets + Growth reserve10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16.4)range overlapping the Lyon site = peering or VPN impossible later
Address = 10.<NN>.x.x (trainee 07 → 10.7.0.0/22)| Network | Range | Subnets |
|---|---|---|
Hub vnet-st07-hub |
10.7.0.0/22 |
Gateway, firewall (×2), Bastion, snet-shared |
App spoke vnet-st07-spoke-app |
10.7.4.0/22 |
snet-web 10.7.4.0/24, snet-app 10.7.5.0/24 |
Data spoke vnet-st07-spoke-data |
10.7.8.0/22 |
snet-data 10.7.8.0/24, snet-pe 10.7.9.0/24 |
| Simulated Lyon (shared) | 10.200.0.0/16 |
Trainee subnet 10.200.7.0/24 (M5) |
10.07.0.0 rejected (leading zero); in Bash OCT=$((10#$NN)) gives 7
Mandatory name + Minimum size = Deployment accepted| Subnet | Service | Size | Arvéo (st07) |
|---|---|---|---|
GatewaySubnet |
VPN or ExpressRoute gateway | /27 recommended | 10.7.0.0/27 |
AzureFirewallSubnet |
Azure Firewall | /26 | 10.7.0.64/26 |
AzureFirewallManagementSubnet |
Azure Firewall Basic management | /26 | 10.7.0.128/26 |
AzureBastionSubnet |
Azure Bastion (M7) | /26 minimum | 10.7.1.0/26 |
NSG not supported on GatewaySubnet; no VM in these subnets
Hub-spoke = Hub (connectivity + security) + Spokes (isolated applications)flowchart LR LYON[Lyon site 10.200.0.0/16] -->|VPN M5| HUB[Hub 10.7.0.0/22<br/>Gateway · Firewall · Bastion] NET[Internet] --> HUB HUB --- APP[App spoke 10.7.4.0/22] HUB --- DATA[Data spoke 10.7.8.0/22]
Example for trainee 07:
az network vnet create -g rg-st07-spoke -n vnet-st07-spoke-app \
--address-prefixes 10.7.4.0/22 \
--subnet-name snet-web --subnet-prefixes 10.7.4.0/24 \
--tags Projet=Arveo Environnement=Formation Proprietaire=st07 -o none
az network vnet subnet create -g rg-st07-spoke --vnet-name vnet-st07-spoke-app \
-n snet-app --address-prefixes 10.7.5.0/24 -o none
az network vnet subnet list -g rg-st07-spoke --vnet-name vnet-st07-spoke-app \
--query "[].{Name:name, Range:addressPrefix}" -o tableExpected output:
Name Range
-------- -----------
snet-web 10.7.4.0/24
snet-app 10.7.5.0/24Public IP = Standard SKU + Static + Zones (1, 2, 3)| Type | Assignment | Arvéo use |
|---|---|---|
| Dynamic private | First free address of the subnet | Application VMs (M7) |
| Static private | Set on the NIC, outside the 5 reserved | Test VMs on .10 |
| Standard public | Static, inbound closed by default | Firewall, VPN gateway |
[TO VERIFY] timeline: explicit egress (firewall, NAT Gateway)45 min
NSG rule = Priority + Source + Destination + Port + Protocol + ActionNSG at subnet level; NIC level only for a justified exception
Empty NSG = Intra-VNet allowed + Outbound Internet allowed + Rest denied| Direction | Rule (priority) | Source → Destination | Action |
|---|---|---|---|
| Inbound | AllowVnetInBound (65000) | VirtualNetwork → VirtualNetwork | Allow |
| Inbound | AllowAzureLoadBalancerInBound (65001) | AzureLoadBalancer → * | Allow |
| Inbound | DenyAllInBound (65500) | * → * | Deny |
| Outbound | AllowVnetOutBound (65000) | VirtualNetwork → VirtualNetwork | Allow |
| Outbound | AllowInternetOutBound (65001) | * → Internet | Allow |
| Outbound | DenyAllOutBound (65500) | * → * | Deny |
Inbound: subnet NSG → NIC NSG (outbound: reverse order)flowchart LR SRC[Source] --> NSGS[Subnet NSG] --> NSGN[NIC NSG] --> VM[VM]
VirtualNetwork tag = VNet + peered VNets + VPN sites + UDR prefixeswith a 0.0.0.0/0 UDR, VirtualNetwork covers EVERYTHING; plan an explicit deny
ASG = Logical group of network interfaces (application role)Internet, Storage.FranceCentral)asg-st07-data), used in a rule instead of an IPBefore: rule 10.7.8.10, 10.7.8.11, 10.7.8.12 → updated for every new VM
After: rule asg-st07-data → new VM placed in the ASG, rule unchanged
NICs of an ASG = Same VNet (the first NIC added sets the VNet)10.7.4.0/24), destination as an ASGsource asg-st07-web (app spoke) to asg-st07-data (data spoke) = rule rejected
az network nsg create -g rg-st07-spoke -n nsg-st07-web \
--tags Projet=Arveo Environnement=Formation Proprietaire=st07 -o none
az network nsg rule create -g rg-st07-spoke --nsg-name nsg-st07-web \
-n Allow-HTTP-HTTPS-Inbound --priority 100 --direction Inbound \
--access Allow --protocol Tcp --destination-port-ranges 80 443 -o none
az network vnet subnet update -g rg-st07-spoke --vnet-name vnet-st07-spoke-app \
-n snet-web --network-security-group nsg-st07-web -o none
az network nsg rule list -g rg-st07-spoke --nsg-name nsg-st07-web \
--query "[].{Name:name, Prio:priority, Ports:join(',', destinationPortRanges)}" -o tableExpected output:
Name Prio Ports
------------------------ ------ ------
Allow-HTTP-HTTPS-Inbound 100 80,443Check = Effective rules (NIC) + IP flow verify (Network Watcher)az network nic list-effective-nsg -g rg-st07-spoke -n nic-st07-test-web \
--query "value[0].effectiveSecurityRules[?direction=='Inbound'].name" -o tsv
az network watcher test-ip-flow -g rg-st07-spoke --vm vm-st07-test-web \
--direction Inbound --protocol TCP --local 10.7.4.10:80 --remote 10.7.5.20:50000Expected output (excerpts):
securityRules/Allow-HTTP-HTTPS-Inbound
defaultSecurityRules/AllowVnetInBound
{ "access": "Allow", "ruleName": "securityRules/Allow-HTTP-HTTPS-Inbound" }effective rules = running VM; IP flow verify = deciding rule named
60 min
Defense in depth = NSG (subnet) + Azure Firewall (hub)| Criterion | NSG | Azure Firewall |
|---|---|---|
| Layer | 3-4 (IP, port) | 3-7 (IP, port, FQDN, URL by SKU) |
| Scope | Subnet or NIC | All traffic routed to the hub |
| Logging | Flow logs | Detailed logs in Log Analytics |
| Cost | Free | Hourly + processed volume |
| Arvéo role | Micro-segmentation | Inter-spoke, Internet egress, publishing |
Azure Firewall = Managed service + Policy (Firewall Policy) + Public IPs| Feature | Basic | Standard | Premium |
|---|---|---|---|
| Maximum throughput | 250 Mbps | 30 Gbps | 100 Gbps |
| Network, application, DNAT rules | Yes | Yes | Yes |
| Threat intelligence | Alert | Alert and deny | Alert and deny |
| DNS proxy, FQDN in network rules | No | Yes | Yes |
| TLS inspection, IDPS | No | No | Yes |
Basic for training (cost); Standard in production, Premium if TLS inspection is required
Policy > Rule collection group > Rule collection > Ruleflow accepted by a network rule = application rules never evaluated for it
Effective routes = System routes + BGP routes (gateway) + UDR routes| Next hop | Destination | Arvéo example |
|---|---|---|
VnetLocal |
VNet address space | 10.7.4.0/22 |
VNetPeering |
Peered VNet | 10.7.0.0/22 (hub) |
VirtualNetworkGateway |
VPN or ExpressRoute site | 10.200.0.0/16 (M5) |
Internet |
Rest of the world | 0.0.0.0/0 |
VirtualAppliance |
Appliance IP (UDR) | 10.7.0.68 (firewall) |
None |
Traffic dropped | Range to block |
Choice = Most specific prefix → UDR > BGP > System10.7.4.20 from snet-web: 10.7.4.0/22 (VnetLocal) beats 0.0.0.0/0 (UDR)0.0.0.0/0 → VirtualAppliance (firewall private IP); intra-spoke unchangedGatewaySubnet completed in M5)Peering = Hub → spoke link + Spoke → hub link (two separate objects)Initiated after the first link, Connected after the second--allow-forwarded-traffic: accept traffic relayed by the hub firewallaz network vnet peering create -g rg-st07-hub --vnet-name vnet-st07-hub \
-n peer-hub-to-spoke-app --remote-vnet "$APP_ID" \
--allow-vnet-access --allow-forwarded-traffic --query peeringState -o tsvExpected output:
InitiatedVariables: $FW_IP = firewall private IP (deployment output)
az network route-table create -g rg-st07-spoke -n rt-st07-spoke-app \
--disable-bgp-route-propagation true \
--tags Projet=Arveo Environnement=Formation Proprietaire=st07 -o none
az network route-table route create -g rg-st07-spoke \
--route-table-name rt-st07-spoke-app -n default-via-fw \
--address-prefix 0.0.0.0/0 --next-hop-type VirtualAppliance \
--next-hop-ip-address "$FW_IP" -o none
az network vnet subnet update -g rg-st07-spoke --vnet-name vnet-st07-spoke-app \
-n snet-web --route-table rt-st07-spoke-app -o none
az network nic show-effective-route-table -g rg-st07-spoke -n nic-st07-test-web \
--query "value[?source=='User'].{Prefix:addressPrefix[0], Hop:nextHopType}" -o tableExpected output:
Prefix Hop
--------- ----------------
0.0.0.0/0 VirtualApplianceflowchart LR WEB[vm-st07-test-web<br/>10.7.4.10] -->|UDR 0.0.0.0/0| FW[afw-st07-hub<br/>10.7.0.68] FW -->|network rule TCP 1433| DATA[vm-st07-test-data<br/>10.7.8.10] FW -->|application rule| NET[Internet *.ubuntu.com]
rt-st07-spoke-app → firewall → peering → data spokert-st07-spoke-data → firewall (SYMMETRIC routing required)nsg-st07-data still applied: source seen as 10.7.4.10 (no SNAT for private traffic)pip-st07-fwUDR on one spoke only = return path bypasses the firewall, connection dropped
45 min
Azure DNS = Public zones + Private zones + 168.63.129.16 resolver| Service | Role | Arvéo example |
|---|---|---|
| Public DNS zone | Name resolved from the Internet | www.arveo-st07.fr |
| Private DNS zone | Name resolved in linked VNets | sql.arveo.internal |
168.63.129.16 resolver |
Default DNS of every VM | Resolution without setup |
| DNS Private Resolver | On-premises ↔ Azure DNS bridge | Lyon → arveo.internal (overview) |
168.63.129.16 = platform address, reachable from any VM, never routed by a UDR
Delegation = Azure zone (4 NS servers) + NS records at the registrarflowchart LR C[Client] --> R[ISP resolver] --> TLD[.fr servers] -->|NS| AZ[ns1-XX.azure-dns.com]
ns1-XX.azure-dns.com to ns4-XX.azure-dns.info)Private zone + Virtual network link = Names resolved in that VNetprivatelink.* zones: private endpoint resolution (M6)zone not linked to the VM's VNet = NXDOMAIN, even if the zone exists
flowchart LR ZONE[arveo.internal<br/>rg-st07-hub] --- HUB[vnet-st07-hub<br/>resolution] ZONE --- APP[app spoke<br/>auto-registration] ZONE --- DATA[data spoke<br/>auto-registration]
vm-st07-test-web.arveo.internalsql → 10.7.8.10 (stable service name)168.63.129.16 → zones linked to the VM's VNetsql.arveo.internal survives a server replacement; only the record changes
Variables: $APP_ID = ID of VNet vnet-st07-spoke-app
az network private-dns zone create -g rg-st07-hub -n arveo.internal \
--tags Projet=Arveo Environnement=Formation Proprietaire=st07 -o none
az network private-dns link vnet create -g rg-st07-hub -z arveo.internal \
-n link-spoke-app -v "$APP_ID" --registration-enabled true \
--tags Projet=Arveo Environnement=Formation Proprietaire=st07 -o none
az network private-dns record-set a add-record -g rg-st07-hub -z arveo.internal \
-n sql -a 10.7.8.10 -o none
az network private-dns record-set list -g rg-st07-hub -z arveo.internal \
--query "[].{Name:name, Auto:isAutoRegistered}" -o tableExpected output:
Name Auto
---------------- ------
@ False
sql False
vm-st07-test-web True168.63.129.16 is reachable from Azure onlyDNS Private Resolver = Inbound endpoint + Outbound endpointarveo.lan) forwarded to the Lyon DNS[TO VERIFY])Before: two DNS VMs in the hub → patching, backups, high availability to manage
After: managed service → forwarders declared, no VM to administer
GatewaySubnet, AzureFirewallSubnet)snet-firewallAzureFirewallSubnetFirewallSubnetGatewaySubnetsnet-web routes: 10.7.4.0/22 VnetLocal and 0.0.0.0/0 UDR. Next hop for 10.7.5.20?arveo.internal: resolution of sql.arveo.internal?168.63.129.16NXDOMAIN: zone not linked to this VNet