Azure VM's NIC Effective Routes VS VM OS Route Table

Hello ,

I was deep diving the routing for the NIC effective routes and the VM OS route table which I found something left me curious to ask about . Let me tell you about my Lab:

VNet1 of address space : 10.1.0.0/16

• LAN1 subnet : 10.1.1.0/29
• LAN2 subnet: 10.1.2.0/29
• VM1 of ip: 10.1.1.4 /29
• VM2 of ip : 10.1.2.4/29

Below is the screenshot of the VM1 NIC effective routes : I understand that the NIC has learned the 10.1.0.0/16 which is the entire VNet address space and it will not learn the smaller subnets , thus covering the both LAN1 and LAN2 networks

Also let's have a look the route table of the OS VM : 10.1.1.0/29 is learned which is the LAN1 subnet

My Question here is why the VM1 OS route table didnt learn also the entire VNet address space similar to the VM NIC effective routes? and when trying to ping from VM1 to VM2 which is on another subnet it will follow the first default route 0.0.0.0 -->10.1.1.1 ( GW of LAN1 ) routing to the VM2 inside LAN2 ? and how tracerouting VM1 to VM2 is not showing any next hop?