- Az firewall
- az firewall is linked to Az Vnet
- Vnet should spare subnet in place
- due to FW helps to communicate on private IP hence public IP is not assigned to VM
- supply private ip address of firewall here to route traffic via firewall
- attach subnet of VM to route table
- connect VM via NAT
- Hub Spoke model
- traffic flow will be via peering
- attach route table to GatewaySubnet
- Setting up Hub network
- acting as onprem machine with routing capability
- create VNet for Hub
- vn gateway
- az bastion
- add gatewaysubnet to hubVnet
- Create Virtual network gateway
- create a vnet for spoke and subnet
- create local network gateway
- assign IP of you on-prem vpn device public IP
- same for address space, should be taken from on-prem vpn subnet
- click on connection on VNgateway
- select above created local network gateway, supply shared key
- supply pre-shared key in the properties
- Create Route Table
- associate the hubnet / subnet and associate with Route Table
- Create another Route Table to route the traffice to company