Azure Maps pricing: Local business search API, GET / search/ poi/ {format}
Is Azure Maps yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
- Free, Gen2 FreeGen2 Free$0.00 per 1,000
- Pay as you go, Gen2 <500KGen2 <500K$0.045 per 1,000
- Contact us, Gen2 500K+Gen2 500K+
GET / search/ poi/ {format} one of Azure Maps's 3 callsGET /Free, Gen2 Free$0.00 per 1,000search/ nearby/ {format} GET /Free, Gen2 Free$0.00 per 1,000search/ poi/ {format} GET /Free, Gen2 Free$0.00 per 1,000search/ poi/ category/ {format}
About this item
- Freshness. We don't know how fresh this plan's data is.
- 6 of the 8 key fields we check. Address, Phone, Website, Category, Coordinates, Opening hours.
- Nothing to pay. You get 5,000 requests a month, enough for 5,000 pages.
- One call. You send
queryandformattoGET /. You setsearch/ poi/ {format} api-versionto "1.0". The call returns the businesses there. - Who can get it: anyone with an Azure Maps account. Keep data: with conditions. Use data: with conditions.
Azure Maps: Local business search API alternatives
Azure Maps alternatives: every Local business search API plan compared
The table starts with Azure Maps's cheapest paid plan. Next come plans from other providers with the price per 1,000 places closest to Azure Maps's.
| Azure Maps, pay as you go, Gen2 <500K, GET /search/poi/{format} | Mapbox, pay as you go, Introductory preview pricing, 50,001 - 500,000 requests, GET /search/searchbox/v1/category/{canonical_category_id} | Amazon Location Service, pay as you go, On-demand, POST /v2/search-text, SearchText (Stored) | Stadia Maps, $20 monthly, Starter, GET /geocoding/v1/search | Amap, CNY 50,000 yearly, 技术服务许可 基础版, GET /v5/place/around | |
|---|---|---|---|---|---|
| $ per 1,000 places | $0.045 | $0.04 | $0.04 | $0.04 | $0.05 |
| Completeness | 75% | 75% | 75% | 50% | 75% |
| Billing | pay as you go | pay as you go | pay as you go | monthly | yearly |
| Pay | monthly | monthly | monthly | $20 | CNY 50,000 |
| Enough for | as many as you pay for | as many as you pay for | as many as you pay for | 50,000 pages a month | 500,000 pages a month |
| Who can get it | anyone with an Azure Maps account | anyone 18 or older | anyone with an AWS account | anyone with a Stadia Maps account | legal entities and organisations that buy Amap's technical service licence, which commercial use of the service needs |
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-04.
- 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-search-poi
- 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.
- Address
- Phone
- Website
- Category
- Coordinates
- Rating, not in the answer
- Review count, not in the answer
- Opening hours
| $ per 1,000 places | $0.00 |
|---|---|
| Per | page of 100 |
| Billing | free |
| Most per search | 2,000 |
|---|---|
| Also pays for | from the same budget: Get Search POI Category · Get Search Nearby · Batch Search · Geocode Autocomplete |
| $ per 1,000 | $0.00 |
|---|
| Their pitch | Use to search for points of interest by name. The Points of Interest (POI) Search API is an HTTP GET request that allows you to request POI results by name. It also supports additional query parameters such as language and filtering results by area of interest driven by country/region or bounding box. The Endpoint will return only POI results matching the query string. Response includes POI details such as address, coordinate location and category. |
|---|
| 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 | 5,000 pages a month |
| Per second | 500 |
|---|
| Answer | in the call |
|---|
| You send | query, format, api-version "1.0". Optional: typeahead, limit, ofs, categorySet, countrySet, lat, lon, radius, topLeft, btmRight, language, extendedPostalCodesFor, brandSet, connectorSet, view, openingHours |
|---|---|
| Method | GET |
| Path | /search/poi/{format} |
| Plan | Gen2 Free |
|---|---|
| Who can get it | anyone with an Azure Maps account |
The 33 fields the plan's answer can hold
name, address, street number, street name, neighborhood, municipality subdivision, municipality, local name, county, tertiary subdivision, state, state name, ZIP code, extended ZIP code, country, country code, country code (ISO 3166-1 alpha-3), latitude, longitude, viewport, entry points, distance, place ID, data source info, phone, website, brands, categories, category IDs, classification code, classification names, opening hours, total results