Skip to content

Commit dfd9b58

Browse files
committed
Updated text
1 parent f04bf4b commit dfd9b58

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

azure-local/manage/azure-arc-vms-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ sections:
6767
- question: |
6868
When creating an Azure Local VM via Azure portal, why does the image dropdown shows a blank list, when I choose security type as Trusted launch?
6969
answer: |
70-
Trusted launch Azure Local VMs currently support only select images from Azure Marketplace. See [Guest operating system images](./trusted-launch-vm-overview.md#guest-operating-system-images) for a list of supported images. When creating a Trusted launch Azure Local VM in the Azure portal, the image dropdown list shows only images supported by Trusted launch. If you select any image, including a custom image, that isn't supported, the image dropdown list will be blank. If none of the images available on your Azure Local system are supported by Trusted launch, the image dropdown list will also be blank.
70+
Trusted launch Azure Local VMs currently support only select images from Azure Marketplace. For a list of supported images, see [Guest operating system images](./trusted-launch-vm-overview.md#guest-operating-system-images). When you create a Trusted launch Azure Local VM in the Azure portal, the image dropdown list shows only images supported by Trusted launch. If you select any image, including a custom image, that isn't supported, the image dropdown list is blank. If none of the images available on your Azure Local system are supported by Trusted launch, the image dropdown list is also blank.
7171
7272
- question: |
7373
Can I use the same name for gallery image projections and do existing VMs use the new image?

azure-local/manage/troubleshoot-arc-enabled-vms.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article describes how to collect logs and troubleshoot issues with Azure Lo
1717

1818
## Unable to select an image for Trusted launch VMs
1919

20-
When you create an Azure Local VM, your image must be available on your cluster. If your image isn't available, the dropdown lists for options like security type and image will appear blank during the creation process. This is by design. For information on which images work for Trusted launch VMs, see [Guest operating system images](./trusted-launch-vm-overview.md#guest-operating-system-images).
20+
Trusted launch Azure Local VMs currently support only select images from Azure Marketplace. For a list of supported images, see [Guest operating system images](./trusted-launch-vm-overview.md#guest-operating-system-images). When you create a Trusted launch Azure Local VM in the Azure portal, the image dropdown list shows only images supported by Trusted launch. If you select any image that isn't supported, including a custom image, the image dropdown list is blank. If none of the images available on your Azure Local system are supported by Trusted launch, the image dropdown list is also blank.
2121

2222
## Failure when trying to enable guest management
2323

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article introduces Trusted launch for Azure Local virtual machines (VMs) en
1818

1919
Trusted launch for Azure Local VMs enables secure boot, installs a virtual Trusted Platform Module (vTPM) device, automatically transfers the vTPM state when the VM migrates or fails over to another machine within the system, and supports the ability to attest whether the VM started in a known good state.
2020

21-
Trusted launch is a security type that can be specified when creating Azure Local VMs. For more information, see [Trusted launch for Azure Local VMs enabled by Azure Arc](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/trusted-launch-for-azure-arc-vms-on-azure-stack-hci-version-23h2/ba-p/3978051).
21+
Trusted launch is a security type that can be specified when you create Azure Local VMs. For more information, see [Trusted launch for Azure Local VMs enabled by Azure Arc](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/trusted-launch-for-azure-arc-vms-on-azure-stack-hci-version-23h2/ba-p/3978051).
2222

2323
## Capabilities and benefits
2424

@@ -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 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).
39+
- Trusted launch Azure Local VMs currently support only select images from Azure Marketplace. For a list of supported images, see [Guest operating system images](./trusted-launch-vm-overview.md#guest-operating-system-images). When you create a Trusted launch Azure Local VM in the Azure portal, the image dropdown list shows only images supported by Trusted launch. If you select any image that isn't supported, including a custom image, the image dropdown list is blank. If none of the images available on your Azure Local system are supported by Trusted launch, the image dropdown list is also blank.
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)