Skip to content

Commit 6b3a577

Browse files
author
Ajay Kundnani
committed
Updated per acrolinx score
1 parent 311b619 commit 6b3a577

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

articles/virtual-machines/migration-managed-image-to-compute-gallery.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Migrate Managed image to Compute gallery
3-
description: Learn how to legacy Managed image to image version in Azure Compute Gallery
3+
description: Learn how to legacy Managed image to image version in Azure Compute Gallery.
44
author: AjKundnani
55
ms.service: virtual-machines
66
ms.subservice: gallery
@@ -13,44 +13,44 @@ ms.custom: template-how-to, devx-track-azurepowershell
1313

1414
# Migrate Managed image to Azure compute gallery image version
1515

16-
**Applies to:** :heavy_check_mark: Linux VM :heavy_check_mark: Windows VM :heavy_check_mark: Flex Scale Sets
16+
**Applies to:** :heavy_check_mark: Linux Virtual Machine :heavy_check_mark: Windows Virtual Machine :heavy_check_mark: Virtual Machine Flex Scale Sets
1717

18-
[Managed images](capture-image-resource.md) is legacy method to generalize and capture VM image. For the most current technology, customers are encouraged to use [Azure compute gallery](azure-compute-gallery.md). All new features, like ARM64, Trusted launch, and Confidential VM are only supported through Azure compute gallery. If you have an existing managed image, you can use it as a source and create an Azure compute gallery image.
18+
[Managed images](capture-image-resource.md) is legacy method to generalize and capture Virtual Machine image. For the most current technology, customers are encouraged to use [Azure compute gallery](azure-compute-gallery.md). All new features, like ARM64, Trusted launch, and Confidential Virtual Machine are only supported through Azure compute gallery. If you have an existing managed image, you can use it as a source and create an Azure compute gallery image.
1919

2020
## Before you begin
2121

22-
- [Create an Azure Compute Gallery](create-gallery.md)
23-
- Reader permission on source managed image.
24-
- Contributor permission on target Azure compute gallery image definition.
22+
- [Create an Azure Compute Gallery](create-gallery.md).
23+
- Assign `Reader` permission on source managed image.
24+
- Assign `Contributor` permission on target Azure compute gallery image definition.
2525

2626
## Migrate Managed image to Azure Compute Gallery image
2727

2828
### [Portal](#tab/portal)
2929

3030
This section steps through using the Azure portal to migrate Managed image to existing Azure Compute Gallery.
3131

32-
1. Log in to [Azure portal](https://portal.azure.com)
33-
2. Navigate to `Managed image` to be migrated and click **Clone to a VM image**.
32+
1. Sign-in to [Azure portal](https://portal.azure.com).
33+
2. Navigate to `Managed image` to be migrated and select **Clone to a VM image**.
3434

3535
:::image type="content" source="./media/shared-image-galleries/01-click-clone-image.png" alt-text="Screenshot of the Managed image to be migrated":::
3636

37-
3. Provide following details on the `Create VM image version` page and click **Next : Replication >**:
37+
3. Provide following details on the `Create VM image version` page and select **Next : Replication >**:
3838
- Version number
3939
- Target Azure compute gallery
40-
- Target VM image definition
40+
- Target Virtual Machine image definition
4141

42-
4. Select following `Replication` configuration or select default values and click **Next : Encryption >**:
42+
4. Select following `Replication` configuration or select default values and select **Next : Encryption >**:
4343
- Default storage sku
4444
- Default replication count
4545
- Target replication regions
4646

47-
5. Select `SSE encryption type` or select default `Encryption at-rest with a platform managed key` and click **Next : Tags >**.
47+
5. Select `SSE encryption type` or select default `Encryption at-rest with a platform managed key` and select **Next : Tags >**.
4848
6. *Optional* Assign resource tags.
49-
7. Validate the configuration on `Review + Create` page and click **Create** to complete the migration
49+
7. Validate the configuration on `Review + Create` page and select **Create** to complete the migration.
5050

5151
### [CLI](#tab/cli)
5252

53-
You will need the `tenantID` of the source image, the `subscriptionID` for the subscription where the new image will be stored (target), and the `resourceID` of the source image.
53+
You need the `tenantID` of the source image, the `subscriptionID` for the Azure compute gallery (target), and the `resourceID` of the source image.
5454

5555
```azurecli
5656
# Set some variables
@@ -79,7 +79,7 @@ az sig image-version create `
7979

8080
### [PowerShell](#tab/powershell)
8181

82-
You will need the `tenantID` of the source image, the `subscriptionID` for the subscription where the new image will be stored (target), and the `resourceID` of the source image.
82+
You need the `tenantID` of the source image, the `subscriptionID` for the Azure compute gallery (target), and the `resourceID` of the source image.
8383

8484
```azurepowershell
8585
# Set variables

0 commit comments

Comments
 (0)