แก้ไข

แชร์ผ่าน


Enable Trusted launch on existing Azure VMs

Applies to: ✔️ Linux VM ✔️ Windows VM ✔️ Generation 2 VM

Azure Virtual Machines supports enabling Azure Trusted launch on existing Azure Generation 2 virtual machines (VMs) by upgrading to the Trusted launch security type.

Trusted launch is a way to enable foundational compute security on Azure Generation 2 VMs and protects against advanced and persistent attack techniques like boot kits and rootkits. It does so by combining infrastructure technologies like Secure Boot, virtual Trusted Platform Module (vTPM), and boot integrity monitoring on your VM.

Important

Support for enabling Trusted launch on existing Azure Generation 1 VMs is currently in private preview. You can gain access to preview by using the registration form.

Prerequisites

Best practices

  • Enable Trusted launch on a test Generation 2 VM and determine if any changes are required to meet the prerequisites before you enable Trusted launch on Generation 2 VMs associated with production workloads.
  • Create restore points for Azure Generation 2 VMs associated with production workloads before you enable the Trusted launch security type. You can use the restore points to re-create the disks and Generation 2 VM with the previous well-known state.

Enable Trusted launch on an existing VM

Note

  • After you enable Trusted launch, currently VMs can't be rolled back to the Standard security type (non-Trusted launch configuration).
  • vTPM is enabled by default.
  • We recommend that you enable Secure Boot, if you aren't using custom unsigned kernel or drivers. It's not enabled by default. Secure Boot preserves boot integrity and enables foundational security for VMs.

Enable Trusted launch on an existing Azure Generation 2 VM by using the Azure portal.

  1. Sign in to the Azure portal.

  2. Confirm that the VM generation is V2 and select Stop for the VM.

    Screenshot that shows the Gen2 VM to be deallocated.

  3. On the Overview page in the VM properties, under Security type, select Standard. The Configuration page for the VM opens.

    Screenshot that shows the Security type as Standard.

  4. On the Configuration page, under the Security type section, select the Security type dropdown list.

    Screenshot that shows the Security type dropdown list.

  5. Under the dropdown list, select Trusted launch. Select checkboxes to enable Secure Boot and vTPM. After you make the changes, select Save.

    Note

    Screenshot that shows the Secure Boot and vTPM settings.

  6. After the update successfully finishes, close the Configuration page. On the Overview page in the VM properties, confirm the Security type settings.

    Screenshot that shows the Trusted launch upgraded VM.

  7. Start the upgraded Trusted launch VM. Verify that you can sign in to the VM by using either the Remote Desktop Protocol (RDP) for Windows VMs or the Secure Shell Protocol (SSH) for Linux VMs.

Azure Advisor Recommendation

Azure Advisor populates an Enable Trusted launch foundational excellence, and modern security for Existing Generation 2 VM(s) operational excellence recommendation for existing Generation 2 VMs to adopt Trusted launch, a higher security posture for Azure VMs at no additional cost to you. Ensure Generation 2 VM has all prerequisites to migrate to Trusted launch, follow all the best practices including validation of OS image, VM Size, and creating restore points. For the Advisor recommendation to be considered complete, follow the steps outlined in the Enable Trusted launch on an existing VM to upgrade the virtual machines security type and enable Trusted launch.

What if there is Generation 2 VMs, that doesn't fit the prerequisites for Trusted launch?

For a Generation 2 VM, that has not met the prerequisites to upgrade to Trusted launch, look how to fulfill the prerequisites. For example, If using a virtual machine size not supported, please look for an equivalent Trusted launch supported size that supports Trusted launch.

Note

Please dismiss the recommendation if Gen2 virtual machine is configured with VM size families which are currently not supported with Trusted launch like MSv2-series.