How do we resolve ConnectionRoutingConfigConflictsWithRoutingIntent Error?

Question

I have a hub virtual network connection with the routing configurations enabled with defaultRouteTable and when we associate this connection with a Secured Virtual WAN Hub (routing Intent Enabled), the error observed is ConnectionRoutingConfigConflictsWithRoutingIntent. The suggested approach is to "Leave Routing Configuration empty to auto populate". Can I get some insights into what this means to leave Routing Configuration empty? Does this mean not to Propagate routes to a route table (default in this case) and leave the Associate Route Table and Propagate to Route Tables as None?

If on the other hand, routing intent is disabled on the vHUB and the virtual network connection is created with default route tables and then routing intent re-enabled, this error is not seen. Need inputs on how this works.

Answer 1

Hi Krishna Sridhar

Greetings!

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

The error message talks about Misconfiguration ConnectionRoutingConfigConflictsWithRoutingIntent indicates that there is a conflict between the routing configurations you've set for your virtual network connection and the routing intent configured on your Secured Virtual WAN Hub (vHUB).

To enable routing intent and policies, your Virtual Hub must meet the below prerequisites:

• There are no custom route tables deployed with the Virtual Hub. The only route tables that exist are the noneRouteTable and the defaultRouteTable.
• You can't have static routes with next hop Virtual Network Connection. You may have static routes in the defaultRouteTable have next hop Azure Firewall.

Refer: https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies#prereq

For Routing Intent Enabled: When working with a vHUB that has routing intent enabled, ensure that you leave the routing configuration empty. This means:

• Do not associate any route table.
• Set route propagation options to None.

Refer: https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies#troubleshooting-configuration-issues

When the routing intent is disabled in Azure, it should not face any conflicts with custom route tables and propagation settings. This is because Azure does not enforce routing intent, allowing for more flexibility in managing routes.

NOTE: Hence, working with a Secured Virtual WAN Hub with routing intent enabled, allowing Azure to manage routing configurations automatically by leaving them empty is the recommended approach. This prevents conflicts and ensures that routing works as intended.

---

Hope this clarifies!

If above is unclear and/or you are unsure about something add a comment below.

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

Regards,

Ganesh