Updated Screenshots and references to blade in A2A scenarios

Author: rrishabhjn

articles/site-recovery/azure-stack-site-recovery.md

@@ -254,7 +254,7 @@ Before you run a test failover, verify the machine properties, and make sure tha
 
 1. In **Protected Items**, click **Replicated Items** > VM.
 2. In the **Replicated item** pane, there's a summary of VM information, health status, and the latest available recovery points. Click **Properties** to view more details.
-3. In **Compute and Network**, modify settings as needed.
+3. In **Compute** and **Network** settings, modify settings as needed.
 
     - You can modify the Azure VM name, resource group, target size, [availability set](../virtual-machines/windows/tutorial-availability-sets.md), and managed disk settings.
     - You can also view and modify network settings. These include the network/subnet to which the Azure VM is joined after failover, and the IP address that will be assigned to the VM.

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

@@ -48,17 +48,17 @@ If you haven't prepared network mapping before you configure disaster recovery f
 
 >[!NOTE]
 >* Modifying the network mapping only changes the defaults for new VM replications. It does not impact the target virtual network selections for existing replications.
->* If you wish to modify the target network for an existing replication, go to Compute and Network Settings of the replicated item.
+>* If you wish to modify the target network for an existing replication, go to **Network** Settings of the replicated item.
 
 ## Specify a subnet
 
 The subnet of the target VM is selected based on the name of the subnet of the source VM.
 
 - If a subnet with the same name as the source VM subnet is available in the target network, that subnet is set for the target VM.
 - 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 **Compute and Network** settings for the VM.
+- You can modify the target subnet in the **Network** settings for the VM.
 
-    ![Compute and Network compute properties window](./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png)
+    ![Network compute properties window](./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png)
 
 
 ## Set up IP addressing for target VMs
@@ -87,7 +87,7 @@ Target network isn't the failover VNet | - Target IP address will be static with
 
 - 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.
-- You can modify the target IP address in the **Compute and Network** settings of the VM.
+- You can modify the target IP address in the **Network** settings of the VM.
 
 
 ## Next steps

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

@@ -321,9 +321,9 @@ Internal Load balancer | Supported | Associate the preconfigured load balancer u
 Public IP address | Supported | Associate an existing public IP address with the NIC. Or, create a public IP address and associate it with the NIC using an Azure Automation script in a recovery plan.
 NSG on NIC | Supported | Associate the NSG with the NIC using an Azure Automation script in a recovery plan.
 NSG on subnet | Supported | Associate the NSG with the subnet using an Azure Automation script in a recovery plan.
-Reserved (static) IP address | Supported | If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, it's assigned to the failed over VM.<br/><br/> If the target subnet doesn't have the same IP address available, one of the available IP addresses in the subnet is reserved for the VM.<br/><br/> You can also specify a fixed IP address and subnet in **Replicated items** > **Settings** > **Compute and Network** > **Network interfaces**.
+Reserved (static) IP address | Supported | If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, it's assigned to the failed over VM.<br/><br/> If the target subnet doesn't have the same IP address available, one of the available IP addresses in the subnet is reserved for the VM.<br/><br/> You can also specify a fixed IP address and subnet in **Replicated items** > **Settings** > **Network** > **Network interfaces**.
 Dynamic IP address | Supported | If the NIC on the source has dynamic IP addressing, the NIC on the failed over VM is also dynamic by default.<br/><br/> You can modify this to a fixed IP address if required.
-Multiple IP addresses | Not supported | When you fail over a VM that has a NIC with multiple IP addresses, only the primary IP address of the NIC in the source region is kept. To assign multiple IP addresses, you can add VMs to a [recovery plan](recovery-plan-overview.md) and attach a script to assign additional IP addresses to the plan, or you can make the change manually or with a script after failover.
+Multiple IP addresses | Supported | When you fail over a VM that has a NIC with multiple IP addresses, only the primary IP address of the NIC in the source region is kept by default. To failover Secondary IP Configurations, go to the **Network** blade and configure them.
 Traffic Manager     | Supported | You can preconfigure Traffic Manager so that traffic is routed to the endpoint in the source region on a regular basis, and to the endpoint in the target region in case of failover.
 Azure DNS | Supported |
 Custom DNS    | Supported |

articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md

@@ -62,7 +62,7 @@ To select a proximity placement group in the DR region while enabling replicatio
 You can easily update your selection of a proximity placement group in the DR region after replication has been enabled for the VM:
 
 1. Go to the virtual machine. On the left pane, under **Operations**, select **Disaster Recovery**.
-2. Go to the **Compute and Network** pane and select **Edit**.
+2. Go to the **Compute** pane and select **Edit**.
 3. You can see the options to edit multiple target settings, including the target proximity placement group. Choose the proximity placement group that you want the VM to fail over into, and then select **Save**.
 
 ### VMware to Azure

articles/site-recovery/site-recovery-active-directory.md

