Forum Discussion
Found inconsistencies in the Address Autocomplete API results between Bing Maps and Azure Maps
Hi Team,
We are currently in the process of upgrading our application from Bing Maps to Azure Maps. As part of this migration, we are evaluating the Azure Maps Address Autocomplete API to ensure it provides functionality comparable to our existing Bing Maps implementation. During our evaluation, we observed several inconsistencies in the https://samples.azuremaps.com/rest-services/autocomplete API results between Bing Maps and Azure Maps, particularly for addresses in India. and would appreciate your assistance in investigating these issues.
As part of our testing, we searched for below address:
- Everest Nivara Infotech Park
- Mumbai International Airport
- IIT Bombay
The address is correctly returned in the Bing Maps portal:
https://www.bing.com/maps
However, when performing the same search using the https://samples.azuremaps.com/rest-services/autocomplete, the expected address is either not returned or is displayed incorrectly.
Additionally, we observed that business (POI) addresses are not being returned by the Azure Maps Address Autocomplete service. As part of our testing, we searched famous place name in the Address Autocomplete sample. The business was not returned in the autocomplete suggestions, even though it is searchable in the Bing Maps portal.
We would appreciate your guidance on resolving these issues.
Thanks!
2 Replies
Yes, Azure Maps and Bing Maps use different data providers and search algorithms, which can lead to discrepancies in address and POI (Point of Interest) autocomplete results, especially in regions like India.
https://learn.microsoft.com/en-us/azure/azure-maps/migrate-bing-maps-overview
You’re comparing Bing Maps autocomplete with Azure Maps for Indian addresses and POIs, where Azure Maps omits or mislabels results. The key distinction is endpoint scope: Azure Maps Address Search is for geocoding and does not return POIs, while Fuzzy Search combines address and POI indexes and supports type-ahead. Test the production REST endpoint with the full query, countrySet=IN, view=IN, typeahead enabled, and a Mumbai latitude and longitude bias or bounding box. For business names, use Fuzzy Search with POI included; for street addresses, use Address Search or Geocode Autocomplete. Log the exact request, API version, response, and coordinates for every missing result. Azure Maps and Bing Maps use different search data and ranking, so identical suggestions are not guaranteed. If a named place remains absent after scoped testing, submit the reproducible request and expected location to Azure support as a data-quality issue.
