Skip to content

Commit 2016f0b

Browse files
committed
Updated text
1 parent f7b3843 commit 2016f0b

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: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,9 +65,9 @@ sections:
6565
No. Azure Local VMs can be managed by Azure CLI or Azure portal. In either case, no fee is charged. Some VM extensions might have a fee.
6666
6767
- question: |
68-
Why is my image drop-down list blank when creating my Azure Local VM using Trusted launch?
68+
Why are my image dropdown lists blank when creating my Azure Local VM using Trusted launch?
6969
answer: |
70-
When you create an Azure Local VM using Trusted launch, your image must be available on your cluster. If your image isn't available, the drop-down 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](/azure/azure-local/manage/trusted-launch-vm-overview?view=azloc-24113#guest-operating-system-images).
70+
When you create an Azure Local VM using Trusted launch, your image must be available on your cluster. If your image isn'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](/trusted-launch-vm-overview.md#guest-operating-system-images).
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 drop-down 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+
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).
2121

2222
## Failure when trying to enable guest management
2323

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 drop-down 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 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).
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)