I need some help because I'm really desperate about my issue.
I'm running a single Fortigate-VM in Azure. It is configured with one external (port1) and one internal (port2). In Azure a VNet with the IP range 172.16.0.0/16 is deployed and there are several subnets subnet's deployed. The reason why I get in touch today is that my issue shouldn't be an issue. The route attached to the VNet seems to ignore what's configured in there.
First of all the route table is configured like that:
The configuration behaves - in my point of view - a little bit weird. It seems that the between different subnets doesn't pass the Fortigate. I assume this because if a ping to a VM in another Subnet is executed it doesn't be shown in the logs. A tracert to the VMs doesn't show the Fortigate as a hop as well. Removing the "Virtual Network" routes results that the ping is shown in the logs on Fortigate, but the VMs within the same subnet can't communicate to each other anymore.
Does anyone have any advice what's happening here?