Merge pull request #252614 from stevemunk/temp-banner-understanding-azure-maps-transactions-

Data service deprecation: about-azure-maps, qps-rate-limits, understanding-transactions

Author: prmerger-automator[bot]

articles/azure-maps/about-azure-maps.md

@@ -51,9 +51,15 @@ Use the Azure Maps Android SDK to create mobile mapping applications.
 
 Azure Maps consists of the following services that can provide geographic context to your Azure applications.
 
-### Data service
+### Data registry service
 
-Data is imperative for maps. Use the Data service to upload and store geospatial data for use with spatial operations or image composition.  By bringing customer data closer to the Azure Maps service, you reduce latency and increase productivity. For more information on this service, see [Data service].
+Data is imperative for maps. Use the Data registry service to access geospatial data, used with spatial operations or image composition, previously uploaded to your [Azure Storage].  By bringing customer data closer to the Azure Maps service, you reduce latency and increase productivity. For more information on this service, see [Data registry service].
+
+> [!NOTE]
+>
+> **Azure Maps Data service retirement**
+>
+> 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].
 
 ### Geolocation service
 
@@ -216,12 +222,17 @@ Stay up to date on Azure Maps:
 [Azure Maps blog]
 
 <!---------   learn.microsoft.com links     --------------->
+[Azure Storage]: ../storage/common/storage-introduction.md
 [Get started with Azure Maps Power BI visual]: power-bi-visual-get-started.md
 [How to use the Get Map Attribution API]: how-to-show-attribution.md
 [Quickstart: Create a web app]: quick-demo-map-app.md
 [What is Azure Maps Creator?]: about-creator.md
+[v1]: /rest/api/maps/data
+[v2]: /rest/api/maps/data-v2
+[Data Registry service]: /rest/api/maps/data-registry
+[How to create data registry]: how-to-create-data-registries.md
 <!---------   REST API Links     --------------->
-[Data service]: /rest/api/maps/data-v2
+[Data registry service]: /rest/api/maps/data-registry
 [Geolocation service]: /rest/api/maps/geolocation
 [Get Map Tile]: /rest/api/maps/render-v2/get-map-tile
 [Get Weather along route API]: /rest/api/maps/weather/getweatheralongroute

articles/azure-maps/azure-maps-qps-rate-limits.md

@@ -27,7 +27,8 @@ The following list shows the QPS usage limits for each Azure Maps service by Pri
 | Copyright service | 10 | 10 | 10 |
 | Creator - Alias, TilesetDetails | 10 | Not Available | Not Available |
 | Creator - Conversion, Dataset, Feature State, WFS | 50 | Not Available | Not Available |
-| Data service | 50 | 50 |  Not Available  |
+| Data service (Deprecated<sup>1</sup>) | 50 | 50 |  Not Available  |
+| Data registry service | 50 | 50 |  Not Available  |
 | Geolocation service | 50 | 50 | 50 |
 | Render service - Traffic tiles and Static maps | 50 | 50 | 50 |
 | Render service - Road tiles | 500 | 500 | 50 |
@@ -43,7 +44,13 @@ The following list shows the QPS usage limits for each Azure Maps service by Pri
 | Traffic service | 50 | 50 | 50 |
 | Weather service | 50 | 50 | 50 |
 
+<sup>1</sup> 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].
+
 When QPS limits are reached, an HTTP 429 error is returned. If you're using the Gen 2 or Gen 1 S1 pricing tiers, you can create an Azure Maps *Technical* Support Request in the [Azure portal] to increase a specific QPS limit if needed. QPS limits for the Gen 1 S0 pricing tier can't be increased.
 
 [Azure portal]: https://portal.azure.com/
 [Manage the pricing tier of your Azure Maps account]: how-to-manage-pricing-tier.md
+[v1]: /rest/api/maps/data
+[v2]: /rest/api/maps/data-v2
+[Data Registry service]: /rest/api/maps/data-registry
+[How to create data registry]: how-to-create-data-registries.md

articles/azure-maps/tutorial-ev-routing.md

@@ -33,7 +33,7 @@ In this tutorial, you will:
 
 * An [Azure Maps account]
 * A [subscription key]
