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 |
|
Elevation (DEM) | Yes | One request = 2 transactions
|
|
Geolocation | Yes | One request = 1 transaction |
|
Render v1 Render v2 |
Yes, except for Terra maps (MapTile.GetTerraTile and layer=terra) which are non-billable. |
For Creator related usage, see the Creator table. |
|
Route | Yes | One request = 1 transaction
|
|
Search v1 Search v2 |
Yes | One request = 1 transaction.
|
|
Spatial | Yes, except for Spatial.GetBoundingBox , Spatial.PostBoundingBox and Spatial.PostPointInPolygonBatch , which are non-billable. |
One request = 1 transaction.
|
|
Timezone | Yes | One request = 1 transaction |
|
Traffic | Yes | One request = 1 transaction (except tiles) 15 tiles = 1 transaction |
|
Weather | Yes | One request = 1 transaction |
|
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
Feedback
Submit and view feedback for