Merge pull request #179125 from v-bllyd/patch-20

Update backup-azure-vms-encryption.md

Author: PRMerger9

articles/backup/backup-azure-vms-encryption.md

@@ -146,27 +146,11 @@ To set permissions:
 
 1. Select **Save** to provide Azure Backup with the permissions.
 
-## Restore an encrypted VM
-
-Encrypted VMs can only be restored by restoring the VM disk as explained below. **Replace existing** and **Restore VM** aren't supported.
-
-Restore encrypted VMs as follows:
-
-1. [Restore the VM disk](backup-azure-arm-restore-vms.md#restore-disks).
-
-   > [!NOTE]
-   > After you restore the VM disk, you can manually swap the OS disk of the original VM with the restored VM disk without re-creating it. [Learn more](https://azure.microsoft.com/blog/os-disk-swap-managed-disks/).
-
-2. Recreate the virtual machine instance by doing one of the following actions:
-    1. Use the template that's generated during the restore operation to customize VM settings, and trigger VM deployment. [Learn more](backup-azure-arm-restore-vms.md#use-templates-to-customize-a-restored-vm).
-       >[!NOTE]
-       >While deploying the template, verify the storage account containers and the public/private settings.
-    1. Create a new VM from the restored disks using PowerShell. [Learn more](backup-azure-vms-automation.md#create-a-vm-from-restored-disks).
-1. For Linux VMs, reinstall the ADE extension so the data disks are open and mounted.
-
 ## Next steps
 
+[Restore encrypted Azure virtual machines](restore-azure-encrypted-virtual-machines.md)
+
 If you run into any issues, review these articles:
 
 - [Common errors](backup-azure-vms-troubleshoot.md) when backing up and restoring encrypted Azure VMs.
-- [Azure VM agent/backup extension](backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md) issues.
+- [Azure VM agent/backup extension](backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md) issues.