removing blockers

Author: Ankita Dutta

articles/site-recovery/azure-to-azure-customize-networking.md

@@ -6,7 +6,7 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
 ms.topic: article
-ms.date: 03/02/2023
+ms.date: 03/27/2023
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 
@@ -39,12 +39,12 @@ You can provide the following key resource configurations for the failover VM wh
 2. Select the desired Azure VM.
 3. Select **Network** and select **Edit**. Notice that the NIC configuration settings include the corresponding resources at the source.
 
-    :::image type="content" source="./media/azure-to-azure-customize-networking/edit-networking-properties.png" alt-text="Customize the failover networking configurations" lightbox="./media/azure-to-azure-customize-networking/edit-networking-properties.png":::
+    :::image type="content" source="./media/azure-to-azure-customize-networking/edit-networking-properties.png" alt-text="Image showing how to Customize the failover networking configurations." lightbox="./media/azure-to-azure-customize-networking/edit-networking-properties.png":::
 
 4. Select a test failover virtual network.
 5. Select the NIC tab you want to configure. Now, select the corresponding pre-created resources in the test failover and failover location.
 
-    :::image type="content" source="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png" alt-text="Edit the NIC configuration" lightbox="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png":::
+    :::image type="content" source="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png" alt-text="Image showing how to Edit the NIC configuration." lightbox="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png":::
 
 6. Select **OK**.
 

articles/site-recovery/azure-to-azure-network-mapping.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 03/02/2023
+ms.date: 03/27/2023
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 
@@ -27,14 +27,14 @@ Map networks as follows:
 
 1. In **Site Recovery Infrastructure**, click **+Network Mapping**.
 
-    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png" alt-text="Create a network mapping" lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png":::
+    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png" alt-text="Image showing how to Create a network mapping." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png":::
 
 3. In **Add network mapping**, select the source and target locations. In our example, the source VM is running in the East Asia region, and replicates to the Southeast Asia region.
 
-    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png" alt-text="Select source and target" lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png":::
+    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png" alt-text="Image showing how to Select source and target." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png":::
 3. Now create a network mapping in the opposite direction. In our example, the source will now be Southeast Asia, and the target will be East Asia.
 
-    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png" alt-text="Add network mapping pane - Select source and target locations for the target network" lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png":::
+    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png" alt-text="Image showing how to Add network mapping pane - Select source and target locations for the target network." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png":::
 
 
 ## Map networks when you enable replication
@@ -59,7 +59,7 @@ The subnet of the target VM is selected based on the name of the subnet of the s
 - If a subnet with the same name doesn't exist in the target network, the first subnet in the alphabetical order is set as the target subnet.
 - You can modify the target subnet in the **Network** settings for the VM.
 
-    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png" alt-text="Network compute properties window" lightbox="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png":::
+    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png" alt-text="Image showing how to Network compute properties window" lightbox="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png":::
 
 ## Set up IP addressing for target VMs
 
@@ -87,7 +87,7 @@ Different address space | The next available IP address in the target subnet is
 **Target network** | **Details**
 --- | ---
 Target network is the failover VNet | - Target IP address will be static with the same IP address. <br/><br/>  - If the same IP address is already assigned, then the IP address is the next one available at the end of the subnet range. For example: If the source IP address is 10.0.0.19 and failover network uses range 10.0.0.0/24, then the next IP address assigned to the target VM is 10.0.0.254.
-Target network isn't the failover VNet | - Target IP address will be static with the same IP address, only if it is available in the target virtual network. <br/><br/>  - If the same IP address is already assigned, then the IP address is the next one available at the end of the subnet range.<br/><br/> For example: If the source static IP address is 10.0.0.19 and failover is on an network that isn't the failover network, with the range 10.0.0.0/24, then the target static IP address will be 10.0.0.19 if available, and otherwise it will be 10.0.0.254.
+Target network isn't the failover VNet | - Target IP address will be static with the same IP address, only if it is available in the target virtual network. <br/><br/>  - If the same IP address is already assigned, then the IP address is the next one available at the end of the subnet range.<br/><br/> For example: If the source static IP address is 10.0.0.19 and failover is on a network that isn't the failover network, with the range 10.0.0.0/24, then the target static IP address will be 10.0.0.19 if available, and otherwise it will be 10.0.0.254.
 
 - The failover VNet is the target network that you select when you set up disaster recovery.
 - We recommend that you always use a non-production network for test failover.

