Hi, probable dual issue: (1) the "failed to update route map: a retriable exception occurred" error is almost always a blocked plan control/concurrent operation or invalid constraint; (2) in Virtual WAN, route maps don't perform true "summarization": you can filter/modify prefixes, but not generate an aggregate.
Quick fix, everything in one go: verify that the Hub is Standard and in the Succeeded state (not Updating), that the connection has only one route map per direction (inbound/outbound), no simultaneous updates (Routing Intent/Firewall), remove the association from the connection → save the route map → reassociate it; valid names (no spaces/strange chars), valid CIDR prefixes, rules < limits (e.g., <50). If the portal continues to fail, apply via CLI/ARM: create the route map and then az network vhub connection update --inbound-route-map <id>/--outbound-route-map <id>; if it still fails, delete and recreate the route map (often unlocks the state).
To "summarize" the prefixes to Meraki: either perform the aggregation on Meraki (recommended), or in vWAN, publish only the summary (add it as a static route in the relevant Hub route table) and use the route map to deny the more specific outbound routes to the site, so the peer only sees the aggregate; in inbound from the site, you can do the opposite (allow only the summary or deny the specific routes).