Skip to content

Commit 28ee335

Browse files
Update migrate-to-trusted-launch-virtual-machines-using-azure-migrate.md
1 parent d4cbe0d commit 28ee335

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,5 +30,5 @@ At the root of Trusted Launch is Secure Boot. Secure Boot is implemented in plat
3030
>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.
3131
3232
## How to migrate to trusted launch Virtual Machines using azure migrate:
33-
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?view=migrate#set-up-the-azure-migrate-appliance).
33+
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).
3434

0 commit comments

Comments
 (0)