Azure Virtual Networking and Gateway Setup

Study Notes

Connect two virtual networks (VNet2 and VNet3) by selecting "Use remote gateways" on the peering configuration for both networks.
Also, select "Allow gateway transit" on the peering configuration from Vnet1.

Choose the ExpressRoute gateway SKU Ultra Performance to support the FastPath feature.
Consider using VNet peering with FastPath enabled to send traffic directly to VMs in a peered virtual network.
Choose the optimal gateway SKU based on your network traffic demands and requirements (Ultra Performance or ErGw3AZ).

To connect Vnet2 and Vnet3, you should use "Allow forwarded traffic" on the peering from Vnet1 and select "Allow gateway transit" on the peerings from Vnet2 and Vnet3.

To prepare Vnet1, you must:
- Create an express route circuit
- Create an ExpressRoute gateway
- Connect the Vnet to the gateway

To implement a P2S VPN for users in the branch office, you need to:
- Create a VPN Gateway
- Configure point-to-site connections
- Configure client VPN configurations.

For an ExpressRoute connection from the Boston datacenter, you should recommend:
- Ultra Performance ExpressRoute Gateway SKU
- FastPath enabled, as it provides a faster data path between the on-premises network and the virtual network.
FastPath can bypass the gateway and send traffic directly to VMs within the virtual network.
To configure FastPath, the ExpressRoute gateway must be configured with Ultra Performance or ErGw3AZ SKU
VNet Peering can send traffic directly to any VM deployed in a peered virtual network, bypassing the ExpressRoute gateway.

The Ultra Performance ExpressRoute Gateway SKU provides faster data path performance between the on-premises network and the virtual network.
The ExpressRoute Gateway SKU must be configured with Ultra Performance to enable FastPath