stop propagating /32 default route per private endpoint to all of the route tables in directly peered Virtual Networks
Our current setup is hub-spoke model with spokes doing a vnet-peering to hub . We started seeing a lot of /32 default routes in our hub vnet route table with all the private endpoints we started creating in all spoke vnets.
In our setup we would like to see all flows go through NVAs in hub vnet, but these /32 default routes are causing the traffic flows sourcing from onprem to private endpoints to bypass NVA. As per the mitigations suggested under https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-overview#limitations, we started overriding system default /32 route with custom /32 udrs. But as route tables have 400 hard limit on number of udrs we can have, we would like to raise a feature request for something like a toggle button to stop seeing default /32 routes in peered hub vnet. we are okay with seeing these default routes in spoke vnet where private endpoint is created, but we don’t want to see them under peered vnets without any filter.