I have deployed a vMXin our Azure infrastructure in same Vnet as the resource but different subnets. The resource is able to communicate with the LAN of the vMX but i can't ping the resource from the vMX. I also created a route table such that all traffic to the internet from the resource will go through the vMX and associated the resource subnet with the route table but it doesn't seem to work. It seems i am missing something and support was not of much help. Please does anyone have a better idea on this.  vMX subnet=          10.16.112.0/24, vMX IP 10.16.112.4 Resource Subnet = 10.16.114.0/24, Resource IP 10.16.114.4   Ping from resource(10.16.114.4) to vMX(10.16.112.4) =Success Ping from vMX on dashboard(10.16.112.4) to vMX (10.16.114.4) =Failed. Again my priority id to route the Resource traffic via the vMX thereby using the vMX public IP from Azure to access the internet.     ... View more