Merge pull request #2 from cynthn/build-prep-service-groups

Build prep service groups

Author: rthorn17

articles/azure-app-configuration/howto-variant-feature-flags.md

@@ -74,3 +74,4 @@ In this tutorial, you create a web app named _Quote of the Day_. When the app is
 
 2. Continue to the following instructions to use the variant feature flag in your application for the language or platform you're using.
     * [ASP.NET Core](./howto-variant-feature-flags-aspnet-core.md)
+    * [Python](./howto-variant-feature-flags-python.md)

articles/azure-maps/itinerary-optimization-service.md

@@ -78,31 +78,47 @@ Matrix size = 5 origins x 5 destinations = 25
 The Route Matrix POST request:
 
 ```html
-https://atlas.microsoft.com/route/matrix/json?api-version=1.0&routeType=shortest
+https://atlas.microsoft.com/route/matrix?api-version=2025-01-01&routeType=shortest&subscription-key={Your-Azure-Maps-Subscription-key}
 ```
 
 ```json
 {
-  "origins": { 
-    "type": "MultiPoint", 
-    "coordinates": [ 
-      [4.85106, 52.36006], //restaurant or depot 
-      [4.85056, 52.36187], //delivery location 1 
-      [4.85003, 52.36241], //delivery location 2 
-      [4.42937, 52.50931], //delivery location 3 
-      [4.42940, 52.50843]  //delivery location 4 
-    ] 
-  }, 
-  "destinations": { 
-    "type": "MultiPoint", 
-      [4.85106, 52.36006], //restaurant or depot 
-      [4.85056, 52.36187], //delivery location 1 
-      [4.85003, 52.36241], //delivery location 2 
-      [4.42937, 52.50931], //delivery location 3 
-      [4.42940, 52.50843]  //delivery location 4 
-    ] 
-  } 
-} 
+  "type": "FeatureCollection",
+  "features": [
+    {
+      "type": "Feature",
+      "geometry": {
+        "type": "MultiPoint",
+        "coordinates": [
+            [4.85106, 52.36006], //restaurant or depot 
+            [4.85056, 52.36187], //delivery location 1 
+            [4.85003, 52.36241], //delivery location 2 
+            [4.42937, 52.50931], //delivery location 3 
+            [4.42940, 52.50843]  //delivery location 4 
+        ]
+      },
+      "properties": {
+        "pointType": "origins"
+      }
+    },
+    {
+      "type": "Feature",
+      "geometry": {
+        "type": "MultiPoint",
+        "coordinates": [
+            [4.85106, 52.36006], //restaurant or depot 
+            [4.85056, 52.36187], //delivery location 1 
+            [4.85003, 52.36241], //delivery location 2 
+            [4.42937, 52.50931], //delivery location 3 
+            [4.42940, 52.50843]  //delivery location 4 
+        ]
+      },
+      "properties": {
+        "pointType": "destinations"
+      }
+    }
+  ]
+}
 ```
 
 The Route Matrix response returns a 5x5 multi-dimensional array where each row represents the origins and columns represent the destinations. Use the field `travelTimeInSeconds` to get the time cost for each location pair. The time unit should be consistent across the solution. Once the preprocessing stage is complete, the order, depot, fleet info and the cost matrix, are sent over and imported to the cuOpt Server via API calls.

articles/azure-maps/migrate-calculate-route.md

@@ -69,42 +69,44 @@ http://dev.virtualearth.net/REST/V1/Routes/driving?wp.0=47.610173,-122.204171&wp
 Azure Maps _Route Directions_ API POST request:
 
 ``` http
-https://atlas.microsoft.com/route/directions?api-version=2023-10-01-preview&subscription-key={Your-Azure-Maps-Subscription-key} 
+https://atlas.microsoft.com/route/directions?api-version=2025-01-01&subscription-key={Your-Azure-Maps-Subscription-key} 
 ```
 
 Included in the body of the request:
 
 ```json
-{ 
-  "type": "FeatureCollection",` 
-  "features": [ 
-    { 
-      "type": "Feature", 
-      "geometry": { 
-        "coordinates": [ 
-         -122.204171,47.610173 
-        ], 
-        "type": "Point" 
-      }, 
-      "properties": { 
-        "pointIndex": 0, 
-        "pointType": "waypoint" 
-      } 
-    }, 
-    { 
-      "type": "Feature", 
-      "geometry": { 
-        "coordinates": [ 
-          -122.204171,47.612440 
-        ], 
-        "type": "Point" 
-      }, 
-      "properties": { 
-        "pointIndex": 1, 
-        "pointType": "waypoint" 
-      } 
-    } 
-  ] 
+{
+  "type": "FeatureCollection",
+  "features": [
+    {
+      "type": "Feature",
+      "geometry": {
+        "coordinates": [
+          -122.204171,
+          47.610173
+        ],
+        "type": "Point"
+      },
+      "properties": {
+        "pointIndex": 0,
+        "pointType": "waypoint"
+      }
+    },
+    {
+      "type": "Feature",
+      "geometry": {
+        "coordinates": [
+          -122.204171,
+          47.612440
+        ],
+        "type": "Point"
+      },
+      "properties": {
+        "pointIndex": 1,
+        "pointType": "Waypoint"
+      }
+    }
+  ]
 }
 ```
 

articles/azure-maps/migrate-calculate-truck-route.md

@@ -94,7 +94,7 @@ Included in the body of the request:
 Azure Maps _Route Directions_ API POST request:
 
 ``` http
