Design, Implement, and Manage VNet Routing

The main purpose of an Azure virtual network (VNet) is to facilitate the delivery of data between point A (an Azure VNet workload) and point B (other connected systems). Routing defines the path that the transferred data will take between point A and point B.

There is a default routing behavior for workloads in an Azure subnet, but we also have options to customize the default behavior and control/influence the path of network traffic.

This is useful for many scenarios. For example, you may have an organizational requirement to inspect outbound network traffic with network virtual appliances (NVAs), such as third-party firewall solutions, for example, Palo Alto VM-Series firewalls. To implement this architecture, traffic must be properly routed through the NVAs for the inspection to occur. You may also have a requirement to redirect internet-bound traffic to an on-premises gateway instead of directly via Azure’s internet connectivity...