# Azure Maps, free: IP geolocation API > Use to get the ISO country/region code for a given IP address. The Get IP To Location API is an HTTP GET request that returns the ISO country/region code for a given IP address. Developers can use this information to block or modify content based on the geographical location from which the application is accessed. Azure Maps' Gen2 Free plan for the IP geolocation API costs $0.00 per 1,000 IP addresses. We check each provider's docs for 8 fields. Azure Maps' docs list 1: Country. In [our IP geolocation API benchmark](https://datacircle.dev/best-ip-geolocation-api.txt), the best plan from Azure Maps scores 25.5 out of 100. Azure Maps ranks 27th of 27 providers. This plan is free. We rank 429 plans for IP geolocation APIs by price. Half the plans cost $0.214 or less per 1,000 IP addresses. [149 IP geolocation API plans on our price sheet are free.](https://datacircle.dev/best-ip-geolocation-api.txt) [Apixies' free plan](https://datacircle.dev/ip-geolocation-apis/apixies/free-sandbox-no-account/llms.txt) scores highest of the free plans in our benchmark, at 89.6 out of 100. [IPWho.org's $99 monthly plan](https://datacircle.dev/ip-geolocation-apis/ipwho-org/99-monthly-enterprise-get-ip-ip/llms.txt) is the cheapest paid plan per 1,000 IP addresses, with no charge per call. You get as many IP addresses as IPWho.org's rate limit allows. [Api.co.id's Rp19,000 monthly plan](https://datacircle.dev/ip-geolocation-apis/api-co-id/rp19000-monthly/llms.txt) costs the least for 10,000 IP addresses a month: about $1.05. [Api.co.id's Rp99,000 (about $5) monthly plan](https://datacircle.dev/ip-geolocation-apis/api-co-id/rp99000-monthly/llms.txt) covers any number of IP addresses, and costs less up front than IPWho.org's $99 monthly plan. [Apixies](https://datacircle.dev/ip-geolocation-apis/apixies/free-sandbox-no-account/llms.txt), [getmyip.pro](https://datacircle.dev/ip-geolocation-apis/getmyip-pro/free-getmyip-get-v1-ip/llms.txt) and [IPFlare](https://datacircle.dev/ip-geolocation-apis/ipflare/16-80-monthly-unlimited-get-ip/llms.txt) are the best IP geolocation API providers in the Datacircle benchmark. - This page: https://datacircle.dev/ip-geolocation-apis/azure-maps/free - [IP geolocation API in 2026: the best of 20+ compared](https://datacircle.dev/best-ip-geolocation-api.txt) - Get it: https://azure.microsoft.com/en-us/pricing/details/azure-maps/?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - Request: `GET https://atlas.microsoft.com/geolocation/ip/{format}` - API key: with the plan, on https://azure.microsoft.com/en-us/pricing/details/azure-maps/?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - Its API docs: https://learn.microsoft.com/en-us/rest/api/maps/geolocation/get-ip-to-location?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - Sold by: Azure Maps (https://azure.microsoft.com/en-us/products/azure-maps?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing) - Checked: 2026-11-09 ## In the answer - Completeness: 13% - Country: ✓ ## Price - $ per 1,000 IP addresses: $0.00 - Per: call - Billing: free ## Charges - Also pays for: nothing else ## Not found - $ per 1,000 calls that find nothing: $0.00 ## In their words - Their pitch: Use to get the ISO country/region code for a given IP address. The Get IP To Location API is an HTTP GET request that returns the ISO country/region code for a given IP address. Developers can use this information to block or modify content based on the geographical location from which the application is accessed. ## Data - 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. ## Plan - Pay: $0 - You get: 5,000 requests a month - Enough for: 5,000 calls a month ## Rate limit - Per second: 50 ## Speed - Answer: in the call - Median: 0.00 s ## The call - You send: ip, format "json", api-version "1.0" - Method: GET - Path: /geolocation/ip/{format} ## About the plan - Plan: Gen2 Free - Who can get it: anyone with an Azure Maps account ## The 2 fields the plan's answer can hold IP address, country code ## Azure Maps' plans (3) - [Azure Maps, free](https://datacircle.dev/ip-geolocation-apis/azure-maps/free/llms.txt): $0.00 per 1,000, 13% complete - [Azure Maps, pay as you go](https://datacircle.dev/ip-geolocation-apis/azure-maps/pay-as-you-go/llms.txt): $4.50 per 1,000, 13% complete - [Azure Maps, contact us](https://datacircle.dev/ip-geolocation-apis/azure-maps/contact-us/llms.txt): 13% complete ## Azure Maps' calls for this API (1) - `GET /geolocation/ip/{format}`: [Azure Maps, free](https://datacircle.dev/ip-geolocation-apis/azure-maps/free/llms.txt) ## Azure Maps' APIs (2) - [Azure Maps IP geolocation API pricing, 3 plans](https://datacircle.dev/ip-geolocation-apis/azure-maps/free/llms.txt) - [Azure Maps Local business search API pricing, 3 plans, GET /search/nearby/{format}](https://datacircle.dev/local-business-search-apis/azure-maps/free-gen2-free-get-search-nearby-format/llms.txt) - [Azure Maps Local business search API pricing, 3 plans, GET /search/poi/{format}](https://datacircle.dev/local-business-search-apis/azure-maps/free-gen2-free-get-search-poi-format/llms.txt) - [Azure Maps Local business search API pricing, 3 plans, GET /search/poi/category/{format}](https://datacircle.dev/local-business-search-apis/azure-maps/free-gen2-free-get-search-poi-category-format/llms.txt) ## Azure Maps: IP geolocation API alternatives [Azure Maps alternatives: every IP geolocation API provider ranked](https://datacircle.dev/azure-maps-alternatives.txt) We list Azure Maps' cheapest paid plan first. Next we list other providers' plans closest to Azure Maps in price per 1,000 IP addresses. - [Azure Maps, pay as you go](https://datacircle.dev/ip-geolocation-apis/azure-maps/pay-as-you-go/llms.txt): $4.50 per 1,000, 13% complete - [Provero, top-up, 50,001 to 100,000 requests a month, POST /api/fraud-check/geoip](https://datacircle.dev/ip-geolocation-apis/provero/top-up-50001-to-100000-requests-a-month-post-api-fraud-check-geoip/llms.txt): $4.00 per 1,000, 50% complete - [EUVatAPI, €47.90 yearly](https://datacircle.dev/ip-geolocation-apis/euvatapi/47-90-yearly/llms.txt): $4.492 per 1,000, 13% complete, 1 week - [ipify, $23 pack, One-time purchase: 10,000 Credits, GET /api/v2/country,city](https://datacircle.dev/ip-geolocation-apis/ipify/23-pack-one-time-purchase-10000-credits-get-api-v2-country-city/llms.txt): $4.60 per 1,000, 88% complete, 1 day - [FraudLabs Pro, $499.95 monthly](https://datacircle.dev/ip-geolocation-apis/fraudlabs-pro/499-95-monthly/llms.txt): $4.9995 per 1,000, 88% complete ## 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. - https://azure.microsoft.com/en-us/pricing/details/azure-maps/?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - https://azure.microsoft.com/en-us/products/azure-maps?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - https://learn.microsoft.com/en-us/azure/azure-maps/azure-maps-qps-rate-limits?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - https://learn.microsoft.com/en-us/azure/azure-maps/understanding-azure-maps-transactions?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - https://learn.microsoft.com/en-us/rest/api/maps/geolocation/get-ip-to-location?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20%27Azure%20Maps%27%20and%20armRegionName%20eq%20%27eastus%27&utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing - https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/MCA?utm_source=datacircle.dev&utm_medium=referral&utm_campaign=ip-geolocation-api-pricing