Understanding the default routing for Azure VNet workloads
In previous chapters of this book, we created some VNets with subnets and deployed virtual machine (VM) workloads into them. Without making any changes, the default routing behavior for Azure subnets takes effect and controls the path that traffic will follow to get to their intended destination. Let’s examine what this default routing behavior looks like.
The default routing behavior for Azure subnets is controlled by system routes, which are automatically associated via a default route table (Figure 3.1). System routes are a collection of routing entries that define several destination networks (marked as the Address Prefix column in Figure 3.1) and the next hop to send the traffic to (marked as Next Hop Type in Figure 3.1) – this is the path that the traffic should follow to get to the defined destination.
Figure 3.1 – Azure VNet default route table with system routes
...
