Merge pull request #261697 from ankitaduttaMSFT/toc-cleanup

Toc cleanup

Author: v-ccolin

.openpublishing.redirection.json

@@ -1080,6 +1080,46 @@
             "redirect_url": "/azure/site-recovery/azure-to-azure-autoupdate",
             "redirect_document_id": false
         },
+        {
+            "source_path": "articles/site-recovery/vmware-azure-tutorial.md",
+            "redirect_url": "/azure/site-recovery/azure-to-azure-tutorial-enable-replication",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/site-recovery/vmware-azure-tutorial-failover-failback.md",
+            "redirect_url": "/azure/site-recovery/azure-to-azure-tutorial-enable-replication",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/site-recovery/physical-azure-architecture.md",
+            "redirect_url": "/azure/site-recovery/physical-server-azure-architecture-modernized",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/site-recovery/vmware-azure-configuration-server-requirements.md",
+            "redirect_url": "/azure/site-recovery/vmware-physical-azure-classic-deprecation",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/site-recovery/vmware-physical-azure-config-process-server-overview.md",
+            "redirect_url": "/azure/site-recovery/deploy-vmware-azure-replication-appliance-modernized",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/site-recovery/vmware-azure-about-disaster-recovery.md",
+            "redirect_url": "/azure/site-recovery/site-recovery-overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/site-recovery/vmware-physical-secondary-architecture.md",
+            "redirect_url": "/azure/site-recovery/transport-layer-security",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/site-recovery/hyper-v-vmm-architecture.md",
+            "redirect_url": "/azure/site-recovery/transport-layer-security",
+            "redirect_document_id": false
+        },        
         {
             "source_path": "articles/container-registry/container-registry-customer-managed-keys.md",
             "redirect_url": "/azure/container-registry/tutorial-customer-managed-keys",

articles/site-recovery/azure-to-azure-autoupdate.md

@@ -25,7 +25,7 @@ When you use Site Recovery to manage updates, it deploys a global runbook (used
 The default runbook schedule occurs daily at 12:00 AM in the time zone of the replicated VM's geography. You can also change the runbook schedule via the automation account.
 
 > [!NOTE]
-> Starting with [Update Rollup 35](site-recovery-whats-new.md#updates-march-2019), you can choose an existing automation account to use for updates. Prior to Update Rollup 35, Site Recovery created the automation account by default. You can only select this option when you enable replication for a VM. It isn't available for a VM that already has replication enabled. The setting you select applies to all Azure VMs protected in the same vault.
+> Starting with [Update Rollup 35](site-recovery-whats-new-archive.md#updates-march-2019), you can choose an existing automation account to use for updates. Prior to Update Rollup 35, Site Recovery created the automation account by default. You can only select this option when you enable replication for a VM. It isn't available for a VM that already has replication enabled. The setting you select applies to all Azure VMs protected in the same vault.
 
 Turning on automatic updates doesn't require a restart of your Azure VMs or affect ongoing replication.