Merge branch 'release-build-container-apps' of https://github.com/MicrosoftDocs/azure-docs-pr into aca/env-ingress

Author: craigshoemaker

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/container-apps/azure-arc-overview.md

@@ -30,9 +30,9 @@ As you configure your cluster, you carry out these actions:
 
 - **A Container Apps connected environment**, which enables configuration common across apps but not related to cluster operations. Conceptually, it's deployed into the custom location resource, and app developers create apps into this environment.
 
-## Public preview limitations
+## Limitations
 
-The following public preview limitations apply to Azure Container Apps on Azure Arc enabled Kubernetes.
+The following limitations apply to Azure Container Apps on Azure Arc enabled Kubernetes.
 
 | Limitation | Details |
 |---|---|
@@ -43,6 +43,17 @@ The following public preview limitations apply to Azure Container Apps on Azure
 | Feature: Pull images from ACR with managed identity | Not available (depends on managed identities) |
 | Logs | Log Analytics must be configured with cluster extension; not per-application |
 
+The following features are supported:
+
+- Labels
+- Metrics
+- Easy auth
+- Log stream
+- Resilience
+- Custom domains
+- Revision Management
+- App container console
+
 > [!IMPORTANT]
 > If deploying onto **AKS on Azure Local** ensure that you have [setup HAProxy as your load balancer](/azure/aks/hybrid/configure-load-balancer)  before attempting to install the extension.
 
@@ -57,7 +68,7 @@ The following table describes the role of each revision created for you:
 | Pod | Description | Number of Instances | CPU | Memory | Type |
 |----|----|----|----|----|----|
 | `<extensionName>-k8se-activator` | Used as part of the scaling pipeline | 2 | 100 millicpu | 500 MB | ReplicaSet |
-| `<extensionName>-k8se-billing` | Billing record generation - Azure Container Apps on Azure Arc enabled Kubernetes is Free of Charge during preview | 3 | 100 millicpu | 100 MB | ReplicaSet | 
+| `<extensionName>-k8se-billing` | Billing record generation | 3 | 100 millicpu | 100 MB | ReplicaSet |
 | `<extensionName>-k8se-containerapp-controller` | The core operator pod that creates resources on the cluster and maintains the state of components. | 2 | 100 millicpu | 1 GB | ReplicaSet |
 | `<extensionName>-k8se-envoy` | A front-end proxy layer for all data-plane http requests. It routes the inbound traffic to the correct apps. | 3 | 1 Core | 1,536 MB | ReplicaSet |
 | `<extensionName>-k8se-envoy-controller` | Operator, which generates Envoy configuration | 2 | 200 millicpu | 500 MB | ReplicaSet |
@@ -75,7 +86,6 @@ The following table describes the role of each revision created for you:
 
 ## FAQ for Azure Container Apps on Azure Arc
 
-- [How much does it cost?](#how-much-does-it-cost)
 - [Which Container Apps features are supported?](#which-container-apps-features-are-supported)
 - [Are managed identities supported?](#are-managed-identities-supported)
 - [Are there any scaling limits?](#are-there-any-scaling-limits)
@@ -84,13 +94,9 @@ The following table describes the role of each revision created for you:
 - [Can the extension be installed on Windows nodes?](#can-the-extension-be-installed-on-windows-nodes)
 - [Can I deploy the Container Apps extension on an Arm64 based cluster?](#can-i-deploy-the-container-apps-extension-on-an-arm64-based-cluster)
 
-### How much does it cost?
-
-Azure Container Apps on Azure Arc-enabled Kubernetes is free during the public preview.
-
 ### Which Container Apps features are supported?
 
-During the preview period, certain Azure Container App features are being validated. When they're supported, their left navigation options in the Azure portal will be activated. Features that aren't yet supported remain grayed out.
+Check the portal for the most up to date list. Features not supported are grayed out in the portal.
 
 ### Are managed identities supported?
 

articles/cost-management-billing/dataset-schema/cost-usage-details-ea.md

@@ -1,13 +1,13 @@
 ---
 title: Enterprise Agreement cost and usage details file schema
 description: Learn about the data fields available in the Enterprise Agreement cost and usage details file.
-author: bandersmsft
+author: jojopm
 ms.reviewer: jojoh
 ms.service: cost-management-billing
 ms.subservice: common
 ms.topic: reference
 ms.date: 01/24/2025
-ms.author: banders
+ms.author: jojoh
 ---
 
 # Enterprise Agreement cost and usage details file schema