@André Sauer Caprini Please make sure to check that this route is propagated to the route table of the Spoke vnet by looking at the effective routes in the Azure Portal. If the Spoke vnet and Hub vnet are peered networks, you need to have selected the option to "use the remote virtual network's Gateway" on the spoke vnet for it to get the BGP propagated routes on its Route Table. Please also check to confirm that there are no conflicting routes such as an UDR for the same on-premise destinations. Please refer to How Azure selects a route in this document to see how Azure picks the next hop. Otherthan these checks, there is no need to create a new route table as such for this spoke vnet. Hope this helps.
Please let us know if you have any further questions and we will be glad to assist you further. 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.