-- An [Azure storage account]
+* An [Azure storage account]
 
 > [!NOTE]
 > For more information on authentication in Azure Maps, see [manage authentication in Azure Maps].
@@ -168,6 +168,7 @@ for loc in range(len(searchPolyResponse["results"])):
 
 It's helpful to visualize the charging stations and the boundary for the maximum reachable range of the electric vehicle on a map. Follow the steps outlined in the [How to create data registry] article to upload the boundary data and charging stations data as geojson objects to your [Azure storage account] then register them in your Azure Maps account. Make sure to make a note of the unique identifier (`udid`) value, you will need it. The `udid` is is how you reference the geojson objects you uploaded into your Azure storage account from your source code.
 
+<!---------------------------------------------------------------------------
 To upload the boundary and charging point data to Azure Maps Data service, run the following two cells:
 
 ```python
@@ -229,6 +230,7 @@ while True:
         time.sleep(0.2)
 poiUdid = getPoiUdid["udid"]
 ```
+------------------------------------------------------------>
 
 ## Render the charging stations and reachable range on a map
 
@@ -405,14 +407,14 @@ To learn more about Azure Notebooks, see
 [Azure Maps Jupyter Notebook repository]: https://github.com/Azure-Samples/Azure-Maps-Jupyter-Notebook
 [Azure Maps REST APIs]: /rest/api/maps
 [Azure Notebooks]: https://notebooks.azure.com
-[Data Upload API]: /rest/api/maps/data-v2/upload
-[Data Upload]: /rest/api/maps/data-v2/upload
+[Azure storage account]: /azure/storage/common/storage-account-create?tabs=azure-portal
 [Get Map Image API]: /rest/api/maps/render-v2/get-map-static-image
 [Get Map Image service]: /rest/api/maps/render-v2/get-map-static-image
 [Get Route Directions API]: /rest/api/maps/route/getroutedirections
 [Get Route Directions]: /rest/api/maps/route/getroutedirections
 [Get Route Range API]: /rest/api/maps/route/getrouterange
 [Get Route Range]: /rest/api/maps/route/getrouterange
+[How to create data registry]: how-to-create-data-registries.md
 [Jupyter Notebook document file]: https://github.com/Azure-Samples/Azure-Maps-Jupyter-Notebook/blob/master/AzureMapsJupyterSamples/Tutorials/EV%20Routing%20and%20Reachable%20Range/EVrouting.ipynb
 [manage authentication in Azure Maps]: how-to-manage-authentication.md
 [Matrix Routing API]: /rest/api/maps/route/postroutematrix

articles/azure-maps/understanding-azure-maps-transactions.md

@@ -4,7 +4,7 @@ titleSuffix:  Microsoft Azure Maps
 description: Learn about Microsoft Azure Maps Transactions
 author: eriklindeman
 ms.author: eriklind
-ms.date: 06/23/2022
+ms.date: 09/22/2023
 ms.topic: reference
 ms.service: azure-maps
 services: azure-maps
@@ -26,7 +26,8 @@ The following table summarizes the Azure Maps services that generate transaction
 
 | Azure Maps Service | Billable | Transaction Calculation | Meter |
 |--------------------|----------|-------------------------|-------|
