NSv in Azure Route Same VNET different address space
I am attempting to setup some routing in Azure for a new NSv. I used this article as my guide How can I route all traffic to SonicWall NSv using the same address space (same VNet) and different subnet behind X0 interface? | SonicWall
However, my issue is slightly different. I am using the same VNET but I have several different address spaces.
I created a separate network for X0 using 10.181.254.0/26. My X0 IP is 10.181.254.11. The Azure GW IP is 10.181.254.1. I can see this in my ARP table.
I have an Azure routing table setup with the next hop of 10.181.254.11. Right now 172.29.23.0/24 is using this routing table.
I have a test machine on the same VNET with a an address space of 172.29.23.0/24. Its IP is 172.29.23.4. I have created a route on the NSv to 172.29.23.0/24 with a next hop of 10.181.254.1. I can ping 172.29.23.4 from the firewall. When I run a ping from the test machine to 22.214.171.124 and run a packet capture on the firewall, I see that the firewall is forwarding traffic to X1. But the pings fail.
If I was doing this with a physical firewall, I would create a virtual interface on 172.29.23.0/24 and be done with it. Do I need to do something similar on the Azure firewall?