Merge pull request #250977 from stevemunk/tutorial-ev-routing-depricated

tutorial-ev-routing: Replace data upload instructions with data registry instructions.

Author: prmerger-automator[bot]

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

@@ -33,6 +33,7 @@ In this tutorial, you will:
 
 * An [Azure Maps account]
 * A [subscription key]
+- An [Azure storage account]
 
 > [!NOTE]
 > For more information on authentication in Azure Maps, see [manage authentication in Azure Maps].
@@ -163,9 +164,9 @@ for loc in range(len(searchPolyResponse["results"])):
                 reachableLocations.append(location)
 ```
 
-## Upload the reachable range and charging points to Azure Maps Data service
+## Upload the reachable range and charging points
 
-It's helpful to visualize the charging stations and the boundary for the maximum reachable range of the electric vehicle on a map. To do so, upload the boundary data and charging stations data as geojson objects to Azure Maps Data service. Use the [Data Upload API].
+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:
 
@@ -231,7 +232,7 @@ poiUdid = getPoiUdid["udid"]
 
 ## Render the charging stations and reachable range on a map
 
-After you've uploaded the data to the data service, call the Azure Maps [Get Map Image service]. This service is used to render the charging points and maximum reachable boundary on the static map image by running the following script:
+After you've uploaded the data to the Azure storage account, call the Azure Maps [Get Map Image service]. This service is used to render the charging points and maximum reachable boundary on the static map image by running the following script:
 
 ```python
 # Get boundaries for the bounding box.
@@ -327,7 +328,7 @@ routeData = {
 
 ## Visualize the route
 
-To help visualize the route, you first upload the route data as a geojson object to Azure Maps Data service. To do so, use the Azure Maps [Data Upload API]. Then, call the rendering service, [Get Map Image API]), to render the route on the map, and visualize it.
+To help visualize the route, follow the steps outlined in the [How to create data registry] article to upload the route data as a geojson object to your [Azure storage account] then register it 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. Then, call the rendering service, [Get Map Image API], to render the route on the map, and visualize it.
 
 To get an image for the rendered route on the map, run the following script:
 
@@ -384,7 +385,6 @@ To explore the Azure Maps APIs that are used in this tutorial, see:
 
 * [Get Route Range]
 * [Post Search Inside Geometry]
-* [Data Upload]
 * [Render - Get Map Image]
 * [Post Route Matrix]
 * [Get Route Directions]
@@ -405,8 +405,8 @@ 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
+[How to create data registry]: how-to-create-data-registries.md
 [Get Map Image API]: /rest/api/maps/render/getmapimage
 [Get Map Image service]: /rest/api/maps/render/getmapimage
 [Get Route Directions API]: /rest/api/maps/route/getroutedirections