Skip to content

Commit c499da6

Browse files
authored
Update capture-image-resource.md
1 parent 17b20bb commit c499da6

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

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

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,15 +17,15 @@ 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

3030
1. Go to the [Azure portal](https://portal.azure.com). Search for and select **Virtual machines**.
3131

@@ -46,7 +46,7 @@ After the image is created, you can find it as an **Image** resource in the list
4646

4747

4848

49-
## Create an image of a VM using PowerShell
49+
## Create a managed image of a VM using PowerShell
5050

5151
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.
5252

@@ -135,7 +135,7 @@ If you want to create an image of only the OS disk, specify the managed disk ID
135135
```
136136
137137
138-
## Create an image from a snapshot using PowerShell
138+
## Create a managed image from a snapshot using PowerShell
139139
140140
You can create a managed image from a snapshot of a generalized VM by following these steps:
141141
@@ -168,7 +168,7 @@ You can create a managed image from a snapshot of a generalized VM by following
168168
```
169169
170170
171-
## Create an image from a VM that uses a storage account
171+
## Create a managed image from a VM that uses a storage account
172172
173173
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*.
174174
@@ -204,3 +204,4 @@ To create a managed image from a VM that doesn't use managed disks, you need the
204204
205205
## Next steps
206206
- [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)