Merge pull request #300610 from PriskeyJeronika/pup

prmerger-automator[bot] · web-flow · commit 2baf2d20389a · 2025-05-30T07:07:25.000Z
Added preview tags and updated PS command
diff --git a/articles/site-recovery/azure-to-azure-architecture.md b/articles/site-recovery/azure-to-azure-architecture.md
@@ -3,7 +3,7 @@ title: Azure to Azure disaster recovery architecture in Azure Site Recovery
 description: Overview of the architecture used when you set up disaster recovery between Azure regions for Azure VMs, using the Azure Site Recovery service.
 ms.service: azure-site-recovery
 ms.topic: concept-article
-ms.date: 05/19/2025
+ms.date: 05/30/2025
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -22,7 +22,7 @@ The components involved in disaster recovery for Azure VMs are summarized in the
 **VMs in source region** | One of more Azure VMs in a [supported source region](azure-to-azure-support-matrix.md#region-support).<br/><br/> VMs can be running any [supported operating system](azure-to-azure-support-matrix.md#replicated-machine-operating-systems).
 **Source VM storage** | Azure VMs can be managed, or have nonmanaged disks spread across storage accounts.<br/><br/>[Learn about](azure-to-azure-support-matrix.md#replicated-machines---storage) supported Azure storage.
 **Source VM networks** | VMs can be located in one or more subnets in a virtual network (VNet) in the source region. [Learn more](azure-to-azure-support-matrix.md#replicated-machines---networking) about networking requirements.
-**Cache storage account** | You need a cache storage account in the source network. During replication, VM changes are stored in the cache before being sent to target storage. <br/><br/> Using a cache ensures minimal impact on production applications that are running on a VM.<br/><br/> [Learn more](azure-to-azure-support-matrix.md#cache-storage) about cache storage requirements.<br/><br/> **Note**: Virtual machines with Premium SSD v2 disks require High Churn and uses Premium Storage Account. 
+**Cache storage account** | You need a cache storage account in the source network. During replication, VM changes are stored in the cache before being sent to target storage. <br/><br/> Using a cache ensures minimal impact on production applications that are running on a VM.<br/><br/> [Learn more](azure-to-azure-support-matrix.md#cache-storage) about cache storage requirements.<br/><br/> **Note**: Virtual machines with Premium SSD v2 disks (preview) require High Churn and uses Premium Storage Account. 
 **Target resources** | Target resources are used during replication, and when a failover occurs. Site Recovery can set up target resource by default, or you can create/customize them.<br/><br/> In the target region, check that you're able to create VMs, and that your subscription has enough resources to support VM sizes that are needed in the target region. 
 
 ![Diagram showing source and target replication.](./media/concepts-azure-to-azure-architecture/enable-replication-step-1-v2.png)
diff --git a/articles/site-recovery/azure-to-azure-common-questions.md b/articles/site-recovery/azure-to-azure-common-questions.md
@@ -3,7 +3,7 @@ title: Common questions about Azure virtual machine disaster recovery with Azure
 description: This article answers common questions about Azure virtual machine disaster recovery when you use Azure Site Recovery.
 ms.author: ankitadutta
 author: ankitaduttaMSFT
-ms.date: 05/28/2025
+ms.date: 05/30/2025
 ms.topic: faq
 ms.service: azure-site-recovery
 
@@ -137,7 +137,7 @@ The Azure portal displays *logical Zones*. In the datacenter, actual physical zo
 
 In case the source and target zones are the same, you can't view zone for target configuration while enabling zonal replication.
 
-### Premium SSD v2 disks
+### Premium SSD v2 disks (preview)
 
 #### What disk sector size is supported when I protect VMs with Premium SSD v2 disks?
 
diff --git a/articles/site-recovery/azure-to-azure-powershell.md b/articles/site-recovery/azure-to-azure-powershell.md
@@ -5,7 +5,7 @@ ms.service: azure-site-recovery
 author: ankitaduttaMSFT
 manager: rochakm
 ms.topic: how-to
-ms.date: 04/29/2025
+ms.date: 05/30/2025
 ms.author: ankitadutta 
 ms.custom: devx-track-azurepowershell
 ---
@@ -322,7 +322,7 @@ $WusToEusPCMapping = Get-AzRecoveryServicesAsrProtectionContainerMapping -Protec
 
 ## Create cache storage account and target storage account
 
-A cache storage account is a standard storage account in the same Azure region as the virtual machine being replicated. The cache storage account is used to hold replication changes temporarily, before the changes are moved to the recovery Azure region. High churn support is also available in Azure Site Recovery to get higher churn limits. To use this feature, please create a Premium Block Blob type of storage accounts and then use it as the cache storage account.  You can choose to, but it's not necessary, to specify different cache storage accounts for the different disks of a virtual machine. If you use different cache storage accounts, ensure they are of the same type (Standard or Premium Block Blobs). For more information, see [Azure VM Disaster Recovery - High Churn Support](./concepts-azure-to-azure-high-churn-support.md).
+A cache storage account is a standard storage account in the same Azure region as the virtual machine being replicated. The cache storage account is used to hold replication changes temporarily, before the changes are moved to the recovery Azure region. High churn support is also available in Azure Site Recovery to get higher churn limits. To use this feature, please create a Premium Block Blob type of storage accounts and then use it as the cache storage account. Azure Site Recovery for Premium SSD v2 disks (preview) is supported only using high churn. Use SkuName Premium_LRS to enable high churn. You can choose to, but it's not necessary, to specify different cache storage accounts for the different disks of a virtual machine. If you use different cache storage accounts, ensure they are of the same type (Standard or Premium Block Blobs). For more information, see [Azure VM Disaster Recovery - High Churn Support](./concepts-azure-to-azure-high-churn-support.md).
 
 ```azurepowershell
 #Create Cache storage account for replication logs in the primary region
@@ -429,6 +429,9 @@ $OSDiskReplicationConfig = New-AzRecoveryServicesAsrAzureToAzureDiskReplicationC
 # Data disk
 $datadiskId1 = $vm.StorageProfile.DataDisks[0].ManagedDisk.Id
 $RecoveryReplicaDiskAccountType = $vm.StorageProfile.DataDisks[0].ManagedDisk.StorageAccountType
+if ($RecoveryReplicaDiskAccountType -in @("PremiumV2_LRS", "Ultra_LRS")) {
+    $RecoveryReplicaDiskAccountType = "Premium_LRS"
+}
 $RecoveryTargetDiskAccountType = $vm.StorageProfile.DataDisks[0].ManagedDisk.StorageAccountType
 
 $DataDisk1ReplicationConfig  = New-AzRecoveryServicesAsrAzureToAzureDiskReplicationConfig -ManagedDisk -LogStorageAccountId $EastUSCacheStorageAccount.Id `
diff --git a/articles/site-recovery/azure-to-azure-quickstart.md b/articles/site-recovery/azure-to-azure-quickstart.md
@@ -2,7 +2,7 @@
 title: Set up Azure VM disaster recovery to a secondary region with Azure Site Recovery
 description: Quickly set up disaster recovery to another Azure region for an Azure VM, using the Azure Site Recovery service.
 ms.topic: quickstart
-ms.date: 05/22/2025
+ms.date: 05/30/2025
 ms.custom: mvc, mode-other
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -40,7 +40,7 @@ The following steps enable VM replication to a secondary location.
    >Azure Site Recovery has a *High Churn* option that you can choose to protect VMs with high data change rate. With this, you can use a *Premium Block Blob* type of storage account. By default, the **Normal Churn** option is selected. For more information, see [Azure VM Disaster Recovery - High Churn Support](./concepts-azure-to-azure-high-churn-support.md).
    >:::image type="High churn" source="media/concepts-azure-to-azure-high-churn-support/churn-for-vms.png" alt-text="Screenshot of Churn for VM.":::
    >
-   >Azure Site Recovery for Premium SSD v2 by default uses High Churn and a Premium Block Blob type. 
+   >Azure Site Recovery for Premium SSD v2 (preview) by default uses High Churn and a Premium Block Blob type. 
 1. To start the job that enables VM replication, select **Start replication**.
 
    :::image type="content" source="media/azure-to-azure-quickstart/enable-replication1.png" alt-text="Enable replication.":::
diff --git a/articles/site-recovery/site-recovery-cost.md b/articles/site-recovery/site-recovery-cost.md
@@ -3,7 +3,7 @@ title: Understanding Azure Site Recovery for Managed Disks Charges
 description: This article summarizes the costs disaster recovery and migration deployment scenarios.
 ms.topic: overview
 ms.service: azure-site-recovery
-ms.date: 05/19/2025
+ms.date: 05/30/2025
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -49,7 +49,7 @@ This cost includes:
 
 - **Source**:
   - For Premium SSD disks, incremental snapshots are charged.
-  - For Standard and Premium SSD v2 disks, one full snapshot followed by incremental snapshots is charged.
+  - For Standard and Premium SSD v2 disks (preview), one full snapshot followed by incremental snapshots is charged.
 - **Target**:
   - Snapshot costs are associated with the recovery points created by Azure Site Recovery. These snapshots capture the replica storage at a point in time and are charged based on the consumed capacity. Pricing details align with Page Blob Snapshots. [Learn more](https://azure.microsoft.com/pricing/details/storage/page-blobs/#:~:text=Note%3A%20Snapshots%20are%20charged,at%20%240.12%20%2FGB%20per%20month.?msockid=3816c7206e2268e7035dd3316f7069f4).
 
