Merge pull request #313316 from Dhananjayanr98/patch-37

Update migrate-to-trusted-launch-virtual-machines-with-azure-migrate.md

Author: prmerger-automator[bot]

articles/migrate/migrate-to-trusted-launch-virtual-machines-with-azure-migrate.md

@@ -21,14 +21,20 @@ Trusted Launch is the default security type for supported Generation 2 Virtual
 Azure Migrate supports all Operating systems that are supported for Trusted Launch in Azure. For more information, See [Azure supported OS list and Virtual Machine sizes](/azure/virtual-machines/trusted-launch#operating-systems-supported).
 
 >[!Note]
->Trusted Launch is a security feature for Generation 2 Virtual Machines. Generation 1 Virtual Machines use BIOS and MBR, and they do not support Secure Boot or vTPM by design. As a result, Generation 1 Virtual Machines cannot use Trusted Launch and Azure migrate does not support migrating Gen 1 Virtual Machines to Trusted Launch virtual Machines
+>Trusted Launch is a security feature for Generation 2 Virtual Machines. Generation 1 Virtual Machines use BIOS and MBR, and they do not support Secure Boot or vTPM by design. As a result, Generation 1 Virtual Machines cannot use Trusted Launch and Azure migrate does not support migrating Gen 1 Virtual Machines to Trusted Launch virtual Machines.
 
 ## Secure boot
 At the root of Trusted Launch is Secure Boot. Secure Boot is implemented in platform firmware and protects virtual machines from malware such as bootkits and rootkits. Secure Boot ensures that only signed operating systems and drivers can start. It establishes a trusted boot chain for the virtual machine. When Secure Boot is enabled, all operating system boot components—including the boot loader, kernel, and kernel drivers—must be signed by trusted publishers. Both Windows and supported Linux distributions support Secure Boot. If Secure Boot can't verify a trusted signature, the virtual machine fails to boot.
 
 >[!Note]
 >Secure Boot is configured as part of the Trusted Launch settings on the target Virtual Machine and isn’t inherited from the source Virtual Machine. Even if Secure Boot was enabled on the source Virtual Machine, it isn’t automatically enabled on the migrated Trusted Launch Virtual Machine. You must explicitly enable Secure Boot in the Trusted Launch configuration during migration.
 
-## How to migrate to trusted launch virtual machines using Azure Migrate
-This guide explains how to migrate your workloads to Trusted Launch Virtual Machines using Azure Migrate. For more information, See [How to migrate to trusted launch virtual machines using Azure Migrate](tutorial-migrate-vmware.md).
+## Related Links
+- [Assess VM for Trusted Launch Virtual Machines](target-right-sizing.md).
+- [Migrate VMWare VMs to Trusted Launch VMs](tutorial-migrate-vmware.md).
+- [Migrate Hyper V VM to Trusted Launch VM](tutorial-migrate-hyper-v.md).
+- [Migrate Physical or other cloud servers to Trusted Launch VM](tutorial-migrate-physical-virtual-machines.md).
+
+
+