Azure Maps Address autocomplete API pricing
Is Azure Maps yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
GET / geocode: autocomplete Azure Maps' only call for this API- Azure Maps address autocomplete API
- Azure Maps IP geolocation API
- Azure Maps local business search API
GET /search/ nearby/ {format} - Azure Maps local business search API
GET /search/ poi/ {format} - Azure Maps local business search API
GET /search/ poi/ category/ {format}
About this item
- Freshness. We don't know how fresh this plan's data is.
- 7 of the 8 fields on our checklist. Street, House number, Postcode, City, State, Country, Coordinates.
- Nothing to pay. You get 5,000 requests a month, enough for 50,000 calls.
- One call. You call
GET /. You sendgeocode: autocomplete queryand one ofcoordinatesorbbox. You setapi-versionto "2026-01-01". You can also sendtop,resultTypeGroups,resultTypes,view,countryRegionand theAccept-Languageheader. The call returns the addresses it suggests for each search. - Who can get it: anyone with an Azure Maps account. Keep data: with conditions. Use data: with conditions.
Azure Maps: address autocomplete API alternatives
Azure Maps alternatives: every address autocomplete API provider ranked
The table starts with Azure Maps' cheapest paid plan. Next come plans from other providers with the price per 1,000 searches closest to Azure Maps'.
| Azure Maps, pay as you go | 2GIS, ₽26,700 monthly | getAddress.io, A$10 monthly, 500 per day, GET /get/{id} | Addressable, $74 monthly | Geocode Earth, $200 monthly | |
|---|---|---|---|---|---|
| $ per 1,000 searches | $0.45 | $0.425 | $0.464 | $0.493 | $0.50 |
| Completeness | 88% | 75% | 75% | 75% | 100% |
| Billing | pay as you go | monthly | monthly | monthly | monthly |
| Pay | monthly | ₽26,700 | A$10 | $74 | $200 |
| Enough for | as many as you pay for | 750,000 calls a month | 500 calls a day | 5,000 calls a day | 400,000 calls a month |
| Freshness | unknown | unknown | 3 months | 1 month | unknown |
| Who can get it | anyone with an Azure Maps account | legal entities and fully capable individuals, residents or non-residents | anyone | anyone | anyone with an account, for apps provided directly to end users |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-09.
- azure.microsoft.com/en-us/pricing/details/azure-maps/
- azure.microsoft.com/en-us/products/azure-maps
- learn.microsoft.com/en-us/azure/azure-maps/azure-maps-qps-rate-limits
- learn.microsoft.com/en-us/azure/azure-maps/understanding-azure-maps-transactions
- learn.microsoft.com/en-us/rest/api/maps/search/get-geocode-autocomplete
- prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20%27Azure%20Maps%27%20and%20armRegionName%20eq%20%27eastus%27
- microsoft.com/licensing/terms/productoffering/MicrosoftAzure/MCA
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Street
- House number
- Postcode
- City
- State
- Country
- Coordinates
- Suggestion ID, not in the answer
| $ per 1,000 searches | $0.00 |
|---|---|
| Per | call |
| Billing | free |
| Most per search | 20 |
|---|---|
| Also pays for | from the same budget: Get Search POI · Get Search POI Category · Get Search Nearby · Get Search Address · Get Search Address Structured · Get Search Fuzzy · Batch Search |
| $ per 1,000 calls that find nothing | $0.00 |
|---|
| Their pitch | Use to get ranked list of suggested entities based on a user's location and a partial query. Given a request with a user's location and a partial query that serves as the prefix of a full query string (referred to as a query prefix), the Azure Maps Autocomplete API returns a list of suggested entities that the user is most likely searching for. These entities are ranked from most to least likely. |
|---|
| Keep data | the validity period indicated in returned headers or 6 months, whichever is shorter |
|---|---|
| Use data | Customer may not use Azure Maps, or any part thereof (1) to enable turn-by-turn navigation functionality in any Customer Solution or use within an automatic or autonomous vehicle control, or (2) with a vehicle’s dashboard, or a device connected to a vehicles dashboard, systems, or sensors, except that the device may be connected to the vehicle power source for charging purposes. Customer may not use Azure Maps or any part thereof to create a competing database or service, or a derived database populated wholly or partially with Customer’s content and/or content supplied or created by any third party. Customer will not use the content delivered by the Azure Maps in combination with any other third-party database, except that Customer may layer onto the content a type of content not already included within Azure Maps (such as Customer's proprietary content) or which Microsoft separately licenses to Customer. When using content licensed under or subject to an open-source license, Customer may not combine the use of Azure Maps, or any part thereof, in a way that potentially compromises copyright protection. Customer will not modify or create a derivative work based on Azure Maps, or any part thereof, unless expressly permitted to do so under these terms. Microsoft may, in its sole discretion, limit the rate at which Azure Maps, or any portion thereof, may be called. Customer may not cache or store results delivered by the Azure Maps API for the purpose of scaling such Results (as defined below) to serve multiple users, or to circumvent any functionality in Azure Maps, including but not limited to (i) map data tiles, or (ii) information on the calculation of a path between two (2) or more points (“Route”) information (collectively the “Results”). Caching and storing Results and locations (latitude and longitude pair) or addresses that have been returned from a call to Azure Maps (“Geocode”/ ”Reverse Geocode”) are permitted where the purpose of caching is to reduce latency times of the Customer Solution. Results may not be stored for longer than: (i) the validity period indicated in returned headers, or (ii) 6 months, whichever is shorter. However, Customer may store Geocodes as long as Customer maintains an active Azure account. Customer may not display any Results, and/or Azure Maps Weather service results, solely as described in these Terms, on any third-party content or geographical map database. Use of content displaying the TomTom copyright notice must be in accordance with restrictions set forth in the TomTom Licensing Third Party Product Terms and EULA (https://tomtom.com/product-attributions/). Azure Maps may include content that is subject to the Open Data Commons Open Database License ("ODbL"), available at https://opendatacommons.org/licenses/odbl/ or a successor site. Customer’s use of such content is subject to the terms of the ODbL, including the License and Community Guidelines available at https://osmfoundation.org/wiki/Licence/Community_Guidelines, as well as these terms. [...] Customers may not remove, obscure, mask or change any logo and/or copyright notice placed on or automatically generated by Azure Maps. Customer must display in a conspicuous manner within Customer Solution any Microsoft or third-party attribution provided by Microsoft. In addition, customers using the Azure Maps Render services must use the "Get Map Attribution” API to obtain the copyright attribution text and display it in their Customer Solution. |
| Pay | $0 |
|---|---|
| You get | 5,000 requests a month |
| Enough for | 50,000 calls a month |
| Per second | 100 |
|---|
| Answer | in the call |
|---|---|
| Median | 0.05 s |
| You send | query, api-version "2026-01-01", one of coordinates or bbox. Optional: top, resultTypeGroups, resultTypes, view, countryRegion, Accept-Language header |
|---|---|
| Method | GET |
| Path | /geocode:autocomplete |
| Plan | Gen2 Free |
|---|---|
| Who can get it | anyone with an Azure Maps account |
The 22 fields the plan's answer can hold
type group, type, name, address line, formatted address, street number, street name, neighborhood, locality, administrative district, administrative district short name, ZIP code, country, country code, intersection display name, intersection base street, intersection type, intersection secondary street 1, intersection secondary street 2, latitude, longitude, next link