Skip to content

Commit ffee840

Browse files
committed
Updated text
1 parent 271bc18 commit ffee840

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

azure-local/manage/trusted-launch-vm-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Trusted launch is a security type that can be specified when creating Azure Loca
3636

3737
- IgvmAgent is a component that is installed on all machines in the Azure Local system. It enables support for isolated VMs like Trusted launch for Azure Local VMs, for example.
3838

39-
- Trusted launch for Azure Local VMs uses only a subset of images on Azure Local. When you create Azure Local VMs and want to use Trusted launch, ensure your images are available on your cluster. If the images aren't available, the dropdown list during the creation process will be blank. This is by design. For information on which images work for Trusted launch VMs, see [Guest operating system images](#guest-operating-system-images).
39+
- Trusted launch for Azure Local VMs uses only a subset of images on Azure Local. When you create Azure Local VMs and want to use Trusted launch, ensure your images are available on your cluster. If the images aren't available, the dropdown lists during the creation process will be blank. This is by design. For information on which images work for Trusted launch VMs, see [Guest operating system images](#guest-operating-system-images).
4040

4141
- As part of Trusted launch for Azure Local VM creation, Hyper-V creates VM files at a default location on disk to store the VM state. By default, access to those VM files is restricted to host server administrators only. If you store those VM files in a different location, you must ensure that the location is access restricted to host server administrators only.
4242

0 commit comments

Comments
 (0)