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 nonbillable 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 show up in your Cost Analysis report within the Azure portal.
Note
Azure Maps Gen1 pricing tier retirement
Gen1 pricing tier is now deprecated and will be retired on 9/15/26. Gen2 pricing tier replaces Gen1 (both S0 and S1) pricing tier. If your Azure Maps account has Gen1 pricing tier selected, you can switch to Gen2 pricing tier before it’s retired, otherwise it will automatically be updated. For more information, see Manage the pricing tier of your Azure Maps account.
Azure Maps Transaction information by service
The following table summarizes the Azure Maps services that generate transactions, billable and nonbillable, along with any notable aspects that are helpful to understand in how the number of transactions are calculated.
Note
For Azure Maps pricing information and free offering details, see Azure Maps Pricing.
Azure Maps Service | Billable | Transaction Calculation | Meter |
---|---|---|---|
Data service (Deprecated1) | Yes, except for MapDataStorageService.GetDataStatus and MapDataStorageService.GetUserData , which are nonbillable |
One request = 1 transaction |
|
Data registry | Yes | One request = 1 transaction |
|
Geolocation | Yes | One request = 1 transaction |
|
Render | Yes, except Get Copyright API, Get Attribution API and Terra maps (MapTile.GetTerraTile and layer=terra ) which are nonbillable. |
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 nonbillable. |
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 |
|
1 The Azure Maps Data service (both v1 and v2) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps Data Registry service by 9/16/24. For more information, see How to create data registry.
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 | Yes, only with GetMapTile with Creator Tileset ID and GetStaticTile .For everything else for Render, see Render 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) |
Understand billing transactions
Azure Maps doesn't count billing transactions for:
- 5xx HTTP Status Codes
- 401 (Unauthorized)
- 403 (Forbidden)
- 408 (Timeout)
- 429 (TooManyRequests)
- CORS preflight requests
For more information on billing transactions and other Azure Maps pricing information, see Azure Maps pricing.
Next steps
Feedback
https://aka.ms/ContentUserFeedback.
Kommer snart: I hele 2024 udfaser vi GitHub-problemer som feedbackmekanisme for indhold og erstatter det med et nyt feedbacksystem. Du kan få flere oplysninger under:Indsend og få vist feedback om