Merge pull request #296754 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/backup/backup-azure-database-postgresql.md

@@ -182,5 +182,5 @@ Azure Backup service creates a job for scheduled backups or if you trigger on-de
 
 ## Next steps
 
-- [Azure Backup pricing information for PostgreSQ](https://azure.microsoft.com/pricing/details/backup/)
-- [Troubleshoot PostgreSQL database backup by using Azure Backup](backup-azure-database-postgresql-troubleshoot.md)
+- [Azure Backup pricing information for PostgreSQL](https://azure.microsoft.com/pricing/details/backup/)
+- [Troubleshoot PostgreSQL database backup by using Azure Backup](backup-azure-database-postgresql-troubleshoot.md)

articles/container-apps/how-to-integrate-with-azure-front-door.md

@@ -36,6 +36,8 @@ In this article, you learn how to connect directly from Azure Front Door to your
 
 - This feature is only supported for workload profile environments.
 
+- This feature is only available in [supported regions](/azure/frontdoor/private-link#region-availability).
+
 For more information about prerequisites and setup, see [Quickstart: Deploy your first container app with containerapp up](get-started.md?tabs=bash).
 
 ## Set environment variables

articles/healthcare-apis/fhir/fhir-best-practices.md

@@ -35,16 +35,16 @@ To achieve optimal performance with the import operation, consider the following
 
 In Azure FHIR service, bundles act as containers for multiple resources. Batch and transaction bundles enable users to submit sets of actions in a single HTTP request or response. Consider the following to achieve higher throughput with bundle ingestion.
 
-* **Do** tune the number of concurrent bundle requests to the FHIR server. A high number (>100) may lead to negative scaling and reduced processing throughput. The optimal concurrency is dependent on the complexity of the bundles and resources.
 * **Do** generate load on Azure FHIR service in a linear manner and avoid burst operations to prevent performance degradation.
+* **Do** tune the number of concurrent bundle requests to the FHIR server. A high number (>100) may lead to negative scaling and reduced processing throughput.
+* **DO** use separate transaction bundles for FHIR resources that don't depend on each other, and can be updated separately.
+* **Consider** using smaller bundle sizes for complex operations such as conditional creates or updates.
 * **Consider** enabling parallel processing for batch and transaction bundles. By default, resources in bundles are processed sequentially. To enhance throughput, you can enable parallel resource processing by adding the HTTP header flag `x-bundle-processing-logic` and setting it to `parallel`. For more information, see the [batch bundle parallel processing documentation](rest-api-capabilities.md#bundle-parallel-processing).
+* **Avoid** submitting parallel bundle requests that attempt to update the same resources concurrently, which can cause delays in processing.
+* **Avoid** submitting a large number of bundles with a single PUT or POST request can lead to transaction bottlenecks.
 
 > [!NOTE]
-> Parallel bundle processing can enhance throughput when there isn't an implicit dependency on the order of resources within an HTTP operation.
-
-* **Consider** splitting resource entries across multiple bundles to increase parallelism, which can enhance throughput. Optimizing the number of resource entries in a bundle can reduce network time.
-* **Consider** using smaller bundle sizes for complex operations. Smaller transaction bundles can reduce errors and support data consistency. Use separate transaction bundles for FHIR resources that don't depend on each other, and can be updated separately.
-* **Avoid** submitting parallel bundle requests that attempt to update the same resources concurrently, which can cause delays in processing.
+> Parallel bundle processing using the `x-bundle-processing-logic` flags can enhance throughput when there isn't an implicit dependency on the order of resources within an HTTP operation.
 
 ### Search parameter index tuning
 

includes/static-web-apps-languages-runtimes.md

@@ -11,18 +11,22 @@ To configure the API language runtime version, set the `apiRuntime` property in
 | Language runtime version | Operating system | Azure Functions version | `apiRuntime` value | End of support date |
 |--|--|--|--|--|
 | .NET Core 3.1 | Windows | 3.x | `dotnet:3.1` | December 3, 2022 |
-| .NET 6.0 in-process | Windows | 4.x | `dotnet:6.0` | - |
-| .NET 6.0 isolated | Windows | 4.x | `dotnet-isolated:6.0` | - |
-| .NET 7.0 isolated | Windows | 4.x | `dotnet-isolated:7.0` | - |
+| .NET 6.0 in-process | Windows | 4.x | `dotnet:6.0` | April 30, 2025 |
+| .NET 8.0 in-process | Windows | 4.x | `dotnet:8.0` | - |
+| .NET 6.0 isolated | Windows | 4.x | `dotnet-isolated:6.0` | April 30, 2025 |
+| .NET 7.0 isolated | Windows | 4.x | `dotnet-isolated:7.0` | April 30, 2025 |
 | .NET 8.0 isolated | Windows | 4.x | `dotnet-isolated:8.0` | - |
+| .NET 9.0 isolated | Windows | 4.x | `dotnet-isolated:9.0` | - |
 | Node.js 12.x | Linux | 3.x | `node:12` | December 3, 2022 |
-| Node.js 14.x | Linux | 4.x | `node:14` | - |
-| Node.js 16.x | Linux | 4.x | `node:16` | - |
-| Node.js 18.x | Linux | 4.x | `node:18` | - |
-| Node.js 20.x (preview) | Linux | 4.x | `node:20` | - |
-| Python 3.8 | Linux | 4.x | `python:3.8` | - |
+| Node.js 14.x | Linux | 4.x | `node:14` | April 30, 2025 |
+| Node.js 16.x | Linux | 4.x | `node:16` | April 30, 2025 |
+| Node.js 18.x | Linux | 4.x | `node:18` | May 31, 2025 |
+| Node.js 20.x | Linux | 4.x | `node:20` | - |
+| Python 3.8 | Linux | 4.x | `python:3.8` | April 30, 2025 |
 | Python 3.9 | Linux | 4.x | `python:3.9` | - |
 | Python 3.10 | Linux | 4.x | `python:3.10` | - |
+| Python 3.11 | Linux | 4.x | `python:3.11` | - |
+
 
 ### .NET