-| [Data v1]<br>[Data v2]<br>[Data registry] | Yes, except for `MapDataStorageService.GetDataStatus` and `MapDataStorageService.GetUserData`, which are nonbillable| One request = 1 transaction| <ul><li>Location Insights Data (Gen2 pricing)</li></ul>|
+| Data service (Deprecated<sup>1</sup>) | Yes, except for `MapDataStorageService.GetDataStatus` and `MapDataStorageService.GetUserData`, which are nonbillable| One request = 1 transaction| <ul><li>Location Insights Data (Gen2 pricing)</li></ul>|
+| [Data registry]    | Yes      | One request = 1 transaction| <ul><li>Location Insights Data (Gen2 pricing)</li></ul>|
 | [Geolocation]| Yes| One request = 1 transaction| <ul><li>Location Insights Geolocation (Gen2 pricing)</li><li>Standard S1 Geolocation Transactions (Gen1 S1 pricing)</li><li>Standard Geolocation Transactions (Gen1 S0 pricing)</li></ul>|
 | [Render] | Yes, except for Terra maps (`MapTile.GetTerraTile` and `layer=terra`) which are nonbillable.|<ul><li>15 tiles = 1 transaction</li><li>One request for Get Copyright = 1 transaction</li><li>One request for Get Map Attribution = 1 transaction</li><li>One request for Get Static Map = 1 transaction</li><li>One request for Get Map Tileset = 1 transaction</li></ul> <br> For Creator related usage, see the [Creator table]. |<ul><li>Maps Base Map Tiles (Gen2 pricing)</li><li>Maps Imagery Tiles (Gen2 pricing)</li><li>Maps Static Map Images (Gen2 pricing)</li><li>Maps Traffic Tiles (Gen2 pricing)</li><li>Maps Weather Tiles (Gen2 pricing)</li><li>Standard Hybrid Aerial Imagery Transactions (Gen1 S0 pricing)</li><li>Standard Aerial Imagery Transactions (Gen1 S0 pricing)</li><li>Standard S1 Aerial Imagery Transactions (Gen1 S1 pricing)</li><li>Standard S1 Hybrid Aerial Imagery Transactions (Gen1 S1 pricing)</li><li>Standard S1 Rendering Transactions (Gen1 S1 pricing)</li><li>Standard S1 Tile Transactions (Gen1 S1 pricing)</li><li>Standard S1 Weather Tile Transactions (Gen1 S1 pricing)</li><li>Standard Tile Transactions (Gen1 S0 pricing)</li><li>Standard Weather Tile Transactions (Gen1 S0 pricing)</li><li>Maps Copyright (Gen2 pricing, Gen1 S0 pricing and Gen1 S1 pricing)</li></ul>|
 | [Route] | Yes | One request = 1 transaction<br><ul><li>If using the Route Matrix, each cell in the Route Matrix request generates a billable Route transaction.</li><li>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 has **-Batch** appended to the API name of your Azure portal metrics report.</li></ul> | <ul><li>Location Insights Routing (Gen2 pricing)</li><li>Standard S1 Routing Transactions (Gen1 S1 pricing)</li><li>Standard Services API Transactions (Gen1 S0 pricing)</li></ul> |
@@ -36,6 +37,8 @@ The following table summarizes the Azure Maps services that generate transaction
 | [Traffic] | Yes | One request = 1 transaction (except tiles)<br>15 tiles = 1 transaction | <ul><li>Location Insights Traffic (Gen2 pricing)</li><li>Standard S1 Traffic Transactions (Gen1 S1 pricing)</li><li>Standard Geolocation Transactions (Gen1 S0 pricing)</li><li>Maps Traffic Tiles (Gen2 pricing)</li><li>Standard S1 Tile Transactions (Gen1 S1 pricing)</li><li>Standard Tile Transactions (Gen1 S0 pricing)</li></ul> |
 | [Weather] | Yes | One request = 1 transaction | <ul><li>Location Insights Weather (Gen2 pricing)</li><li>Standard S1 Weather Transactions (Gen1 S1 pricing)</li><li>Standard Weather Transactions (Gen1 S0 pricing)</li></ul> |
 
+<sup>1</sup> 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].
+
 <!-- In Bing Maps, any time a synchronous Truck Routing request is made, three transactions are counted. Does this apply also to Azure Maps?-->
 
 ## Azure Maps Creator
@@ -80,8 +83,10 @@ The following table summarizes the Azure Maps services that generate transaction
 [Conversion]: /rest/api/maps/v2/conversion
 [Creator table]: #azure-maps-creator
 [Data registry]: /rest/api/maps/data-registry
-[Data v1]: /rest/api/maps/data
-[Data v2]: /rest/api/maps/data-v2
+[v1]: /rest/api/maps/data
+[v2]: /rest/api/maps/data-v2
+[Data Registry service]: /rest/api/maps/data-registry
+[How to create data registry]: how-to-create-data-registries.md
 [Dataset]: /rest/api/maps/v2/dataset
 [Feature State]: /rest/api/maps/v2/feature-state
 [Geolocation]: /rest/api/maps/geolocation