Merge pull request #171058 from JYOTHIRMAISURI/master

adding notes and minor updates

Author: PRMerger7

articles/site-recovery/deploy-vmware-azure-replication-appliance-preview.md

@@ -3,7 +3,7 @@ title: Deploy Azure Site Recovery replication appliance - Preview
 description: This article describes support and requirements when deploying the replication appliance for VMware disaster recovery to Azure with Azure Site Recovery - Preview
 ms.service: site-recovery
 ms.topic: article
-ms.date: 08/19/2021
+ms.date: 09/01/2021
 ---
 
 # Deploy Azure Site Recovery replication appliance - Preview
@@ -62,10 +62,9 @@ Ensure the following URLs are allowed and reachable from the Azure Site Recovery
   |aka.ms |Allow access to also known as links. Used for Azure Site Recovery appliance updates. |
   |download.microsoft.com/download |Allow downloads from Microsoft download. |
   |`*.servicebus.windows.net `|Communication between the appliance and the Azure Site Recovery service. |
-  |`*.discoverysrv.windowsazure.com `|Connect to Azure Site Recovery discovery service URL. |
-  |`*.hypervrecoverymanager.windowsazure.com `|Connect to Azure Site Recovery micro-service URLs  |
-  |`*.blob.core.windows.net `|Upload data to Azure storage which is used to create target disks |
-  |`*.backup.windowsazure.com `|Protection service URL – a microservice used by Azure Site Recovery for processing and creating replicated disks in Azure |
+  |`*.discoverysrv.windowsazure.com `<br><br>`*.hypervrecoverymanager.windowsazure.com `<br><br> `*.backup.windowsazure.com ` |Connect to Azure Site Recovery micro-service URLs.
+  |`*.blob.core.windows.net `|Upload data to Azure storage which is used to create target disks. |
+
 
 > [!NOTE]
 > Private links are not supported with the preview release.
@@ -236,6 +235,9 @@ In case of any organizational restrictions, you can manually set up the Site Rec
 
     Ensure you do not close the browser while configuration is in progress.
 
+    >[!NOTE]
+    > Appliance cloning is not supported with this preview. If you attempt to clone, it might disrupt the recovery flow.
+
 
 ## View Azure Site Recovery replication appliance in Azure portal
 
@@ -263,4 +265,4 @@ An appliance that uses an inbuilt process server to protect the workload can han
 For detailed information about how to use multiple appliances and failover a replication appliance, see [this article](switch-replication-appliance-preview.md)
 
 ## Next steps
-Set up disaster recovery of [VMware VMs](vmware-azure-tutorial.md) to Azure.
+Set up disaster recovery of [VMware VMs](vmware-azure-set-up-replication-tutorial-preview.md) to Azure.

articles/site-recovery/switch-replication-appliance-preview.md

@@ -3,7 +3,7 @@ title: Switch replication appliance in Azure Site Recovery - Preview
 description: This article describes show to switch between different replication appliances while replicating VMware VMs to Azure in Azure Site Recovery- Preview
 ms.service: site-recovery
 ms.topic: article
-ms.date: 08/19/2021
+ms.date: 09/01/2021
 ---
 
 # Switch Azure Site Recovery replication appliance
@@ -73,4 +73,4 @@ As an example, here is the scenario where replication appliance 1 (RA1) has beco
    Once the resync is complete, the replication status turns healthy for the VMs that are moved to a new appliance.
 
 ## Next steps
-Set up disaster recovery of [VMware VMs](vmware-azure-tutorial.md) to Azure.
+Set up disaster recovery of [VMware VMs](vmware-azure-set-up-replication-tutorial-preview.md) to Azure.

articles/site-recovery/upgrade-mobility-service-preview.md

@@ -3,14 +3,22 @@ title: Upgrade Mobility Service and appliance components - preview
 description: This article describes about automatic updates for mobility agent and the procedure involved with manual updates - preview.
 ms.service: site-recovery
 ms.topic: article
-ms.date: 08/19/2021
+ms.date: 09/01/2021
 ---
 
 
 # Upgrade Mobility Service and Appliance components (Preview)
 
+From this preview, you do not need to maintain source machine's Root/Admin credentials are not required for performing upgrades. The credentials are required only for the initial installation of the agent. Once done, you can remove the credentials.
+
+
+## Update mobility agent automatically
+
 By default, automatic updates are enabled on a vault. Automatic updates will be triggered at 12:00 AM local time every day, if a new version is available.
 
+> [!NOTE]
+> If you are using private preview bits, automatic updates are blocked for the protected machines. Ensure that you setup Site Recovery on your machine again, using a fresh Preview appliance.
+
 To avail the latest features, enhancements and fixes, we recommend you to choose **Allow Site Recovery to manage** option on the **Mobility agent upgrade settings (Preview)**. Automatic updates do not require a reboot or affect on-going replication of your virtual machines. Automatic updates also ensure that all the replication appliances in the vault are automatically updated.
 
 ![Automatic updates on for Mobility agent](./media/upgrade-mobility-service-preview/automatic-updates-on.png)
@@ -19,8 +27,6 @@ To turn off the automatic updates, toggle the **Allow Site Recovery to manage**
 
 ![Automatic updates off for mobility agent](./media/upgrade-mobility-service-preview/automatic-updates-off.png)
 
-> [!NOTE]
-> If you are using private preview bits, automatic updates are blocked for the protected machines. Ensure that you setup Site Recovery on your machine again, using a fresh Preview appliance.
 
 ## Update mobility agent manually