Deploy Trusted launch for Azure Arc VMs on Azure Stack HCI, version 23H2

Artikkel
02/27/2024

Applies to: Azure Stack HCI, version 23H2

This article describes how to deploy Trusted launch for Azure Arc virtual machines (VMs) on Azure Stack HCI, version 23H2.

Prerequisites

Make sure that you have access to an Azure Stack HCI, version 23H2 cluster that is deployed and registered with Azure. For more information, see deploy using the Azure portal.

Create a Trusted launch Arc VM

You can create a Trusted launch VM using Azure portal or by using Azure Command-Line Interface (CLI). Use the tabs below to select a method.

Azure portal
Azure CLI

To create a Trusted launch Arc VM on Azure Stack HCI, follow the steps in the Create Arc virtual machines on Azure Stack HCI using Azure portal, with the following changes:

While creating the VM, select Trusted launch virtual machines for security type.
Select a VM guest OS image from the list of supported images:
Once a VM is created, go to the VM properties page and verify the security type shown is Trusted launch.

To create a Trusted launch Arc VM on Azure Stack HCI, follow the steps in the Create Arc virtual machines on Azure Stack HCI using Azure CLI, with the following changes:

Create a VM image using a supported VM guest OS image by Trusted launch from Azure Marketplace. For more information, see Create Azure Stack HCI VM image using Azure Marketplace.

Create a VM using CLI as follows:

$vmName="<Name of the VM>" 
$subscription="<Subscription ID associated with your cluster>" 
$resourceGroup="<Resource group name for your cluster>" 
$location="<Location for your Azure Stack HCI cluster>" 
$customLocationID=(az customlocation show --resource-group $resource_group --name "<custom location name for HCI cluster>" --query id -o tsv) 
$guestName="<Name of the guest>" 
$userName="<Username for VM>" 
$password="<Password for VM>" 
$galleryImageName="<Name of VM guest image>" 
$vNic="<Name of virtual network interface>" 

az stack-hci-vm create --name $vmName --subscription $subscription --resource-group $resourceGroup --custom-location=$customLocationID --location $location --size="Default" --computer-name $guestName --admin-username $userName --admin-password $password --image $galleryImageName --nics $vNic --enable-secure-boot true --enable-vtpm true --security-type "TrustedLaunch"

Sample output:

{
  "extendedLocation": {
    "name": "/subscriptions/myhci-sub/resourceGroups/myhci-rg/Microsoft.ExtendedLocation/customLocations/myhci-cl",
    "type": "CustomLocation"
  },
  "id": "/subscriptions/myhci-sub/resourceGroups/myhci-rg/providers/Microsoft.HybridCompute/machines/tvm1/providers/Microsoft.AzureStackHCI/virtualMachineInstances/default",
  "name": "default",
  "properties": {
    "hardwareProfile": {
      "dynamicMemoryConfig": {
        "maximumMemoryMb": null,
        "minimumMemoryMb": null,
        "targetMemoryBuffer": null
      },
      "memoryMb": 4096,
      "processors": 4,
      "vmSize": "Custom"
    },
    "instanceView": {
      "vmAgent": {
        "statuses": []
      }
    },
    "networkProfile": {
      "networkInterfaces": [
        {
          "id": "ram-nic"
        }
      ]
    },
    "osProfile": {
      "adminPassword": null,
      "adminUsername": "admin",
      "computerName": "myhci-tvm",
      "linuxConfiguration": {
        "disablePasswordAuthentication": null,
        "provisionVmAgent": false,
        "provisionVmConfigAgent": false,
        "ssh": {
          "publicKeys": null
        }
      },
      "windowsConfiguration": {
        "enableAutomaticUpdates": null,
        "provisionVmAgent": false,
        "provisionVmConfigAgent": false,
        "ssh": {
          "publicKeys": null
        },
        "timeZone": null
      }
    },
    "provisioningState": "Succeeded",
    "securityProfile": {
      "enableTpm": true,
      "securityType": "TrustedLaunch",
      "uefiSettings": {
        "secureBootEnabled": true
      }
    },
    "status": {
      "powerState": "Running"
    },
    "storageProfile": {
      "dataDisks": [],
      "imageReference": {
        "id": "/subscriptions/myhci-sub/resourceGroups/myhci-rg/providers/Microsoft.AzureStackHCI/marketplacegalleryimages/Win11EntMulti21H2",
        "resourceGroup": "myhci-rg"
      },
      "osDisk": {
        "id": null,
        "osType": "Windows"
      },
      "storagepathId": null
    },
    "vmId": "myhci-tvm-1234567890"
  },
  "resourceGroup": "myhci-rg",
  "systemData": {
    "createdAt": "2023-10-24T19:15:47.152610+00:00",
    "createdBy": "registration@contoso.com",
    "createdByType": "User",
    "lastModifiedAt": "2023-10-24T19:41:05.196469+00:00",
    "lastModifiedBy": "319f651f-7ddb-4fc6-9857-7aef9250bd05",
    "lastModifiedByType": "Application"
  },
  "tags": null,
  "type": "microsoft.azurestackhci/virtualmachineinstances"
}

Once VM is created, verify the security type of the VM as Trusted launch.
Run the following cmdlet to find the owner node of the VM:
```
Get-ClusterGroup $vmName
```
Run the following cmdlet on the owner node of the VM:
```
(Get-VM $vmName).GuestStateIsolationType
```
Ensure a value of TrustedLaunch is returned.

Example

This example shows a Trusted launch Arc VM running Windows 11 guest with BitLocker encryption enabled. Here the steps to exercise the scenario:

Create a Trusted launch Arc VM running a supported Windows 11 guest operating system.
Enable BitLocker encryption for the OS volume on the Win 11 guest.

Sign in to the Windows 11 guest and enable BitLocker encryption (for the OS volume): In the search box on the task bar, type Manage BitLocker, and then select it from the list of results. Select Turn on BitLocker and then follow the instructions to encrypt the OS volume (C:). BitLocker will use vTPM as a key protector for the OS volume.

Migrate the VM to another node in the cluster. Run the following PowerShell command:

Move-ClusterVirtualMachineRole -Name $vmName -Node <destination node name> -MigrationType Shutdown

Confirm that the owner node of the VM is the specified destination node:
```
Get-ClusterGroup $vmName
```
After VM migration completes, verify if the VM is available and BitLocker is enabled.
Verify if you can log in to the Windows 11 guest in the VM, and if BitLocker encryption for the OS volume remains enabled. If you can do this, this confirms that the vTPM state was preserved during VM migration.

If vTPM state was not preserved during VM migration, VM startup would have resulted in BitLocker recovery during guest boot up. That is, you would have been prompted for the BitLocker recovery password when you attempted to log in to the Windows 11 guest. This was because the boot measurements (stored in the vTPM) of the migrated VM on the destination node were different from that of the original VM.
Force the VM to failover to another node in the cluster.
1. Confirm the owner node of the VM using this command:
```
Get-ClusterGroup $vmName
```
2. Use Failover Cluster Manager to stop the cluster service on the owner node as follows: Select the owner node as displayed in Failover Cluster Manager.  On the Actions right pane, select More Actions and then select Stop Cluster Service.
3. Stopping the cluster service on the owner node will cause the VM to be automatically migrated to another available node in the cluster. Restart the cluster service afterwards.
After failover completes, verify if the VM is available and BitLocker is enabled after failover.
Confirm that the owner node of the VM is the specified destination node:
```
Get-ClusterGroup $vmName
```

Next steps

Manage Trusted launch Arc VM guest state protection key.

Share via