articles/site-recovery/azure-to-azure-support-matrix.md

@@ -2,7 +2,7 @@
 title: Support matrix for Azure VM disaster recovery with Azure Site Recovery
 description: Summarizes support for Azure VMs disaster recovery to a secondary region with Azure Site Recovery.
 ms.topic: article
-ms.date: 03/02/2023
+ms.date: 03/27/2023
 ms.service: site-recovery
 author: ankitaduttaMSFT
 ms.author: ankitadutta

articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md

@@ -7,7 +7,7 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 03/02/2023
+ms.date: 03/27/2023
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 
@@ -16,7 +16,7 @@ ms.custom: engagement-fy23
 
 Accelerated Networking enables single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the datapath, reducing latency, jitter, and CPU utilization, for use with the most demanding network workloads on supported VM types. The following picture shows communication between two VMs with and without accelerated networking:
 
-:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png" alt-text="Comparison" lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png":::
+:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png" alt-text="Image showing Comparison." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png":::
 
 Azure Site Recovery enables you to utilize the benefits of Accelerated Networking, for Azure virtual machines that are failed over to a different Azure region. This article describes how you can enable Accelerated Networking for Azure virtual machines replicated with Azure Site Recovery.
 
@@ -70,7 +70,7 @@ When you [enable replication](azure-to-azure-tutorial-enable-replication.md) for
 
 The status of Accelerated Networking can be verified under the respective NIC's Tab in the **Network** settings for the replicated virtual machine.
 
-:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png" alt-text="Accelerated Networking setting" lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png":::
+:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png" alt-text="Image showing the Accelerated Networking setting." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png":::
 
 
 
@@ -79,7 +79,7 @@ If you have enabled Accelerated Networking on the source virtual machine after e
 2. Click on the name of the network interface under the **Network interfaces** section
 3. Select **Enabled** from the dropdown for Accelerated Networking under the **Target** column
 
-:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png" alt-text="Enable Accelerated Networking" lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png":::
+:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png" alt-text="Image showing how to Enable Accelerated Networking." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png":::
 
 
 The above process should also be followed for existing replicated virtual machines, that did not previously have Accelerated Networking enabled automatically by Site Recovery.

articles/site-recovery/concepts-multiple-ip-address-failover.md

@@ -6,7 +6,7 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 03/02/2023
+ms.date: 03/27/2023
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 
@@ -25,24 +25,24 @@ Site Recovery automatically configures the failover of your Primary IP Configura
 
 1. Navigate to the **Network** blade on the Replicated Items page.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-tab.png" alt-text="Replicated Items Blade":::
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-tab.png" alt-text="Image showing Replicated Items Blade.":::
 
 
 2. You will see the following highlighted text.  Click on **Edit** to modify it.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-edit.png" alt-text="Network Tab Edit Mode" lightbox="./media/concepts-multiple-ip-address-failover/network-edit-expanded.png":::    
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-edit.png" alt-text="Image showing Network Tab Edit Mode." lightbox="./media/concepts-multiple-ip-address-failover/network-edit-expanded.png":::    
 
 3. Click on "+ IP Configurations". You will see two options, Either add all IP Configurations, or selectively add IP Configurations.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-ip-configurations.png" alt-text="Add IP Configurations":::
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-ip-configurations.png" alt-text="Image showing how to Add IP Configurations.":::
 
 4. On clicking **Add all secondary IP Configurations**, all of them will appear in the grid below, and then you can configure them as you like.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations.png" alt-text="Add All IP Configurations" lightbox="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations-expanded.png":::    
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations.png" alt-text="Image showing how to add All IP Configurations." lightbox="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations-expanded.png":::    
 
 5. Alternatively, on clicking **Select and add secondary IP Configurations**, a blade will open where you can pick and add IP Configurations you'd like to configure for failover.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png" alt-text="Select and Add IP Configurations" lightbox="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png"::::::
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png" alt-text="Image showing how to Select and Add IP Configurations." lightbox="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png":::
 
 Now, for each IP Configuration that you've added, you can configure the values for Private IP, Public IP, and Backend Pool for Failover and Test Failover separately. After you've done it all, don't forget to Save changes.