Azure Maps pricing

Simple and secure location APIs provide geospatial context to data

Enhance your IoT, mobility, asset tracking and logistics solutions with geospatial data using Azure Maps – geospatial services APIs that enable you to easily incorporate maps, search, routing, traffic and time zones into any of your projects.

Pricing details

Standard S0 Standard S1
Services offered
  • Map render
  • Search
  • Route
  • Traffic
  • Time zone
  • GeolocationPREVIEW
  • WeatherPREVIEW
  • Map render
    • Includes Satellite Imagery
  • Search
    • Includes Batch Search
  • Route
    • Includes Batch Routing
    • Includes Matrix Routing
    • Includes Route Range (Isochrones)
  • Traffic
  • Time zone
  • GeolocationPREVIEW
  • ElevationPREVIEW
  • Spatial Operations
    • Including Geo-fencing
  • Azure Maps dataPREVIEW
  • MobilityPREVIEW
  • WeatherPREVIEW
  • CreatorPREVIEW
    • Includes conversion
    • Includes dataset
    • Includes tileset
    • Includes feature state
    • Includes web feature
Use Case For small-scale deployments, customers requiring only the core geospatial APIs, and/or customers with small volumes of concurrent users For customers who need support for large-scale enterprise, mission critical applications, have high volumes of concurrent users and/or require advanced geospatial services
Included free quantity During Azure Maps Creator public preview, there will be no billing for Azure Maps Creator services (conversion, dataset, tileset, feature state, web feature)
Queries Per Second (QPS) 50 QPS Greater than 50 QPS
Price beyond included free quantity (For Maps, Traffic and Weather Tiles) $- per 1,000 transactions $- per 1,000 transactions
Price beyond included free quantity (Other Maps Services) $- per 1,000 transactions (for all APIs besides GeolocationPREVIEW)
$- per 1,000 transactions (for GeolocationPREVIEW)
$- per 1,000 transactions

*Note on transactions

For Maps, Traffic and Weather Tile requests, one transaction is created using increments of 15 tiles. Maps Tile requests made by S1 accounts include Aerial Imagery and Hybrid Aerial Imagery Tile requests.

For ElevationPREVIEW Maps Tile requests made by S1 accounts, one API tile request is counted as 50 transactions.

For Search Service, Route Service, Time Zone Service, GeolocationPREVIEW Service, single point ElevationPREVIEW Service, Spatial Operations except Geofencing, MobilityPREVIEW Service, WeatherPREVIEW Service, non-Map Tile Render Service and non-Traffic Tile Service requests, each API call counts as a transaction.

For multi-point ElevationPREVIEW requests, each API call counts as two transactions.

For Route Matrix, one transaction is counted for every cell in the matrix. If you provided 5 origins and 10 destinations, that would be counted as 50 transactions.

For Spatial Operations Geofencing, one transaction is created using increments of five Geofencing API calls.

For Batch Search calls, each individual query in the batch counts as a transaction. For Batch Route calls, each individual route calculation query in the batch counts as a transaction.


  • As a specific example, let’s say that you consume the following quantities in a certain monthly billing period:

    • 300,000 transactions of Vector Map Tiles
    • 100,000 transactions of Raster Map
    • 50,000 transactions of Traffic Service
    • 20,000 transactions of Search Service

    In this billing period, you get 275,000 free transactions (250,000 for Maps and 25,000 for other services). Your total billable transactions will be:

    (400,000 total maps transactions – 250,000 free maps transactions) + (70,000 total other transactions – 25,000 free other transactions) = 195,000 transactions

    Your total bill for this monthly billing period will be:

    $-/1,000 transactions * 195,000 transactions = $-

    For additional simulations, please use our pricing calculator.

  • The included free quantity may not apply to subscriptions associated with Azure credit offers, and your account may be suspended if the spending limit is turned on. Learn more about the Azure spending limit and how to remove it.

  • All APIs in the S1 tier are charged at a flat rate of $- per 1,000 transactions.

  • Yes. You can change the configuration of an Azure Maps account at any time. For instructions on how to make the changes in the Azure portal, please see our documentation.

  • Yes, you can have multiple Azure Maps accounts within your Azure Maps subscription. You can configure each account differently (S0 or S1), depending on what your consumption needs may be.


Estimate your monthly costs for Azure services

Review Azure pricing frequently asked questions

Learn more about Azure Maps

Review technical tutorials, videos and more resources

Added to estimate. Press 'v' to view on calculator

Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.

Get free cloud services and $200 in credit to explore Azure for 30 days.