Skip to content

Commit 4cb6562

Browse files
author
Ajay Kundnani
committed
Updated disclaimer on TL page
1 parent 31d3014 commit 4cb6562

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/virtual-machines/trusted-launch.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,10 @@ ms.custom: template-concept; references_regions
1818
Azure offers trusted launch as a seamless way to improve the security of [generation 2](generation-2.md) VMs. Trusted launch protects against advanced and persistent attack techniques. Trusted launch is composed of several, coordinated infrastructure technologies that can be enabled independently. Each technology provides another layer of defense against sophisticated threats.
1919

2020
> [!IMPORTANT]
21+
>
2122
> - Trusted Launch is selected as the default state for newly created Azure VMs. If your new VM requires features which are not supported by trusted launch, see the [Trusted Launch FAQs](trusted-launch-faq.md)
22-
> - Existing [Azure Generation 2 VMs](generation-2.md) can have trusted launch enabled after being created. For more information, see **[Enable Trusted Launch on existing VMs](trusted-launch-existing-vm.md)**
23-
> - You cannot enable trusted launch on an existing virtual machine scale set (VMSS) that was initially created without it. Trusted launch requires the creation of new VMSS.
23+
> - Existing [Virtual machines](overview.md) can have trusted launch enabled after being created. For more information, see **[Enable Trusted Launch on existing VMs](trusted-launch-existing-vm.md)**
24+
> - Existing [Virtual machine scale sets](../virtual-machine-scale-sets/overview.md) can have trusted launch enabled after being created. For more information, see **[Enable Trusted launch on existing scale sets](trusted-launch-existing-vmss.md)**.
2425
2526
## Benefits
2627

0 commit comments

Comments
 (0)