@Matthew Relouw Thank you for reaching out to Microsoft Q&A.
I understand that you are having issues with connectivity to your additional NIC attached to your WatchGuard Firebox where traffic forwarded to that NIC does not seem to be reaching the target VMs as expected.
Azure assigns a default gateway to the first (primary) network interface attached to the virtual machine. Azure does not assign a default gateway to additional (secondary) network interfaces attached to a virtual machine. Therefore, you are unable to communicate with resources outside the subnet that a secondary network interface is in, by default. Secondary network interfaces can, however, communicate with resources outside their subnet, though the steps to enable communication are different for different operating systems. Here are steps to enable the same for Windows VM : Configure guest OS for multiple NICs.
For Linux VM: Configure guest OS for multiple NICs
As mentioned in the document, Once you've added the route for a secondary interface, verify that the route is in your route table with route -n. Once you do the same, please check if the traffic reaches the target VM. If it still does not reach it, please capture the traffic on both the Firebox and the Target VM by using necessary filters to minimize traffic to only the extra NIC/test traffic and attach it here so we can verify the same. Thank you!
Remember:
Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.
Want a reminder to come back and check responses? Here is how to subscribe to a notification.