@@ -42,7 +42,7 @@ The domain controller that is replicated by using Site Recovery is used for [tes
 
 ### Configure VM network settings
 
-For the virtual machine that hosts the domain controller or DNS, in Site Recovery, configure network settings under the **Compute and Network** settings of the replicated virtual machine. This ensures that the virtual machine is attached to the correct network after failover.
+For the virtual machine that hosts the domain controller or DNS, in Site Recovery, configure network settings under the **Network** settings of the replicated virtual machine. This ensures that the virtual machine is attached to the correct network after failover.
 
 ## Protect Active Directory
 
@@ -72,12 +72,12 @@ Most applications require the presence of a domain controller or a DNS server. T
 
 1. Use Site Recovery to [replicate](vmware-azure-tutorial.md) the virtual machine that hosts the domain controller or DNS.
 1. Create an isolated network. Any virtual network that you create in Azure is isolated from other networks by default. We recommend that you use the same IP address range for this network that you use in your production network. Don't enable site-to-site connectivity on this network.
-1. Provide a DNS IP address in the isolated network. Use the IP address that you expect the DNS virtual machine to get. If you're replicating to Azure, provide the IP address for the virtual machine that's used on failover. To enter the IP address, in the replicated virtual machine, in the **Compute and Network** settings, select the **Target IP** settings.
+1. Provide a DNS IP address in the isolated network. Use the IP address that you expect the DNS virtual machine to get. If you're replicating to Azure, provide the IP address for the virtual machine that's used on failover. To enter the IP address, in the replicated virtual machine, in the **Network** settings, select the **Target IP** settings.
 
    :::image type="content" source="./media/site-recovery-active-directory/azure-test-network.png" alt-text="Azure test network":::
 
    > [!TIP]
-   > Site Recovery attempts to create test virtual machines in a subnet of the same name and by using the same IP address that's provided in the **Compute and Network** settings of the virtual machine. If a subnet of the same name isn't available in the Azure virtual network that's provided for test failover, the test virtual machine is created in the alphabetically first subnet.
+   > Site Recovery attempts to create test virtual machines in a subnet of the same name and by using the same IP address that's provided in the **Network** settings of the virtual machine. If a subnet of the same name isn't available in the Azure virtual network that's provided for test failover, the test virtual machine is created in the alphabetically first subnet.
    >
    > If the target IP address is part of the selected subnet, Site Recovery tries to create the test failover virtual machine by using the target IP address. If the target IP isn't part of the selected subnet, the test failover virtual machine is created by using the next available IP in the selected subnet.
 

articles/site-recovery/site-recovery-failover-to-azure-troubleshoot.md

@@ -20,7 +20,7 @@ Site Recovery was not able to create a failed over virtual machine in Azure. It
 
 * There isn't sufficient quota available to create the virtual machine: You can check the available quota by going to Subscription -> Usage + quotas. You can open a [new support request](https://aka.ms/getazuresupport) to increase the quota.
 
-* You are trying to failover virtual machines of different size families in same availability set. Ensure that you choose same size family for all virtual machines in the same availability set. Change size by going to Compute and Network settings of the virtual machine and then retry failover.
+* You are trying to failover virtual machines of different size families in same availability set. Ensure that you choose same size family for all virtual machines in the same availability set. Change size by going to **Compute** settings of the virtual machine and then retry failover.
 
 * There is a policy on the subscription that prevents creation of a virtual machine. Change the policy to allow creation of a virtual machine and then retry failover.
 
@@ -32,7 +32,7 @@ Site Recovery was not able to create a network interface for the failed over vir
 
 Site Recovery was not able to create a failed over Classic virtual machine in Azure. It could happen because:
 
-* One of the resources such as a virtual network that is required for the virtual machine to be created doesn't exist. Create the virtual network as provided under Compute and Network settings of the virtual machine or modify the setting to a virtual network that already exists and then retry failover.
+* One of the resources such as a virtual network that is required for the virtual machine to be created doesn't exist. Create the virtual network as provided under Network settings of the virtual machine or modify the setting to a virtual network that already exists and then retry failover.
 
 ## Failover failed with Error ID 170010
 

articles/site-recovery/site-recovery-iis.md

@@ -64,9 +64,9 @@ Azure|NA|Yes
 
 To start replicating all the IIS web farm virtual machines to Azure, follow the guidance in [Test failover to Azure in Site Recovery](site-recovery-test-failover-to-azure.md).
 
-If you are using a static IP address, you can specify the IP address that you want the virtual machine to take. To set the IP address, go to  **Compute and Network settings** > **TARGET IP**.
+If you are using a static IP address, you can specify the IP address that you want the virtual machine to take. To set the IP address, go to  **Network settings** > **TARGET IP**.
 
-![Screenshot that shows how to set the target IP in the Site Recovery Compute and Network pane](./media/site-recovery-active-directory/dns-target-ip.png)
+![Screenshot that shows how to set the target IP in the Site Recovery Network pane](./media/site-recovery-active-directory/dns-target-ip.png)
 
 ## Create a recovery plan
 A recovery plan supports the sequencing of various tiers in a multi-tier application during a failover. Sequencing helps maintain application consistency. When you create a recovery plan for a multi-tier web application, complete the steps described in [Create a recovery plan by using Site Recovery](site-recovery-create-recovery-plans.md).