Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us429364-seo-top25-vnet

Author: asudbring

.openpublishing.redirection.json

@@ -6958,6 +6958,11 @@
       "source_path": "articles/signups/startup-programs.md",
       "redirect_url": "/azure/signups/overview",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/reliability/migrate-sql-database.md",
+      "redirect_url": "/azure/azure-sql/database/enable-zone-redundancy",
+      "redirect_document_id": false
     }
 
   ]

articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md

@@ -3,7 +3,7 @@ title: Move Azure App Service resources across resource groups or subscriptions
 description: Use Azure Resource Manager to move App Service resources to a new resource group or subscription.
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 02/11/2025
+ms.date: 07/28/2025
 ---
 
 # Move App Service resources to a new resource group or subscription

articles/azure-resource-manager/management/move-limitations/media/app-service-move-limitations/show-hidden-types.png

@@ -3,7 +3,7 @@ title: Attach Azure NetApp Files datastores to Azure VMware Solution hosts
 description: Learn how to create Azure NetApp Files-based NFS datastores for Azure VMware Solution hosts.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 01/29/2025
+ms.date: 07/28/2025
 ms.custom: "references_regions, engagement-fy23"
 # Customer intent: "As an IT administrator, I want to attach Azure NetApp Files NFS datastores to Azure VMware Solution hosts, so that I can optimize storage performance and manage virtual machine workloads effectively in a cloud environment."
 ---
@@ -62,6 +62,7 @@ Azure NetApp Files datastores for Azure VMware Solution are currently supported
 * South Africa North
 * South Central US
 * Southeast Asia
+* Spain Central
 * Sweden Central
 * Switzerland North
 * Switzerland West

articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md

@@ -39,7 +39,7 @@ Azure Communication Services calling generates **eight distinct log types**, eac
 
 ### **Call summary updates logs**: 
 Fast-arriving logs with basic call metadata (IDs, timestamps, endpoints, SDK info). These log data arrive in Azure Monitor faster than the call summary logs. This log contains basic information about the call, including all the relevant IDs, time stamps, endpoints, and SDK information.
-- Data available within 60 minutes of the call ending.
+- Data generally available within 60 minutes after the call ending.
 - May contain multiple rows per call participant.
 - Contains the most recent updates for each participant.
 - Useful for near-real-time monitoring and analysis of call activities.
@@ -48,7 +48,7 @@ To learn more, see: [Call summary updates log schema](call-summary-updates-log-s
 
 ### **Call summary logs**:
 This log is a subset of the Call summary updates log schema. It contains basic information about the call, including all the relevant IDs, time stamps, endpoints, and SDK information. For faster log latency, use the call summary updates logs instead. 
-- Data available within 3-5 hours of the call ending.
+- Data generally available within 3 to 5 hours after the call ending.
 - Contains a single row per call participant.
 - Represents a snapshot of the call state at the time of finalization.
 - Useful for post-call analysis and reporting.