ExpressRoute routing tables should return standardized data
When querying the route tables on a Private Peer (via Portal, Powershell or Azure CLI) the routes returned can vary depending on location - presumably because there are different platforms providing these tables:
e.g. for a default route advertised from on-premises to the MSEE:
EASTUS2 returns 0.0.0.0
CENTRALUS returns 0.0.0.0/0/
The different formats make automating route discovery/confirmation a pain - the API should normalize this data so the tables are consistent regardless of the underlying platform's own formatting nuances.