Skip to content

Commit 453d1dc

Browse files
authored
Merge pull request #197176 from igorpag/patch-1
update security-guide.md fta-emea-spring22
2 parents 3f78fb5 + 0a9a26d commit 453d1dc

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/virtual-desktop/security-guide.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,9 @@ By restricting operating system capabilities, you can strengthen the security of
148148

149149
Trusted launch are Gen2 Azure VMs with enhanced security features aimed to protect against “bottom of the stack” threats through attack vectors such as rootkits, boot kits, and kernel-level malware. The following are the enhanced security features of trusted launch, all of which are supported in Azure Virtual Desktop. To learn more about trusted launch, visit [Trusted launch for Azure virtual machines](../virtual-machines/trusted-launch.md).
150150

151+
>[!NOTE]
152+
>Bring your own custom image for Trusted Launch VM is not yet supported. When deploying an AVD Host Pool, you will be limited to the list of pre-canned OS images listed in the dropdown "Image" combo box.
153+
151154
### Secure Boot
152155

153156
Secure Boot is a mode that platform firmware supports that protects your firmware from malware-based rootkits and boot kits. This mode only allows signed OSes and drivers to start up the machine.

0 commit comments

Comments
 (0)