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

Author: RoseHJM

articles/healthcare-apis/dicom/dicom-services-conformance-statement-v2.md

@@ -297,6 +297,7 @@ An example response with `Accept` header `application/dicom+json` with a FailedA
 | `43265` | The provided instance `StudyInstanceUID` didn't match the specified `StudyInstanceUID` in the store request. |
 | `45070` | A DICOM instance with the same `StudyInstanceUID`, `SeriesInstanceUID`, and `SopInstanceUID` was already stored. If you want to update the contents, delete this instance first. |
 | `45071` | A DICOM instance is being created by another process, or the previous attempt to create failed and the cleanup process isn't complete. Delete the instance first before attempting to create again. |
+| `45073` | A DICOM instance was deleted by the user, before the write operation for that instance could be committed successfully. |
 
 #### Store warning reason codes
 

articles/reliability/reliability-fabric.md

@@ -109,7 +109,7 @@ For more information, see the [Power BI high availability, failover, and disas
 
 
 >[!IMPORTANT]
-> For customers whose home regions don't have an Azure pair region and are affected by a disaster, the ability to utilize Fabric capacities may be compromised—even if the data within those capacities is replicated. This limitation is tied to the home region’s infrastructure, essential for the capacities' operation. 
+> For customers affected by a disaster and whose home regions don't have an Azure paired region that supports Fabric, the ability to utilize Fabric capacities may be compromised, even if the data within those capacities is replicated. This limitation is tied to the home region’s infrastructure, essential for the capacities' operation. To see the list of regions that support Fabric, go to [Fabric Region Availability](/fabric/admin/region-availability).
 
 ### Home region and capacity functionality
 

articles/vpn-gateway/basic-public-ip-migrate-about.md

@@ -23,6 +23,8 @@ To migrate your gateway, you first need to validate whether your resource is cap
 
 * If your current gateway subnet is /28 or smaller, the migration tool may error out. You can use this to [add multiple prefixes for subnet](../virtual-network/how-to-multiple-prefixes-subnet.md) to /27 or larger before you can proceed with migration.
 
+* If you have ExpressRoute and VPN coexisting. We'd like to recommend customers to consider migrating the Basic IP resources to Standard IP on **VPN** first. 
+
 
 
 ## FAQ

includes/functions-set-nodejs-version-portal.md

@@ -2,7 +2,7 @@
 author: ggailey777
 ms.service: azure-functions
 ms.topic: include
-ms.date: 06/28/2023
+ms.date: 10/03/2025
 ms.author: glenga
 ---
 
@@ -12,6 +12,4 @@ ms.author: glenga
 
 1. Select the **General settings** tab and update the **Node.js Version** to the latest version. Ideally, you have already locally verified that your functions run on the version you select. 
 
-    :::image type="content" source="media/functions-set-nodejs-version-portal/set-nodejs-version-portal.png" alt-text="Screenshot of setting Node.js for the function app to the latest LTS version in the Azure portal. ":::
-
-1. When notified about a restart, select **Continue**, and then select **Save**. 
+1. When notified about a restart, select **Continue**, and then select **Save**.