Skip to content

Commit ce77ff1

Browse files
committed
fixing h2s
1 parent 681d37d commit ce77ff1

File tree

1 file changed

+10
-27
lines changed

1 file changed

+10
-27
lines changed

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

Lines changed: 10 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.author: cynthn
1111
ms.custom: legacy
1212

1313
---
14-
# Create a managed image of a generalized VM in Azure
14+
# Create a legacy managed image of a generalized VM in Azure
1515

1616
**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets
1717

@@ -26,26 +26,9 @@ For information on how managed images are billed, see [Managed Disks pricing](ht
2626

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

29-
## Create a managed image from a VM using the portal
3029

31-
1. Go to the [Azure portal](https://portal.azure.com). Search for and select **Virtual machines**.
30+
## CLI: Create a legacy managed image of a VM
3231

33-
2. Select your VM from the list.
34-
35-
3. In the **Virtual machine** page for the VM, on the upper menu, select **Capture**. The **Create an image** page appears.
36-
4. For **Share image to Azure compute gallery**, select **No, capture only a managed image.**
37-
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.
38-
39-
4. For **Name**, either accept the pre-populated name or type your own name for the image.
40-
41-
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**.
42-
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**.
43-
44-
8. Select **Create** to create the image.
45-
46-
After the image is created, you can find it as an **Image** resource in the list of resources in the resource group.
47-
48-
## Create a VM image using the CLI
4932
Create a managed image of the VM with [az image create](/cli/azure/image#az-image-create). The following example creates an image named *myImage* in the resource group named *myResourceGroup* using the VM resource named *myVM*.
5033

5134
```azurecli
@@ -64,7 +47,7 @@ az image create \
6447
This command returns JSON that describes the VM image. Save this output for later reference.
6548

6649

67-
## Create a managed image of a VM using PowerShell
50+
## PowerShell: Create a legacy managed image of a VM
6851

6952
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.
7053

@@ -113,7 +96,7 @@ To create a VM image, follow these steps:
11396
New-AzImage -Image $image -ImageName $imageName -ResourceGroupName $rgName
11497
```
11598
116-
## Create an image from a managed disk using PowerShell
99+
## PowerShell: Create a legacy managed image from a managed disk
117100
118101
If you want to create an image of only the OS disk, specify the managed disk ID as the OS disk:
119102
@@ -153,7 +136,7 @@ If you want to create an image of only the OS disk, specify the managed disk ID
153136
```
154137
155138
156-
## Create a managed image from a snapshot using PowerShell
139+
## PowerShell: Create a legacy managed image from a snapshot
157140
158141
You can create a managed image from a snapshot of a generalized VM by following these steps:
159142
@@ -186,7 +169,7 @@ You can create a managed image from a snapshot of a generalized VM by following
186169
```
187170
188171
189-
## PowerShell: Create a managed image from a VM that uses a storage account
172+
## PowerShell: Create a legacy managed image from a VM that uses a storage account
190173
191174
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*.
192175
@@ -220,7 +203,7 @@ To create a managed image from a VM that doesn't use managed disks, you need the
220203
```
221204
222205
223-
## CLI: Create a VM
206+
## CLI: Create a VM from a legacy managed image
224207
Create a VM by using the image you created with [az vm create](/cli/azure/vm). The following example creates a VM named *myVMDeployed* from the image named *myImage*.
225208
226209
```azurecli
@@ -232,7 +215,7 @@ az vm create \
232215
--ssh-key-value ~/.ssh/id_rsa.pub
233216
```
234217

235-
## CLI: Create a VM in another resource group
218+
## CLI: Create a VM in another resource group from a legacy managed image
236219

237220
You can create VMs from an image in any resource group within your subscription. To create a VM in a different resource group than the image, specify the full resource ID to your image. Use [az image list](/cli/azure/image#az-image-list) to view a list of images. The output is similar to the following example.
238221

@@ -254,7 +237,7 @@ az vm create \
254237
```
255238

256239

257-
## Portal: Create a VM
240+
## Portal: Create a VM from a legacy managed image
258241

259242
1. Go to the [Azure portal](https://portal.azure.com) to find a managed image. Search for and select **Images**.
260243
3. Select the image you want to use from the list. The image **Overview** page opens.
@@ -265,7 +248,7 @@ az vm create \
265248
8. On the summary page, you should see your image name listed as a **Private image**. Select **Ok** to start the virtual machine deployment.
266249

267250

268-
## PowerShell: Create a VM
251+
## PowerShell: Create a VM from a legacy managed image
269252

270253
You can use PowerShell to create a VM from an image by using the simplified parameter set for the [New-AzVm](/powershell/module/az.compute/new-azvm) cmdlet. The image needs to be in the same resource group where you'll create the VM.
271254

0 commit comments

Comments
 (0)