Hi Ken,
I am from the Azure Maps product team. We are planning to release high resolution polygons in Azure Maps in GA by the end of this year. At this time, there will be no cost difference based on the polygon resolution. You may notice some difference in latency and response size for detailed polygons compared to simplified ones.
The underlying route algorithm used to generate these polygons for Azure Maps and Bing Maps are different. Azure Maps polygons are detailed enough to support accurate spatial filtering for travel time and distance queries. Azure Maps also supports larger travel time/distance budgets when compared with Bing Maps.
For example, I created a 20-minute travel time polygon from Smokey Point using a scenario similar to the one you shared. Bing Maps included Spencer Island Park which is over 25 minutes drive without traffic whereas Azure Maps returned more accurate range. Could you share an example where you see an issue with the accuracy of the polygon? Also interested to hear about your use case. Thank you!
Bing Maps
Azure Maps