Merge pull request #296275 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

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

@@ -25,7 +25,7 @@ The most recent stable release of the Azure Maps services.
 | [Data Registry] |  2023-06-01  | Programmatically store and update geospatial data to use in spatial operations.<br>The Data registry service is deprecated and will be retired on 9/30/25. |
 | [Geolocation] |  1.0  | Convert IP addresses to country/region ISO codes. |
 | [Render] |  2024-04-01  | Get road, satellite/aerial, weather, traffic map tiles, and static map images. |
-| [Route] |  1.0  | Calculate optimized travel times and distances between locations for multiple modes of transportation and get localized travel instructions. |
+| [Route] |  2025-01-01  | Calculate optimized travel times and distances between locations for multiple modes of transportation and returns localized travel instructions. Now supports [Snap to Roads] API that snaps GPS data to road aligned coordinates. |
 | [Search] |  2025-01-01  | Geocode addresses and coordinates, search for business listings and places by name or category and get administrative boundary polygons. |
 | [Spatial] |  2022-08-01  | Use geofences, great circle distances, and other spatial operations to analyze location data.<br>The Spatial service is deprecated and will be retired on 9/30/25. |
 | [Timezone] |  1.0  | Get time zone and sunrise/sunset information for specified locations. |
@@ -40,6 +40,7 @@ There are previous stable releases of an Azure Maps service that are still in us
 |-----|-------------|-------------|
 | [Render][Render v1] |  1.0  | Get road, satellite/aerial, weather, traffic map tiles, and static map images.<BR>The Azure Maps [Render v1] service is now deprecated and will be retired on 9/17/26. To avoid service disruptions, all calls to Render v1 API need to be updated to use the latest version of the [Render] API. |
 | [Render][render-2022-08-01] |  2022-08-01  | Get road, satellite/aerial, weather, traffic map tiles, and static map images. |
+| [Route] |  1.0  | Calculate optimized travel times and distances between locations for multiple modes of transportation and get localized travel instructions. |
 | [Search][Search v1] |  1.0  | Geocode addresses and coordinates, search for business listings and places by name or category and get administrative boundary polygons. This is version 1.0 of the Search service. For the latest version, see [Search]. |
 | [Search] |  2023-06-01  | Geocode addresses and coordinates, search for business listings and places by name or category and get administrative boundary polygons. |
 
@@ -49,14 +50,15 @@ Prerelease version of an Azure Maps service. Preview releases contain new functi
 
 | API | API version | Description |
 |-----|-------------|-------------|
-| [Route][Route-2024-07-01-preview] | 2024-07-01-preview | Returns the ideal route in GeoJSON between locations for multiple modes of transportation.<BR><BR>Some of the updates in this version of the Route service include:<ul><li>New Snap to Roads API that snaps GPS data to road aligned coordinates.</li><li>Support for up to 50,000 cells in Route Matrix async.</li><li>High-definition route range polygon.</li><li>Routes with "via" waypoints that the route must pass through.</li><li>More geographies</li><li>More languages available for localized travel instructions.</li> |
+| [Route][Route-2024-07-01-preview] | 2024-07-01-preview | The Route Range API supports high definition isochrone polygons. |
 
 <!--- Links to latest versions of each service ---------------------------------->
 [Data Registry]: /rest/api/maps/data-registry
 [Geolocation]: /rest/api/maps/geolocation
 [Render]: /rest/api/maps/render
 [Route]: /rest/api/maps/route
 [Search]: /rest/api/maps/search
+[Snap to Roads]: /azure/azure-maps/tutorial-snap-to-road
 [Spatial]: /rest/api/maps/spatial
 [Timezone]: /rest/api/maps/timezone
 [Traffic]: /rest/api/maps/traffic

articles/azure-resource-manager/bicep/parameter-files.md

@@ -8,6 +8,10 @@ ms.custom: devx-track-bicep
 
 # Create a parameters file for Bicep deployment
 
+Bicep parameter files allow you to define values in an individual file that are then passed to your `main.bicep` file. The parameter file exposes values that may change from a given subscription, environment, and/or region. Leveraging a parameter file will drive consistency in your IaC deployments while also providing flexibility. Some of this flexibility might allow an organization to take advantage of cost benefits by right-sizing their nonproduction environments while maintaining the same core infrastructure. 
+
+These parameter files also help enable a streamlined CI/CD deployment approach. Each parameter file is under source control and passed into the appropriate automated deployment steps. These parameter files ensure a consistent deployment experience.
+
 This article shows you how to create a parameters file, which you can use instead of passing parameters as inline values in your script. You can use either a Bicep parameters file with the `.bicepparam` file extension or a JSON parameters file that contains the parameter value.
 
 > [!NOTE]

articles/expressroute/expressroute-howto-gateway-migration-portal.md

@@ -56,7 +56,7 @@ Here are the steps to migrate to a new gateway in Azure portal.
     > [!NOTE]
     > Be aware that your existing Virtual Network gateway will be locked during this process, preventing any creation or modification of connections to this gateway.
 
-1. Select **Prepare** to create the new gateway. This operation could take up to 60 minutes.
+1. Select **Prepare** to create the new gateway. This operation could take up to 45 minutes.
 
 1. After the new gateway is created, you'll proceed to the *Migrate* stage. Here, select the new gateway you created. In this example, it's **myERGateway_migrated**. This transfers the settings from your old gateway to the new one. All network traffic, control plane, and data path connections from your old gateway will transfer without any interruptions. To start this process, select **Migrate Traffic**. This operation could take up to 5 minutes.
 
@@ -68,8 +68,9 @@ Here are the steps to migrate to a new gateway in Azure portal.
 
 
 >[!IMPORTANT]
-> - Before running this step, verify that the new virtual network gateway has a working ExpressRoute connection.
+> - Before running this step, verify that the new virtual network gateway has a working ExpressRoute connection and validate if the traffic is flowing through the new connection.
 > - When migrating your gateway, you can expect possible interruption for a maximum of 30 seconds.
+> - Once committed, the connection name can't be changed and has to be deleted and recreated if you want to change the connection naming. Reach out to Azure support in case of any issues.
 
 ## Next steps