Difference between Address Search and the API 2025-01-01 Geocode to get lat/lon?

Question

Difference between Address Search and the API 2025-01-01 Geocode to get lat/lon?

HSB 110

I currently updated our Azure Maps Route Matrix to use the newest API, 2025-01-01. In that process, I saw in the API the Geocode option to get lat/lon coordinates for addresses.

We currently use the Address Search option to do this. What is the difference? Is Address Search an old version or is it going away? Normally if this is the case, there's documentation saying so and pointing you to the new way to do it. My application has both options and they both work, I just don't know why you'd choose one over the other or perhaps the geocode option is better as it's newer and may use more sources to determine the coordinates.

Address Search: https://atlas.microsoft.com/search/address/json?&subscription-key={Your-Azure-Maps-Subscription-key}&api-version=1.0&language=en-US&query=400 Broad St, Seattle, WA 98109

Geocode using API 2025-01-01

https://atlas.microsoft.com/geocode?api-version=2025-01-01&subscription-key={Your-Azure-Maps-Subscription-key}&query=400 Broad St, Seattle, WA 98109

0 comments

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Hi HSB,

Great question — here's a clear breakdown of the difference between Address Search and Geocode (2025-01-01) in Azure Maps:

1. Address Search (Legacy API – search/address)

URL example: https://atlas.microsoft.com/search/address/json?api-version=1.0&query=...

Features:

Part of the Azure Maps Search API v1.

Offers comprehensive search capabilities, including fuzzy matching, multiple results, POI blending, and structured address input.

Still fully supported.

Uses TomTom's backend search engine.

Use cases:

When you want flexible, fuzzy address matching.

When searching for places or POIs alongside addresses.

When working with structured or unstructured addresses.

2. Geocode (New API – geocode?api-version=2025-01-01)

URL example: https://atlas.microsoft.com/geocode?api-version=2025-01-01&query=...

Features:

Part of the Azure Maps v2 APIs (2025-01-01).

Aims to be a simplified, purpose-specific endpoint focused purely on geocoding (address → lat/lon).

Likely built for better integration with v2 APIs (e.g., new Route Matrix, Matrix Metadata).

May evolve with more consistent behavior, optimized for enterprise use.

Use cases:

When all you need is direct address-to-coordinate conversion.

When using other 2025-01-01 APIs and want consistency across your calls.

When building modern solutions that rely on Azure Maps v2 stack.

Key Differences:

Feature	`search/address` (v1)	`geocode` (2025-01-01)
API version	1.0	2025-01-01
API version	`1.0`	`2025-01-01`
Focus	General address/POI search	Pure geocoding (address → lat/lon)
Result richness	Full POI support, fuzzy logic	Likely simpler, lat/lon focused
Backward compatibility	Existing apps use this	New API model for future use
Part of new Matrix stack	No	Yes
Preferred for new projects	No	Yes

Is search/address being deprecated?

No official deprecation notice has been published yet. Both APIs are supported. However, the geocode API is clearly the direction forward for apps aligning with Azure Maps 2025-01-01.

Recommendation:

If you're already using the new 2025-01-01 API stack for Route Matrix or other services, it's a good idea to move to the new geocode endpoint for consistency and future-proofing.

Keep search/address for legacy needs or broader search scenarios (POIs, fuzzy matching, etc.).

Let me know if you'd like side-by-side JSON response comparisons for both endpoints.

Best regards, Martin

rbrundritt 21,706 Reputation points Volunteer Moderator

2025-07-03T15:49:14.92+00:00

Also, the old Address Search only used TomTom, while the new Geocoder API is based on the same data as Bing Maps which has both TomTom and a lot of data from other sources. It also has improved matching capabilities. All in all, the new geocoder is notably more accurate.
HSB 110 Reputation points

2025-07-03T15:53:45.0933333+00:00

Thanks @Martin Egli & @rbrundritt I'm using the new API and grabbing the coordinates out of the geometry section.

root.features[0].geometry.coordinates[0]; // longitude
Andrew Martin 0 Reputation points

2026-01-15T09:12:46.1033333+00:00

We have a requirement to differentiate between a POI and address search in our software and therefore currently have to use version 1.0. We would however benefit from the "other sources" mentioned above, as sometimes the results are inaccurate. Are there plans to replicate this functionality in the newer versions?

Answer 2

A couple of key points; V1 Search services are a pass through to the TomTom APIs. This means data passed into this API is passed on to TomTom and processed by them. Additionally, it also means that Microsoft's only way to improve the results is to report issues to TomTom. The V2 services are powered directly by Microsoft (they host and process requests within their own systems). This means any data passed into the service is only handled by Microsoft, and they have a lot more ability to improve the accuracy of the services. The v2 geocoding service in particular uses the same backend as the Bing Maps geocoder. This is to make for a smoother transition for those moving from Bing Maps to Azure Maps, with the main difference being an updated API interface that aligns with open standards.

Share via

Difference between Address Search and the API 2025-01-01 Geocode to get lat/lon?

1 additional answer

Your answer