Skip to content

Commit 8c99758

Browse files
authored
Update trusted-launch-portal.md
Updated generalize.md to generalize.yml
1 parent 0d0fa44 commit 8c99758

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/virtual-machines/trusted-launch-portal.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Deploy a trusted launch VM
33
description: Deploy a VM that uses trusted launch.
4-
author: lakmeedee
4+
author: howieasmerom
55
ms.author: howieasmerom
66
ms.reviewer: jushiman
77
ms.service: virtual-machines
@@ -373,7 +373,7 @@ The resulting image version can be used only to create Azure Trusted launch VMs.
373373
2. To create an Azure Compute Gallery Image from a VM, open an existing Trusted launch VM and select **Capture**.
374374
3. In the Create an Image page that follows, allow the image to be shared to the gallery as a VM image version. Creation of Managed Images isn't supported for Trusted Launch VMs.
375375
4. Create a new target Azure Compute Gallery or select an existing gallery.
376-
5. Select the **Operating system state** as either **Generalized** or **Specialized**. If you want to create a generalized image, ensure that you [generalize the VM to remove machine specific information](generalize.md) before selecting this option. If Bitlocker based encryption is enabled on your Trusted launch Windows VM, you may not be able to generalize the same.
376+
5. Select the **Operating system state** as either **Generalized** or **Specialized**. If you want to create a generalized image, ensure that you [generalize the VM to remove machine specific information](generalize.yml) before selecting this option. If Bitlocker based encryption is enabled on your Trusted launch Windows VM, you may not be able to generalize the same.
377377
6. Create a new image definition by providing a name, publisher, offer, and SKU details. The **Security Type** of the image definition should already be set to **Trusted launch**.
378378
7. Provide a version number for the image version.
379379
8. Modify replication options if necessary.
@@ -426,7 +426,7 @@ az sig image-definition create --resource-group MyResourceGroup --location eastu
426426
--features SecurityType=TrustedLaunch
427427
```
428428

429-
To create an image version, we can capture an existing Linux based Trusted launch VM. [Generalize the Trusted launch VM](generalize.md) before creating the image version.
429+
To create an image version, we can capture an existing Linux based Trusted launch VM. [Generalize the Trusted launch VM](generalize.yml) before creating the image version.
430430

431431
```azurecli-interactive
432432
az sig image-version create --resource-group MyResourceGroup \
@@ -470,7 +470,7 @@ $features = @($SecurityType)
470470
New-AzGalleryImageDefinition -ResourceGroupName $rgName -GalleryName $galleryName -Name $galleryImageDefinitionName -Location $location -Publisher $publisherName -Offer $offerName -Sku $skuName -HyperVGeneration "V2" -OsState "Generalized" -OsType "Windows" -Description $description -Feature $features
471471
```
472472

473-
To create an image version, we can capture an existing Windows based Trusted launch VM. [Generalize the Trusted launch VM](generalize.md) before creating the image version.
473+
To create an image version, we can capture an existing Windows based Trusted launch VM. [Generalize the Trusted launch VM](generalize.yml) before creating the image version.
474474

475475
```azurepowershell-interactive
476476
$rgName = "MyResourceGroup"

0 commit comments

Comments
 (0)