Express Route permissions are not configure properly from MS side
This is a permission issue. when a service principal is giving read access on express route circuit, it's able to list all route for private connection using CLI and Powershell commands along with the ability to see it directly from the azure portal. However, it's not able to list the route using Rest calls. This issue basically means that permissions across express route are not configured properly. We need a work around it.