-https://atlas.microsoft.com/route/directions?api-version=2023-10-01-preview&subscription-key={Your-Azure-Maps-Subscription-key} 
+https://atlas.microsoft.com/route/directions?api-version=2025-01-01&subscription-key={Your-Azure-Maps-Subscription-key} 
 ```
 
 Included in the body of the request:

articles/azure-maps/migrate-help-using-copilot.md

@@ -208,7 +208,7 @@ Step 6. Create and add a SymbolLayer to the map.
 
 Step 7. Create and add a LineLayer to the map.
 
-Step 8. Utilize the Route POST API: <https://atlas.microsoft.com/route/directions?api-version=2023-10-01-preview&subscription-key=${subscriptionKey}> to find the route between the start and end points. Add the GeoJSON response to the DataSource and adjust the map's camera based on the bounding box of the response.
+Step 8. Utilize the Route POST API: <https://atlas.microsoft.com/route/directions?api-version=2025-01-01&subscription-key=${subscriptionKey}> to find the route between the start and end points. Add the GeoJSON response to the DataSource and adjust the map's camera based on the bounding box of the response.
 
 Example request body:
 
@@ -335,7 +335,7 @@ GitHub Copilot can create the following code snippet to provide an interface for
  
       function getRoute(startCoordinates, endCoordinates) {
         fetch(
-          `https://atlas.microsoft.com/route/directions?api-version=2023-10-01-preview&subscription-key=${subscriptionKey}`,
+          `https://atlas.microsoft.com/route/directions?api-version=2025-01-01&subscription-key=${subscriptionKey}`,
           {
             method: "POST",
             headers: {

articles/azure-maps/rest-api-azure-maps.md

@@ -75,4 +75,4 @@ Prerelease version of an Azure Maps service. Preview releases contain new functi
 
 <!--- 2024-07-01-preview is the latest preview release of the Route service,
       currently the only Azure Maps service in Preview -------------------------->
-[Route-2024-07-01-preview]: /rest/api/maps/route?view=rest-maps-2024-07-01-preview
+[Route-2024-07-01-preview]: /rest/api/maps/route?view=rest-maps-2024-07-01-preview

articles/azure-maps/supported-languages.md

@@ -92,9 +92,9 @@ Azure Maps have been localized in variety languages across its services. The fol
 <sup>1</sup> Neutral Ground Truth (Local) - Official languages for all regions in local scripts if available<br>
 <sup>2</sup> Neutral Ground Truth (Latin) - Latin exonyms are used if available
 
-## Routing v2 services (preview) supported languages
+## Routing services supported languages
 
-Azure Maps have been localized in variety languages across its services. The following table provides the supported language codes for the routing v2 services. The routing column in the following table includes routes for driving and walking.
+Azure Maps have been localized in variety languages across its services. The following table provides the supported language codes for the latest version of the Azure Maps [Route] service. The routing column in the following table includes routes for driving and walking.
 
 | Culture        | Language                                   | Routing | Truck Routing |
 |----------------|--------------------------------------------|:-------:|:-------------:|
@@ -266,3 +266,5 @@ The following table provides supported views.
 | YE      | Yemen (Arabic View)                                         |   ✓  |        |
 | Auto    | Automatically detect based on request                       |   ✓  |    ✓   |
 | Unified | Unified View (Others)                                       |   ✓  |    ✓   |
+
+[Route]:  /rest/api/maps/route

articles/azure-maps/tutorial-snap-to-road.md

@@ -142,7 +142,7 @@ The code in this notebook cell reads raw GPS data from the data file in lakehous
     import json
 
     az_maps_subkey = ""
-    az_maps_snaproads_url = "https://atlas.microsoft.com/route/snapToRoads?api-version=2024-07-01-preview&subscription-key=" + az_maps_subkey
+    az_maps_snaproads_url = "https://atlas.microsoft.com/route/snapToRoads?api-version=2025-01-01&subscription-key=" + az_maps_subkey
 
     # Function to process snap to road for each given trip
     def process_route(df, outputFilePath):

articles/azure-netapp-files/application-volume-group-disaster-recovery.md

@@ -1,11 +1,11 @@
 ---
-title: Add volumes for an SAP HANA system as a DR system using Azure NetApp Files cross-region replication  | Microsoft Docs
+title: Add volumes for an SAP HANA system as a DR system using Azure NetApp Files cross-region replication
 description: Describes using an application volume group to add volumes for an SAP HANA system as a disaster recovery (DR) system.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 04/22/2025
+ms.date: 05/06/2025
 ms.author: anfdocs
 ---
 # Add volumes for an SAP HANA system as a DR system using cross-region replication
@@ -26,7 +26,7 @@ The following diagram illustrates cross-region replication between the source an
 > When you use an HA deployment with HSR at the primary side, you can choose to replicate not only the primary HANA system as described in this section, but also the HANA secondary system using cross-region replication. To automatically adapt the naming convention, you select both the **HSR secondary** and **Disaster recovery destination** options in the Create a Volume Group screen. The prefix then changes to `DR2-`. 
 
 > [!IMPORTANT]
-> * Recovering the HANA database at the destination region requires that you use application-consistent storage snapshots for your HANA backup. You can create such snapshots by using data-protection solutions such as SnapCenter and the [Azure Application Consistent Snapshot tool](azacsnap-introduction.md) (AzAcSnap).
+> * Recovering the HANA database at the destination region requires that you use application-consistent storage snapshots for your HANA backup. You can create such snapshots by using data-protection solutions including [SnapCenter](https://docs.netapp.com/us-en/snapcenter/protect-azure/protect-applications-azure-netapp-files.html), [Azure Application Consistent Snapshot tool](azacsnap-introduction.md) (AzAcSnap), or other [validated partner solutions](../storage/solution-integration/validated-partners/backup-archive-disaster-recovery/partner-overview.md).
 > * You need to replicate at least the data volume and the log-backup volume. 
 > * You can optionally replicate the data-backup volume and the shared volume. 
 > * You should *never* replicate the log volume. The application volume group will create the log volume as a standard volume.

articles/azure-netapp-files/application-volume-group-manage-volumes-oracle.md

@@ -1,13 +1,12 @@
 ---
-title: Manage volumes in Azure NetApp Files application volume group for Oracle | Microsoft Docs
+title: Manage volumes in Azure NetApp Files application volume group for Oracle
 description: Describes how to manage a volume from its application volume group for Oracle, including resizing, deleting, or changing throughput for the volume. 
 services: azure-netapp-files
-documentationcenter: ''
 author: b-hchen
 ms.service: azure-netapp-files
 ms.workload: storage
 ms.topic: how-to
-ms.date: 04/17/2025
+ms.date: 05/06/2025
 ms.author: anfdocs
 ---
 # Manage volumes in an application volume group for Oracle
@@ -34,7 +33,7 @@ You can manage a volume from its volume group. You can resize, delete, or change
         > Changing the protocol type involves reconfiguration at the Linux host. When using dNFS, it's not recommended to mix volumes using NFSv3 and NFSv4.1.  
 
         > [!NOTE] 
-        > Using Azure NetApp Files built-in automated snapshots doesn't create database consistent backups. Instead, use data protection software such as [SnapCenter](https://docs.netapp.com/us-en/snapcenter/protect-azure/protect-applications-azure-netapp-files.html) and [AzAcSnap](azacsnap-introduction.md) that supports snapshot-based data protection for Oracle. 
+        > Using Azure NetApp Files built-in automated snapshots doesn't create database consistent backups. Instead, use data protection software such as [SnapCenter](https://docs.netapp.com/us-en/snapcenter/protect-azure/protect-applications-azure-netapp-files.html), [AzAcSnap](azacsnap-introduction.md), or other [validated partner solutions](../storage/solution-integration/validated-partners/backup-archive-disaster-recovery/partner-overview.md) that supports snapshot-based data protection for Oracle. 
 
     * **Change Throughput**   
         You can adapt the throughput of the volume.