Azure Maps totalResults is always 100

Question

Azure Maps totalResults is always 100

Haiko Wick 20

Hi, we are currently testing Azure Maps as an alternative to google Maps for categorized radius searches around a location. Unfortunately, we are encountering a problem with pagination:

Regardless of the requested location and radius, the Nearby search (and also the POI search) returns a maximum of 100 results (totalResults). If the offset is set to 100, no more results are returned. The example given in https://learn.microsoft.com/de-de/rest/api/maps/search/get-search-nearby?view=rest-maps-1.0&tabs=HTTP#examples also returns a totalResults of 100 and does not allow pagination. Is there a configuration option we might have overlooked?

Using Gen2 (Maps & Location Insights) in West Europe

VSawhney 795 Reputation points Microsoft External Staff Moderator

2025-05-30T05:50:31.69+00:00
Hello Haiko Wick,

It sounds like you're running into a limit with the Azure Maps API, where your nearby and POI searches are consistently returning a maximum of 100 results, regardless of the parameters used.

This behavior can be related to several factors, including:

Default Pagination Limit: Currently, Azure Maps may have an internal limit set to return a maximum of 100 results by default for certain queries. The ability to paginate beyond these 100 results may not be supported for the Nearby search and POI search endpoints you're using.

Service Documentation: As per the Azure Maps documentation, there isn’t a clear mention of how to override this limitation directly for the searches you're conducting, unlike the mechanisms available in Azure AI Search where you can adjust top and skip parameters.

Potential Configuration Issues: There might not be an explicit configuration option you'll need to adjust to facilitate the fetching of more than 100 results. However, reaching out to Azure support could provide further insights if this is something that could be updated or changed in the future.

Here are a few suggestions on what you could try:

Double-check Parameters: Ensure you're not missing any optional parameters that might help in broadening the search results.

Use Different Queries: If your use case allows, consider alternative query strategies or combining search requests with different parameters to broaden the data you receive.

Hope this helps!
Thank you!
VSawhney 795 Reputation points Microsoft External Staff Moderator

2025-06-03T06:08:54.8733333+00:00

Hello Haiko Wick,

Following up to check if the responses provided helped you. Please feel free reach us for further help.

Thank you!
VSawhney 795 Reputation points Microsoft External Staff Moderator

2025-06-04T09:30:19.6366667+00:00

Hello Haiko Wick,

We haven’t heard from you on the responses provided and was just checking back to see if you have a resolution yet. Please feel free reach us for further help.

Thank you!
Haiko Wick 20 Reputation points

2025-06-05T04:51:11.5866667+00:00

Unfortunately, none of the answers really bring us any closer to using the service and it is still unclear to me whether this is by design and therefore the documentation is wrong or vice versa. It is also unclear whether there are any changes or a correction planned on either side. But I can follow rbrundritt's answer (thanks for that!) - since I also tested the TomTom service myself shortly afterwards and found the same behavior there, I am contacting TomTom directly.

Accepted answer

1 additional answer

Your answer

VSawhney 795 Reputation points Microsoft External Staff Moderator

2025-05-30T05:50:31.69+00:00

Hello Haiko Wick,

It sounds like you're running into a limit with the Azure Maps API, where your nearby and POI searches are consistently returning a maximum of 100 results, regardless of the parameters used.

This behavior can be related to several factors, including:

Default Pagination Limit: Currently, Azure Maps may have an internal limit set to return a maximum of 100 results by default for certain queries. The ability to paginate beyond these 100 results may not be supported for the Nearby search and POI search endpoints you're using.

Service Documentation: As per the Azure Maps documentation, there isn’t a clear mention of how to override this limitation directly for the searches you're conducting, unlike the mechanisms available in Azure AI Search where you can adjust top and skip parameters.

Potential Configuration Issues: There might not be an explicit configuration option you'll need to adjust to facilitate the fetching of more than 100 results. However, reaching out to Azure support could provide further insights if this is something that could be updated or changed in the future.

Here are a few suggestions on what you could try:

Double-check Parameters: Ensure you're not missing any optional parameters that might help in broadening the search results.

Use Different Queries: If your use case allows, consider alternative query strategies or combining search requests with different parameters to broaden the data you receive.

Hope this helps!
Thank you!
VSawhney 795 Reputation points Microsoft External Staff Moderator

2025-06-03T06:08:54.8733333+00:00

Hello Haiko Wick,

Following up to check if the responses provided helped you. Please feel free reach us for further help.

Thank you!
VSawhney 795 Reputation points Microsoft External Staff Moderator

2025-06-04T09:30:19.6366667+00:00

Hello Haiko Wick,

We haven’t heard from you on the responses provided and was just checking back to see if you have a resolution yet. Please feel free reach us for further help.

Thank you!
Haiko Wick 20 Reputation points

2025-06-05T04:51:11.5866667+00:00

Unfortunately, none of the answers really bring us any closer to using the service and it is still unclear to me whether this is by design and therefore the documentation is wrong or vice versa. It is also unclear whether there are any changes or a correction planned on either side. But I can follow rbrundritt's answer (thanks for that!) - since I also tested the TomTom service myself shortly afterwards and found the same behavior there, I am contacting TomTom directly.

Answer 1

This is one of the older search services that is directly powered by TomTom. If memory serves me correctly TomTom modified the backend of this service a year or two ago so that only the first 100 POI's may be retrieved. I believe there were concerns with individuals scraping the POI data and creating databases. The pagination is still there as many users will retrieve 10 results at a time and allow users to page to the next 10 results.

I'm not on the Azure Maps team, but wrote a lot of the code samples for Azure Maps and recall one where I had it paging through POI's and a few years ago it stopped getting more than 100 results. Testing the TomTom service that powers this Azure Maps API I see the same behavior: https://developer.tomtom.com/search-api/documentation/search-service/nearby-search

Answer 2

Hi Haiko Wick

Currently Nearby Search and POI Search APIs are capped at returning 100 results per request.

To retrieve more than 100 results, you can use the ofs (offset) parameter in combination with limit. This allows you to paginate through the results.

Attached is the sample example source code

Sample -https://samples.azuremaps.com/?search=search&sample=load-pois-as-the-map-moves

Source code -

Reference thread -https://learn.microsoft.com/en-us/answers/questions/1180380/how-to-extend-the-limit-of-100-in-azure-maps-searc

Hope it helps.

Thank you.

Share via

Azure Maps totalResults is always 100

1 additional answer

Your answer