Skip to content

Commit 9b7a567

Browse files
authored
Merge pull request #189633 from cynthn/patch-589
Update capture-image-resource.md - https://dev.azure.com/mseng/TechnicalContent/_workitems/edit/1908216
2 parents 14f6d22 + c499da6 commit 9b7a567

File tree

1 file changed

+13
-17
lines changed

1 file changed

+13
-17
lines changed

articles/virtual-machines/windows/capture-image-resource.md

Lines changed: 13 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: virtual-machines
66
ms.subservice: imaging
77
ms.workload: infrastructure-services
88
ms.topic: how-to
9-
ms.date: 09/27/2018
9+
ms.date: 02/24/2022
1010
ms.author: cynthn
1111
ms.custom: legacy
1212
ms.collection: windows
@@ -17,41 +17,36 @@ ms.collection: windows
1717
**Applies to:** :heavy_check_mark: Windows VMs
1818

1919

20-
A managed image resource can be created from a generalized virtual machine (VM) that is stored as either a managed disk or an unmanaged disk in a storage account. The image can then be used to create multiple VMs. For information on how managed images are billed, see [Managed Disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/).
20+
Managed images are helpful in development and test environments where you need a consistent baseline VM. A managed image resource can be created from a generalized virtual machine (VM) that is stored as either a managed disk or an unmanaged disk in a storage account. The image can then be used to create multiple VMs. For information on how managed images are billed, see [Managed Disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/).
2121

2222
One managed image supports up to 20 simultaneous deployments. Attempting to create more than 20 VMs concurrently, from the same managed image, may result in provisioning timeouts due to the storage performance limitations of a single VHD. To create more than 20 VMs concurrently, use an [Azure Compute Gallery](../shared-image-galleries.md) (formerly known as Shared Image Gallery) image configured with 1 replica for every 20 concurrent VM deployments.
2323

2424
## Prerequisites
2525

2626
You need a [generalized](../generalize.md) VM in order to create an image.
2727

28-
## Create a managed image in the portal
28+
## Create a managed image from a VM using the portal
2929

30-
1. Go to the [Azure portal](https://portal.azure.com) to manage the VM image. Search for and select **Virtual machines**.
30+
1. Go to the [Azure portal](https://portal.azure.com). Search for and select **Virtual machines**.
3131

3232
2. Select your VM from the list.
3333

34-
3. In the **Virtual machine** page for the VM, on the upper menu, select **Capture**.
34+
3. In the **Virtual machine** page for the VM, on the upper menu, select **Capture**. The **Create an image** page appears.
35+
4. For **Share image to Azure compute gallery**, select **No, capture only a managed image.**
36+
5. For **Resource Group**, you can either create the image in the same resource group as the VM or select another resource group in your subscription.
3537

36-
The **Create image** page appears.
37-
38-
4. For **Name**, either accept the pre-populated name or enter a name that you would like to use for the image.
39-
40-
5. For **Resource group**, either select **Create new** and enter a name, or select a resource group to use from the drop-down list.
38+
4. For **Name**, either accept the pre-populated name or type your own name for the image.
4139

4240
6. If you want to delete the source VM after the image has been created, select **Automatically delete this virtual machine after creating the image**.
43-
44-
7. If you want the ability to use the image in any [availability zone](../../availability-zones/az-overview.md), select **On** for **Zone resiliency**.
41+
7. 7. If you want the ability to use the image in any [availability zone](../../availability-zones/az-overview.md), select **On** for **Zone resiliency**.
4542

4643
8. Select **Create** to create the image.
4744

4845
After the image is created, you can find it as an **Image** resource in the list of resources in the resource group.
4946

5047

5148

52-
## Create an image of a VM using PowerShell
53-
54-
49+
## Create a managed image of a VM using PowerShell
5550

5651
Creating an image directly from the VM ensures that the image includes all of the disks associated with the VM, including the OS disk and any data disks. This example shows how to create a managed image from a VM that uses managed disks.
5752

@@ -140,7 +135,7 @@ If you want to create an image of only the OS disk, specify the managed disk ID
140135
```
141136
142137
143-
## Create an image from a snapshot using PowerShell
138+
## Create a managed image from a snapshot using PowerShell
144139
145140
You can create a managed image from a snapshot of a generalized VM by following these steps:
146141
@@ -173,7 +168,7 @@ You can create a managed image from a snapshot of a generalized VM by following
173168
```
174169
175170
176-
## Create an image from a VM that uses a storage account
171+
## Create a managed image from a VM that uses a storage account
177172
178173
To create a managed image from a VM that doesn't use managed disks, you need the URI of the OS VHD in the storage account, in the following format: https://*mystorageaccount*.blob.core.windows.net/*vhdcontainer*/*vhdfilename.vhd*. In this example, the VHD is in *mystorageaccount*, in a container named *vhdcontainer*, and the VHD filename is *vhdfilename.vhd*.
179174
@@ -209,3 +204,4 @@ To create a managed image from a VM that doesn't use managed disks, you need the
209204
210205
## Next steps
211206
- [Create a VM from a managed image](create-vm-generalized-managed.md).
207+
- Learn more about using an [Azure Compute Gallery](../shared-image-galleries.md) (formerly known as Shared Image Gallery)

0 commit comments

Comments
 (0)