Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into su

Author: gitName

articles/api-center/synchronize-aws-gateway-apis.md

@@ -8,8 +8,9 @@ ms.date: 02/10/2025
 ms.author: danlep 
 ms.custom: 
   - devx-track-azurecli
-  - migration
-  - aws-to-azure
+ms.collection: 
+ - migration
+ - aws-to-azure
 # Customer intent: As an API program manager, I want to integrate my Azure API Management instance with my API center and synchronize API Management APIs to my inventory.
 ---
 

articles/application-gateway/application-gateway-probe-overview.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 09/14/2023
+ms.date: 04/09/2025
 ms.author: greglin 
 ms.custom: devx-track-azurepowershell
 ---
@@ -46,15 +46,15 @@ Once the probe detects a failed response, the counter for "Unhealthy threshold"
 
 An application gateway automatically configures a default health probe when you don't set up any custom probe configuration. The monitoring behavior works by making an HTTP GET request to the IP addresses or FQDN configured in the backend pool. For default probes if the backend http settings are configured for HTTPS, the probe uses HTTPS to test health of the backend servers.
 
-For example: You configure your application gateway to use backend servers A, B, and C to receive HTTP network traffic on port 80. The default health monitoring tests the three servers every 30 seconds for a healthy HTTP response with a 30-second-timeout for each request. A healthy HTTP response has a [status code](/troubleshoot/developer/webapps/iis/www-administration-management/http-status-code) between 200 and 399. In this case, the HTTP GET host header for the health probe looks like `http://127.0.0.1/`. Also see [HTTP response codes in Application Gateway](http-response-codes.md).
+For example: You configure your application gateway to use backend servers A, B, and C to receive HTTP network traffic on port 80. The default health monitoring tests the three servers every 30 seconds for a healthy HTTP response with a 30-second-timeout for each request. A healthy HTTP response has a [status code](/troubleshoot/developer/webapps/iis/www-administration-management/http-status-code) between 200 and 399. In this case, the HTTP GET Host header for the health probe appears as `http://127.0.0.1/`, unless a hostname is configured in the [Backend Settings](configuration-http-settings.md#configuring-the-host-name).
 
 If the default probe check fails for server A, the application gateway stops forwarding requests to this server. The default probe still continues to check for server A every 30 seconds. When server A responds successfully to one request from a default health probe, application gateway starts forwarding the requests to the server again.
 
 ### Default health probe settings
 
 | Probe property | Value | Description |
 | --- | --- | --- |
-| Probe URL |\<protocol\>://127.0.0.1:\<port\>/ |The protocol and port are inherited from the backend HTTP settings to which the probe is associated |
+| Probe URL |\<protocol\>://127.0.0.1:\<port\>/ |The protocol and port are inherited from the Backend Settings to which the probe is associated. The default host is 127.0.0.1 unless one is specified in the associated Backend Settings. |
 | Interval |30 |The amount of time in seconds to wait before the next health probe is sent.|
 | Time-out |30 |The amount of time in seconds the application gateway waits for a probe response before marking the probe as unhealthy. If a probe returns as healthy, the corresponding backend is immediately marked as healthy.|
 | Unhealthy threshold |3 |Governs how many probes to send in case there's a failure of the regular health probe. In v1 SKU, these additional health probes are sent in quick succession to determine the health of the backend quickly and don't wait for the probe interval. For v2 SKU, the health probes wait the interval. The backend server is marked down after the consecutive probe failure count reaches the unhealthy threshold. |

articles/azure-cache-for-redis/cache-migration-guide.md

@@ -1,14 +1,12 @@
 ---
 title: Migrate to Azure Cache for Redis
 description: Learn how to migrate your existing cache to Azure Cache for Redis
-
-
-
 ms.topic: conceptual
 ms.custom:
   - ignite-2024
-  - migration
-  - aws-to-azure
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.date: 11/17/2021
 appliesto:
   - ✅ Azure Cache for Redis

articles/azure-functions/migration/assess-lambda-workloads.md

@@ -4,6 +4,9 @@ description: Learn how to map AWS Lambda features to Azure Functions and develop
 author: MadhuraBharadwaj-MSFT
 ms.author: mabhar
 ms.service: azure-functions
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.topic: how-to
 ms.date: 03/18/2025
 #customer intent: As a developer, I want to ensure compatibility between features and create a detailed migration plan so that I can migrate serverless applications from AWS Lambda to Azure Functions efficiently.

articles/azure-functions/migration/discover-lambda-workloads.md

@@ -4,6 +4,9 @@ description: Learn how to conduct a detailed discovery process to inventory curr
 author: MadhuraBharadwaj-MSFT
 ms.author: mabhar
 ms.service: azure-functions
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.topic: how-to
 ms.date: 03/18/2025
 #customer intent: As a developer, I want to evaluate existing AWS Lambda workloads so that I can migrate serverless applications to Azure Functions efficiently.

articles/azure-functions/migration/migrate-lambda-workloads-overview.md

@@ -4,6 +4,9 @@ description: Learn about Azure Functions and the three stages that you need to c
 author: MadhuraBharadwaj-MSFT
 ms.author: mabhar
 ms.service: azure-functions
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.topic: how-to
 ms.date: 03/18/2025
 #customer intent: As a developer, I want to learn how to migrate serverless applications from AWS Lambda to Azure Functions so that I can make the transition efficiently.

articles/azure-functions/migration/migrate-lambda-workloads.md

@@ -4,6 +4,9 @@ description: Learn about the steps to complete your AWS Lambda to Azure Function
 author: MadhuraBharadwaj-MSFT
 ms.author: mabhar
 ms.service: azure-functions
+ms.collection: 
+ - migration
+ - aws-to-azure
 ms.topic: how-to
 ms.date: 03/18/2025
 #customer intent: As a developer, I want to adapt function code for compatibility and best practices so that I can migrate serverless applications from AWS Lambda to Azure Functions efficiently.

articles/azure-maps/elevation-data-services.md

@@ -363,7 +363,7 @@ http://localhost:7071/api/tileserver?zoom={z}&x={x}&y={y}
 [QGIS]: https://www.qgis.org/en/site/forusers/download.html
 [rio-rgbify]: https://pypi.org/project/rio-rgbify/
 [PostgreSQL]: https://www.postgresql.org/download/
-[PostGIS]: https://postgis.net/install/
+[PostGIS]: https://postgis.net/documentation/getting_started/#learn-about-spatial-sql
 [Azure Maps Web SDK]: about-azure-maps.md#web-sdk
 [Create Contour line vector tiles and RGB-encoded DEM tiles]: #create-contour-line-vector-tiles-and-rgb-encoded-dem-tiles
 [Create Contour line vector tile service using Azure Function and PostgreSQL]: #create-contour-line-vector-tile-service-using-azure-function-and-postgresql

articles/azure-maps/release-notes-map-control.md

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: Release notes for the Azure Maps Web SDK. 
 author: sinnypan
 ms.author: sipa
-ms.date: 03/24/2025
+ms.date: 04/09/2025
 ms.topic: reference
 ms.service: azure-maps
 ms.subservice: web-sdk
@@ -16,7 +16,7 @@ This document contains information about new features and other changes to the M
 
 ## v3 (latest)
 
-### [3.6.1] (CDN: April 7, 2025, npm: TBA)
+### [3.6.1] (CDN: April 7, 2025, npm: April 9, 2025)
 
 #### Bug fixes
 * Fix the issue where `maxBounds` wasn't included in `map.getCamera()`, causing it to be unset when `setCamera()` is called.

articles/azure-vmware/azure-vmware-solution-platform-updates.md

@@ -13,13 +13,13 @@ Microsoft regularly applies important updates to the Azure VMware Solution for n
 
 ## April 2025
 
-Public Preview of the next generation of AVS, AVS in a Virtual Network (also known as AVS on Fleet Native internally) is now available in East US, UK South, Switzerland North and Japan East on the AV64 SKU. With this capability,
+Public Preview of the next generation of AVS, AVS in a Virtual Network (also known as AVS on Fleet Native internally) is now available in East US, UK South, Switzerland North and Japan East on the AV64 SKU. 
 
-We've achieved Infrastructure innovation, powered by Azure Boost, simplifying networking, delivering 100 Gbps throughput, lowering latency, and boosting performance for VMware workloads.
+With this capability, we've achieved Infrastructure innovation, powered by Azure Boost, simplifying networking, delivering 100 Gbps throughput, lowering latency, and boosting performance for VMware workloads.
 
 - Customers can deploy their AVS Private Clouds directly using the AV64 node size. There is no need for minimum 3-host AV36, AV36P, AV48 or AV52 cluster.
 
-Private clouds deployed inside a virtual network, enabling your private cloud with standard Azure Networking. ExpressRoute is no longer required required.
+Private clouds deployed inside a virtual network, enables your private cloud with standard Azure Networking. ExpressRoute is no longer required.
 
 Azure VMware Solution AV48 node size is now available in the Japan East region. The AV48 node is built on Intel Xeon Gold 6442Y CPUs with a total of 48 physical cores, 1 TB of Memory and 19.2 TB of total storage.