Taking a look at the Azure Maps sample I noticed that it doesn't specify a radius
property in the request which would likely significantly improve things for this scenario. Alternatively, using the btmRight
and topLeft
properties of that service would also improve things. So give those a try to see if they address your issue.
That said, Azure Maps has been bringing over some of the Bing Maps services (fwd/rev geocoding and boundary services have already been brought over in the latest version of the search service). So I suspect that the Bing Maps Autosuggest service will also make its way over. The v1 search services are powered by TomTom (logic and data), while the Microsoft autosuggest service that's currently in Bing Maps has access to more data sources and improved logic.