Understanding Azure Maps Transactions

When you use Azure Maps Services, the API requests you make generate transactions. Your transaction usage is available for review in your Azure portal Metrics report. For more information, see View Azure Maps API usage metrics. These transactions can be either billable or non-billable usage, depending on the service and the feature. It’s important to understand which usage generates a billable transaction and how it’s calculated so you can plan and budget for the costs associated with using Azure Maps. Billable transactions will show up in your Cost Analysis report within the Azure portal.

The following table summarizes the Azure Maps services that generate transactions, billable and non-billable, along with any notable aspects that are helpful to understand in how the number of transactions are calculated.

Azure Maps Transaction information by service

Azure Maps Service	Billable	Transaction Calculation	Meter
Data v1 Data v2	Yes, except for MapDataStorageService.GetDataStatus and MapDataStorageService.GetUserData, which are non-billable	One request = 1 transaction	Location Insights Data (Gen2 pricing)
Elevation (DEM)	Yes	One request = 2 transactions If requesting elevation for a single point then one request = 1 transaction	Location Insights Elevation (Gen2 pricing) Standard S1 Elevation Service Transactions (Gen1 S1 pricing)
Geolocation	Yes	One request = 1 transaction	Location Insights Geolocation (Gen2 pricing) Standard S1 Geolocation Transactions (Gen1 S1 pricing) Standard Geolocation Transactions (Gen1 S0 pricing)
Render v1 Render v2	Yes, except for Terra maps (MapTile.GetTerraTile and layer=terra) which are non-billable.	15 tiles = 1 transaction, except microsoft.dem is one tile = 50 transactions One request for Get Copyright = 1 transaction One request for Get Map Attribution = 1 transaction One request for Get Static Map = 1 transaction One request for Get Map Tileset = 1 transaction For Creator related usage, see the Creator table.	Maps Base Map Tiles (Gen2 pricing) Maps Imagery Tiles (Gen2 pricing) Maps Static Map Images (Gen2 pricing) Maps Traffic Tiles (Gen2 pricing) Maps Weather Tiles (Gen2 pricing) Standard Hybrid Aerial Imagery Transactions (Gen1 S0 pricing) Standard Aerial Imagery Transactions (Gen1 S0 pricing) Standard S1 Aerial Imagery Transactions (Gen1 S1 pricing) Standard S1 Hybrid Aerial Imagery Transactions (Gen1 S1 pricing) Standard S1 Rendering Transactions (Gen1 S1 pricing) Standard S1 Tile Transactions (Gen1 S1 pricing) Standard S1 Weather Tile Transactions (Gen1 S1 pricing) Standard Tile Transactions (Gen1 S0 pricing) Standard Weather Tile Transactions (Gen1 S0 pricing) Maps Copyright (Gen2 pricing, Gen1 S0 pricing and Gen1 S1 pricing)
Route	Yes	One request = 1 transaction If using the Route Matrix, each cell in the Route Matrix request generates a billable Route transaction. If using Batch Directions, each origin/destination coordinate pair in the Batch request call generates a billable Route transaction. Note, the billable Route transaction usage results generated by the batch request will have -Batch appended to the API name of your Azure portal metrics report.	Location Insights Routing (Gen2 pricing) Standard S1 Routing Transactions (Gen1 S1 pricing) Standard Services API Transactions (Gen1 S0 pricing)
Search v1 Search v2	Yes	One request = 1 transaction. If using Batch Search, each location in the Batch request generates a billable Search transaction. Note, the billable Search transaction usage results generated by the batch request will have -Batch appended to the API name of your Azure portal metrics report.	Location Insights Search Standard S1 Search Transactions (Gen1 S1 pricing) Standard Services API Transactions (Gen1 S0 pricing)
Spatial	Yes, except for Spatial.GetBoundingBox, Spatial.PostBoundingBox and Spatial.PostPointInPolygonBatch, which are non-billable.	One request = 1 transaction. If using Geofence, five requests = 1 transaction	Location Insights Spatial Calculations (Gen2 pricing) Standard S1 Spatial Transactions (Gen1 S1 pricing)
Timezone	Yes	One request = 1 transaction	Location Insights Timezone (Gen2 pricing) Standard S1 Time Zones Transactions (Gen1 S1 pricing) Standard Time Zones Transactions (Gen1 S0 pricing)
Traffic	Yes	One request = 1 transaction (except tiles) 15 tiles = 1 transaction	Location Insights Traffic (Gen2 pricing) Standard S1 Traffic Transactions (Gen1 S1 pricing) Standard Geolocation Transactions (Gen1 S0 pricing) Maps Traffic Tiles (Gen2 pricing) Standard S1 Tile Transactions (Gen1 S1 pricing) Standard Tile Transactions (Gen1 S0 pricing)
Weather	Yes	One request = 1 transaction	Location Insights Weather (Gen2 pricing) Standard S1 Weather Transactions (Gen1 S1 pricing) Standard Weather Transactions (Gen1 S0 pricing)

Azure Maps Creator

Azure Maps Creator	Billable	Transaction Calculation	Meter
Alias	No	One request = 1 transaction	Not applicable
Conversion	Part of a provisioned Creator resource and not transactions based.	Not transaction-based	Map Provisioning (Gen2 pricing)
Dataset	Part of a provisioned Creator resource and not transactions based.	Not transaction-based	Map Provisioning (Gen2 pricing)
Feature State	Yes, except for FeatureState.CreateStateset, FeatureState.DeleteStateset, FeatureState.GetStateset, FeatureState.ListStatesets, FeatureState.UpdateStatesets	One request = 1 transaction	Azure Maps Creator Feature State (Gen2 pricing)
Render v2	Yes, only with GetMapTile with Creator Tileset ID and GetStaticTile. For everything else for Render v2, see Render v2 section in the above table.	One request = 1 transaction One tile = 1 transaction	Azure Maps Creator Map Render (Gen2 pricing)
Tileset	Part of a provisioned Creator resource and not transactions based.	Not transaction-based	Map Provisioning    (Gen2 pricing)
WFS	Yes	One request = 1 transaction	Azure Maps Creator Web Feature (WFS) (Gen2 pricing)

Next steps

Azure Maps pricing

Pricing calculator

Manage the pricing tier of your Azure Maps account

View Azure Maps API usage metrics