vwan route map not working as expected

Martin Kallukalam 460 Reputation points
2025-05-25T17:39:54.4333333+00:00

My configuration (POC) is like this.
I have a VWAN with 2 VNETs
10.30.96.0/19
10.30.224.0/19

A P2S VPN with address pool 172.24.10.0/24

My Windows Laptop with Azure VPN client configured using downloaded hub vpn profile.

Standard everything as per Azure doc.
I have a route map with a rule as below and is attached to outbound P2S

User's image

User's image

Problem #1
I am expecting to see summary route 10.30.0.0/16 in route map dashboard. However it is showing individual VNET route
User's image

Problem #2
I downloaded a fresh vpn config from HUB . When I connect P2S Azure VPN client , I do not see summary routes, instead I see individual VNET routes.
User's image

Observation:
I do not think route map is functioning as expected or what else am I missing

Azure Virtual WAN
Azure Virtual WAN
An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.
{count} votes

Accepted answer
  1. Sindhuja Dasari 1,520 Reputation points Microsoft External Staff Moderator
    2025-05-27T04:07:51.04+00:00

    Hello Martin Kallukalam

    Thank you for the update and additional details.

    Based on your current route map dashboard, it appears you’re seeing only the summarized route as expected. The specific routes (10.30.96.0/19 and 10.30.224.0/19) should not be advertised to the VPN client, but it is reflecting the changes in VPN Client.

    Steps we have tried in the lab environment:
    Remove
    the existing rule that only performs a “replace” operation.

    Create two separate rules,

    Rule 1: Drop Specific Prefixes

    • Match condition: 10.30.96.0/19, 10.30.224.0/19 (If comma separation doesn't work, create two separate rules with action drop and next step continue)
    • Action: Drop
    • Next step: Continue

    This rule ensures the individual /19 routes are not propagated to the VPN client.

    Rule 2: Permit and Replace with Summarized Prefix

    • Match condition: Prefix contains 10.30.0.0/16
    • Action: Modify
    • Modification: Replace with 10.30.0.0/16
    • Next step: Terminate

    Even after trying several rules, we observed that summarization only occurred at the route map dashboard level and not at the VPN site level.

    We will reach out to the backend team regarding this feature issue.

    Thank you for your time, Martin!


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

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Alex Burlachenko 13,330 Reputation points Volunteer Moderator
    2025-05-26T08:09:54.29+00:00

    Hey there,

    thanks for posting your question about the virtual wan route map not working as expected. I appreciate you taking the time to share this on the Microsoft Q&A portal )).

    From what I understand, you're having trouble with route maps in azure virtual wan not behaving the way you intended. Let me try to break this down in a simple way while still keeping the technical details.

    So, route maps in virtual wan are used to control how routes are propagated between different connections. The documentation explains this here: Virtual WAN routing intent and routing policies.

    A common issue folks run into is that the route map rules might not be applied in the order you expect. The processing happens sequentially based on the priority you set. Maybe double check that your rules are ordered correctly? Also make sure the match conditions are properly configured - sometimes small typos in the community values or prefixes can cause the whole thing to not work as intended.

    Another thing to look at is the propagation settings. The routes need to be properly propagated to the hub for the route maps to take effect. You can verify this in the virtual hub routing section under "propagated routes". Here's more info on that: Configure virtual hub routing.

    If you could share more details about exactly what behavior you're seeing versus what you expected, that would help pinpoint the issue better. Like are certain routes missing entirely or just not taking the path you wanted? Also screenshots of your route map configuration would be super helpful if you can add those.

    Don't worry if this seems confusing at first - routing in virtual wan can be tricky until you get the hang of it. We'll figure this out together )). Let me know if you need clarification on any of these points or if there's other aspects of the setup you'd like to discuss.

    Thanks again for engaging with the community and posting your question! Looking forward to helping resolve this.

    Best regards,
    Alex
    P.S. If my answer help to you, please Accept my answer
    PPS That is my Answer and not a Comment
    https://ctrlaltdel.blog/
    
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.