Merge pull request #212807 from v-pgaddala/release-a2a-simplified-vault

minor edits

Author: v-dirichards

articles/site-recovery/azure-to-azure-common-questions.md

@@ -126,7 +126,7 @@ No, this is unsupported. If you accidentally move storage accounts to a differen
 
 A replication policy defines the retention history of recovery points, and the frequency of app-consistent snapshots.  Site Recovery creates a default replication policy as follows:
 
-- Retain recovery points for 1 day.
+- Retain recovery points for one day.
 - App-consistent snapshots are disabled and are not created by default.
 
 [Learn more](azure-to-azure-how-to-enable-replication.md) about replication settings.
@@ -171,7 +171,7 @@ So, for the recent two hours, you can choose from 24 crash-consistent points, an
 
 ### How far back can I recover?
 
-The oldest recovery point that you can use is 15 days with Managed disk and 3 days with Unmanaged disk.
+The oldest recovery point that you can use is 15 days with Managed disk and three days with Unmanaged disk.
 
 ### How does the pruning of recovery points happen?
 
@@ -200,7 +200,7 @@ The first recovery point that's generated has the complete copy. Successive reco
 
 ### Do increases in recovery point retention increase storage costs?
 
-Yes. For example, if you increase retention from 1 day to 3 days, Site Recovery saves recovery points for an additional two days. The added time incurs storage changes. Earlier, it was saving recovery points per hour for 1 day. Now, it is saving recovery points per two hours for 3 days. Refer [pruning of recovery points](#how-does-the-pruning-of-recovery-points-happen). So additional 12 recovery points are saved.  As an example only, if a single recovery point had delta changes of 10 GB, with a per-GB cost of $0.16 per month, then additional charges would be $1.60 × 12 per month.
+Yes. For example, if you increase retention from one day to three days, Site Recovery saves recovery points for an additional two days. The added time incurs storage changes. Earlier, it was saving recovery points per hour for 1 day. Now, it is saving recovery points per two hours for 3 days. Refer [pruning of recovery points](#how-does-the-pruning-of-recovery-points-happen). So additional 12 recovery points are saved.  As an example only, if a single recovery point had delta changes of 10 GB, with a per-GB cost of $0.16 per month, then additional charges would be $1.60 × 12 per month.
 
 ## Multi-VM consistency
 

articles/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms.md

@@ -88,29 +88,55 @@ Use the following procedure to replicate Azure Disk Encryption-enabled VMs to an
 1. Select **Next**.   
 1. In **Virtual machines**, select each VM that you want to replicate. You can only select machines for which replication can be enabled. You can select up to ten VMs. Then, select **Next**.
 
-   ![Screenshot that highlights where you select virtual machines.](./media/azure-to-azure-how-to-enable-replication-ade-vms/virtual-machine-selection.png)
+   :::image type="Virtual machine selection" source="./media/azure-to-azure-how-to-enable-replication/virtual-machine-selection.png" alt-text="Screenshot that highlights where you select virtual machines.":::
 
-1. In **Replication settings**, you can configure the following settings.
+1. In **Replication settings**, you can configure the following settings:
     1. Under **Location and Resource group**,
-        - **Target location**: Select the location where your source virtual machine data will be replicated. Site Recovery provides a list of suitable target regions based on the selected machine's location. We recommend that you use the same location as the Recovery Services vault's location.
-        - **Target subscription**: Select the target subscription that's used for disaster recovery. By default, the target subscription is the same as the source subscription.
-        - **Target resource group**: Select the resource group to which all your replicated virtual machines belong. By default, Site Recovery creates a new resource group in the target region. The name gets the *asr* suffix. If a resource group already exists that was created by Azure Site Recovery, it's reused. You can also choose to customize it, as shown in the following section. The location of the target resource group can be any Azure region except the region where the source virtual machines are hosted.
-        >[!Note]
-        > You can also create a new target resource group by selecting **Create New**.
+       - **Target location**: Select the location where your source virtual machine data must be replicated. Depending on the location of selected machines, Site Recovery will provide you the list of suitable target regions. We recommend that you keep the target location the same as the Recovery Services vault location.
+       - **Target subscription**: Select the target subscription used for disaster recovery. By default, the target subscription will be same as the source subscription.
+       - **Target resource group**: Select the resource group to which all your replicated virtual machines belong.
+           - By default, Site Recovery creates a new resource group in the target region with an *asr* suffix in the name.
+           - If the resource group created by Site Recovery already exists, it's reused.
+           - You can customize the resource group settings.
+           - The location of the target resource group can be any Azure region, except the region in which the source VMs are hosted.
+           
+            >[!Note]
+            > You can also create a new target resource group by selecting **Create new**. 
+        
+         :::image type="Location and resource group" source="./media/azure-to-azure-how-to-enable-replication-ade-vms/resource-group.png" alt-text="Screenshot of Location and resource group."::: 
+
     1. Under **Network**,
-        - **Failover virtual Network**: Select the Failover  virtual network.
-          >[!Note]
-          > You can also create a new failover virtual network by selecting **Create new**.
-        - **Failover subnet**: Select the failover subnet.
-    1. **Storage**: By default, Site Recovery creates a new target storage account by mimicking your source VM storage configuration. If a storage account already exists, it's reused. Select **View/edit storage configuration** to view or edit the storage account.
+       - **Failover virtual network**: Select the failover virtual network.
+         >[!Note]
+         > You can also create a new failover virtual network by selecting **Create new**.
+       - **Failover subnet**: Select the failover subnet.
+       
+         :::image type="Network" source="./media/azure-to-azure-how-to-enable-replication-ade-vms/network.png" alt-text="Screenshot of Network."::: 
+
+    1. **Storage**: Select **View/edit storage configuration**. **Customize target settings** page opens.
+    
+         :::image type="Storage" source="./media/azure-to-azure-how-to-enable-replication-ade-vms/storage.png" alt-text="Screenshot of Storage."::: 
+  
+       - **Replica-managed disk**: Site Recovery creates new replica-managed disks in the target region to mirror the source VM's managed disks with the same storage type (Standard or premium) as the source VM's managed disk.
+       - **Cache storage**: Site Recovery needs extra storage account called cache storage in the source region. All the changes happening on the source VMs are tracked and sent to cache storage account before replicating them to the target location. This storage account should be Standard. 
+         
     1. **Availability options**: Select appropriate availability option for your VM in the target region. If an availability set that was created by Site Recovery already exists, it's reused. Select **View/edit availability options** to view or edit the availability options.
-    1. **Capacity Reservation**: Capacity Reservation lets you purchase capacity in the recovery region, and then failover to that capacity. You can either create a new Capacity Reservation Group or use an existing one. For more information, see [how capacity reservation works](https://learn.microsoft.com/azure/virtual-machines/capacity-reservation-overview).
+        >[!NOTE]
+        >- While configuring the target availability sets, configure different availability sets for differently sized VMs.
+        >- You cannot change the availability type - single instance, availability set or availability zone, after you enable replication. You must disable and enable replication to change the availability type.  
+
+         :::image type="Availability option" source="./media/azure-to-azure-how-to-enable-replication-ade-vms/availability-option.png" alt-text="Screenshot of availability option."::: 
+   
+    1. **Capacity reservation**: Capacity Reservation lets you purchase capacity in the recovery region, and then failover to that capacity. You can either create a new Capacity Reservation Group or use an existing one. For more information, see [how capacity reservation works](https://learn.microsoft.com/azure/virtual-machines/capacity-reservation-overview).
+    Select **View or Edit Capacity Reservation group assignment** to modify the capacity reservation settings. On triggering Failover, the new VM will be created in the assigned Capacity Reservation Group.
+    
+         :::image type="Capacity reservation" source="./media/azure-to-azure-how-to-enable-replication-ade-vms/capacity-reservation.png" alt-text="Screenshot of capacity reservation.":::
 
     1. **Encryption settings**: Select **View/edit configuration** to configure the Disk Encryption and Key Encryption key Vaults.
         - **Disk encryption key vaults**: By default, Site Recovery creates a new key vault in the target region. It has an *asr* suffix that's based on the source VM disk encryption keys. If a key vault that was created by Azure Site Recovery already exists, it's reused.
         - **Key encryption key vaults**: By default, Site Recovery creates a new key vault in the target region. The name has an *asr* suffix that's based on the source VM key encryption keys. If a key vault created by Azure Site Recovery already exists, it's reused.
 
-       :::image type="enable replication parameters" source="./media/azure-to-azure-how-to-enable-replication-ade-vms/enable-vm-replication.png" alt-text="Screenshot that displays the enable replication parameters.":::
+       :::image type="Encryption settings" source="./media/azure-to-azure-how-to-enable-replication-ade-vms/encryption-settings.png" alt-text="Screenshot of encryption settings.":::
 
 1. Select **Next**.
 1. In **Manage**, do the following:
@@ -128,7 +154,7 @@ Use the following procedure to replicate Azure Disk Encryption-enabled VMs to an
 
    :::image type="review" source="./media/azure-to-azure-how-to-enable-replication-ade-vms/review.png" alt-text="Screenshot that displays the review tab.":::
 
-[!NOTE]
+>[!NOTE]
 >During initial replication, the status might take some time to refresh, without apparent progress. Click **Refresh**  to get the latest status.
 
 ## Update target VM encryption settings

articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md

@@ -35,12 +35,12 @@ As an example, the primary Azure region is East Asia, and the secondary region i
 1. Select **Next**.
 1. In **Virtual machines**, select each VM that you want to replicate. You can only select machines for which replication can be enabled. You can select up to ten VMs. Then select **Next**.
 
-   ![Screenshot that highlights where you select virtual machines.](./media/azure-to-azure-how-to-enable-replication-cmk-disks/virtual-machine-selection.png)
+   :::image type="Virtual machine selection" source="./media/azure-to-azure-how-to-enable-replication/virtual-machine-selection.png" alt-text="Screenshot that highlights where you select virtual machines.":::
 
 1. In **Replication settings**, you can configure the following settings:
     1. Under **Location and Resource group**,
-       - **Target location**: Select the location where your source virtual machine data will be replicated to. We recommend that you use the same location as the Recovery Services vault's location.
-       - **Target subscription**: Select the target subscription that's used for disaster recovery. By default, the target subscription is the same as the source subscription.
+       - **Target location**: Select the location where your source virtual machine data must be replicated. Depending on the location of selected machines, Site Recovery will provide you the list of suitable target regions. We recommend that you keep the target location the same as the Recovery Services vault location.
+       - **Target subscription**: Select the target subscription used for disaster recovery. By default, the target subscription will be same as the source subscription.
        - **Target resource group**: Select the resource group to which all your replicated virtual machines belong.
            - By default, Site Recovery creates a new resource group in the target region with an *asr* suffix in the name.
            - If the resource group created by Site Recovery already exists, it's reused.
@@ -50,24 +50,41 @@ As an example, the primary Azure region is East Asia, and the secondary region i
             >[!Note]
             > You can also create a new target resource group by selecting **Create new**. 
         
+         :::image type="Location and resource group" source="./media/azure-to-azure-how-to-enable-replication-cmk-disks/resource-group.png" alt-text="Screenshot of Location and resource group."::: 
+
     1. Under **Network**,
        - **Failover virtual network**: Select the failover virtual network.
          >[!Note]
          > You can also create a new failover virtual network by selecting **Create new**.
        - **Failover subnet**: Select the failover subnet.
-    1. **Storage**: By default, Site Recovery creates a new target storage account by mimicking your source VM storage configuration. If a storage account already exists, it's reused.
+       
+         :::image type="Network" source="./media/azure-to-azure-how-to-enable-replication-cmk-disks/network.png" alt-text="Screenshot of Network."::: 
+
+    1. **Storage**: Select **View/edit storage configuration**. **Customize target settings** page opens.
+    
+         :::image type="Storage" source="./media/azure-to-azure-how-to-enable-replication-cmk-disks/storage.png" alt-text="Screenshot of Storage."::: 
+  
+       - **Replica-managed disk**: Site Recovery creates new replica-managed disks in the target region to mirror the source VM's managed disks with the same storage type (Standard or premium) as the source VM's managed disk.
+       - **Cache storage**: Site Recovery needs extra storage account called cache storage in the source region. All the changes happening on the source VMs are tracked and sent to cache storage account before replicating them to the target location. This storage account should be Standard. 
+         
     1. **Availability options**: Select appropriate availability option for your VM in the target region. If an availability set that was created by Site Recovery already exists, it's reused. Select **View/edit availability options** to view or edit the availability options.
         >[!NOTE]
         >- While configuring the target availability sets, configure different availability sets for differently sized VMs.
-        >- You cannot change the availability type - single instance, availability set or availability zone, after you enable replication. You must disable and enable replication to change the availability type.     
+        >- You cannot change the availability type - single instance, availability set or availability zone, after you enable replication. You must disable and enable replication to change the availability type.  
+
+         :::image type="Availability option" source="./media/azure-to-azure-how-to-enable-replication-cmk-disks/availability-option.png" alt-text="Screenshot of availability option."::: 
+   
     1. **Capacity reservation**: Capacity Reservation lets you purchase capacity in the recovery region, and then failover to that capacity. You can either create a new Capacity Reservation Group or use an existing one. For more information, see [how capacity reservation works](https://learn.microsoft.com/azure/virtual-machines/capacity-reservation-overview).
+    Select **View or Edit Capacity Reservation group assignment** to modify the capacity reservation settings. On triggering Failover, the new VM will be created in the assigned Capacity Reservation Group.
 
-    1. **Storage encryption settings**: Site Recovery needs the disk encryption set(s)(DES) to be used for replica and target managed disks. You must pre-create Disk encryption sets in the target subscription and the target region before enabling the replication. By default, a Disk encryption sets is not selected. You must select **View/edit configuration** to choose a Disk encryption sets per source disk.
+         :::image type="Capacity reservation" source="./media/azure-to-azure-how-to-enable-replication-cmk-disks/capacity-reservation.png" alt-text="Screenshot of capacity reservation.":::
+
+    1. **Storage encryption settings**: Site Recovery needs the disk encryption set(s)(DES) to be used for replica and target managed disks. You must pre-create Disk encryption sets in the target subscription and the target region before enabling the replication. By default, a Disk encryption set is not selected. You must select **View/edit configuration** to choose a Disk encryption set per source disk.
 
        >[!Note]
        >Ensure that the Target DES is present in the Target Resource Group, and that the Target DES has Get, Wrap Key, Unwrap Key access to a Key Vault in the same region.
     
-        :::image type="enable replication parameters" source="./media/azure-to-azure-how-to-enable-replication-cmk-disks/enable-vm-replication.png" alt-text="Screenshot that displays the enable replication parameters.":::
+        :::image type="Storage encryption settings" source="./media/azure-to-azure-how-to-enable-replication-cmk-disks/storage-encryption-settings.png" alt-text="Screenshot of storage encryption settings.":::
 
 1. Select **Next**.
 1. In **Manage**, do the following: