Merge branch 'main' into release-aio-2507

Author: v-alje

.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

@@ -11,9 +11,9 @@ ms.service: azure-baremetal-infrastructure
 # Customer intent: As an IT administrator, I want to sign up for and configure Nutanix Cloud Clusters on Azure, so that I can efficiently manage my cloud infrastructure while ensuring connectivity and compliance with my organization’s requirements.
 ---
 
-# Getting started with Nutanix Cloud Clusters on Azure
+# Get started with Nutanix Cloud Clusters on Azure
 
-Learn how to sign up for, set up, and use Nutanix Cloud Clusters (NC2) on Azure.
+Learn how to sign up for, set up, and use Nutanix Cloud Clusters (NC2) on Azure. You can also sign up for a free trial of NC2 on Azure.
 
 ## Azure account requirements
 
@@ -25,6 +25,22 @@ Learn how to sign up for, set up, and use Nutanix Cloud Clusters (NC2) on Azure.
 For more information, see "NC2 on Azure Subscription and Billing" in [Nutanix Cloud Clusters on Azure Deployment and User Guide]
 (https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Cloud-Clusters-Azure:Nutanix-Cloud-Clusters-Azure).
 
+## Start with a free trial of NC2 on Azure
+
+To help you evaluate NC2 on Azure, Nutanix offers and manages a 30-day free trial. You can sign up for the trial with Nutanix. 
+
+Consider these important items for Nutanix on Azure BareMetal nodes:
+
+**Cost coverage**: The BareMetal cluster nodes have no cost through the trial. Other components like VMs for Flow Gateway networking and other Azure services are billed and not included in the trial.
+
+**Trial duration**: The trial begins with the initial hardware node deployment and lasts for 30 consecutive days. It can't be paused, and the start date is fixed regardless of cluster activity. Even if the cluster is dropped, the trial time continues.
+
+**One-time opportunity**: The trial is a one-time offer. If you deploy a cluster after the initial 30-day trial period, regardless of the timeframe, the trial doesn't reset, and you'll be billed. Creating a cluster in a different subscription does not reset your trial timing.
+
+**Track the trial period**: There's no visible trial information for the BareMetal. You should track your BareMetal deployment date manually.
+
+For more information, see _*[Starting a Free Trial for NC2 ](https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Cloud-Clusters-Azure:nc2-clusters-starting-a-nc2-free-trial-t.html"https://portal.nutanix.com/page/documents/details?targetid=nutanix-cloud-clusters-azure:nc2-clusters-starting-a-nc2-free-trial-t.html")*
+
 ## Networking requirements
 
 * Connectivity between your on-premises datacenter and Azure. Both ExpressRoute and VPN are supported. 
@@ -41,7 +57,7 @@ gateway-external-api.cloud.nutanix.com.
 
 ## Sign up for NC2
 
-Go to [Nutanix Cloud Clusters on Azure Deployment and User Guide](https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Cloud-Clusters-Azure:Nutanix-Cloud-Clusters-Azure) to sign up.
+To sign up, go to [Nutanix Cloud Clusters on Azure Deployment and User Guide(https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Cloud-Clusters-Azure:Nutanix-Cloud-Clusters-Azure).
 
 To learn about Microsoft BareMetal hardware pricing, and to purchase Nutanix software, go to [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/nutanixinc.nc2_azure?tab=Overview).
 

articles/baremetal-infrastructure/workloads/nc2-on-azure/get-started.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.