Skip to content

Commit 653cd85

Browse files
Merge pull request #228501 from cynthn/patch-45
Update create-vm-specialized-portal.md - freshness
2 parents b542906 + 8dcab4f commit 653cd85

File tree

1 file changed

+23
-14
lines changed

1 file changed

+23
-14
lines changed

articles/virtual-machines/windows/create-vm-specialized-portal.md

Lines changed: 23 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -7,14 +7,21 @@ ms.subservice: imaging
77
ms.collection: windows
88
ms.workload: infrastructure-services
99
ms.topic: how-to
10-
ms.date: 01/18/2019
10+
ms.date: 02/24/2023
1111
ms.author: cynthn
1212

1313
---
1414
# Create a VM from a VHD by using the Azure portal
1515

1616
**Applies to:** :heavy_check_mark: Windows VMs
1717

18+
19+
> [!NOTE]
20+
> Customers are encouraged to use Azure Compute Gallery as all new features like ARM64, Trusted Launch, and Confidential VM,are only supported through Azure Compute Gallery.  If you have an existing VHD or managed image, you can use it as a source and create an Azure Compute Gallery image. For more information, see [Create an image definition and image version](../image-version.md).
21+
>
22+
> Creating an image instead of just attaching a disk means you can create multiple VMs from the same sounrce disk.
23+
24+
1825
There are several ways to create a virtual machine (VM) in Azure:
1926

2027
- If you already have a virtual hard disk (VHD) to use or you want to copy the VHD from an existing VM to use, you can create a new VM by *attaching* the VHD to the new VM as an OS disk.
@@ -23,6 +30,8 @@ There are several ways to create a virtual machine (VM) in Azure:
2330

2431
- You can create an Azure VM from an on-premises VHD by uploading the on-premises VHD and attaching it to a new VM. You use PowerShell or another tool to upload the VHD to a storage account, and then you create a managed disk from the VHD. For more information, see [Upload a specialized VHD](create-vm-specialized.md#option-2-upload-a-specialized-vhd).
2532

33+
34+
2635
> [!IMPORTANT]
2736
>
2837
> When you use a [specialized](shared-image-galleries.md#generalized-and-specialized-images) disk to create a new VM, the new VM retains the computer name of the original VM. Other computer-specific information (e.g. CMID) is also kept and, in some cases, this duplicate information could cause issues. When copying a VM, be aware of what types of computer-specific information your applications rely on.
@@ -35,37 +44,37 @@ We recommend that you limit the number of concurrent deployments to 20 VMs from
3544

3645
Create a snapshot and then create a disk from the snapshot. This strategy allows you to keep the original VHD as a fallback:
3746

38-
1. From the [Azure portal](https://portal.azure.com), on the left menu, select **All services**.
39-
2. In the **All services** search box, enter **disks** and then select **Disks** to display the list of available disks.
47+
1. Open the [Azure portal](https://portal.azure.com).
48+
2. In the search box, enter **disks** and then select **Disks** to display the list of available disks.
4049
3. Select the disk that you would like to use. The **Disk** page for that disk appears.
4150
4. From the menu at the top, select **Create snapshot**.
4251
5. Choose a **Resource group** for the snapshot. You can use either an existing resource group or create a new one.
4352
6. Enter a **Name** for the snapshot.
44-
7. For **Snapshot type**, choose either **Full** or **Incremental**.
53+
7. For **Snapshot type**, choose **Full**.
4554
8. For **Storage type**, choose **Standard HDD**, **Premium SSD**, or **Zone-redundant** storage.
46-
9. When you're done, select **Create** to create the snapshot.
47-
10. After the snapshot has been created, select **Create a resource** in the left menu.
55+
9. When you're done, select **Review + create** to create the snapshot.
56+
10. After the snapshot has been created, select **Home** > **Create a resource**.
4857
11. In the search box, enter **managed disk** and then select **Managed Disks** from the list.
4958
12. On the **Managed Disks** page, select **Create**.
5059
13. Choose a **Resource group** for the disk. You can use either an existing resource group or create a new one. This selection will also be used as the resource group where you create the VM from the disk.
51-
14. Enter a **Name** for the disk.
60+
14. For **Region**, you must select the same region where the snapshot is located.
61+
15. Enter a **Name** for the disk.
5262
16. In **Source type**, ensure **Snapshot** is selected.
5363
17. In the **Source snapshot** drop-down, select the snapshot you want to use.
54-
18. For **Size**, choose either **Standard (HDD)** or **Premium (SSD)** storage.
55-
19. Make any other adjustments as needed and then select **Create** to create the disk.
64+
18. For **Size**, you can change the storage type and size as needed.
65+
19. Make any other adjustments as needed and then select **Review + create** to create the disk. Once validation passes, select **Create**.
5666

5767
## Create a VM from a disk
5868

5969
After you have the managed disk VHD that you want to use, you can create the VM in the portal:
6070

61-
1. From the [Azure portal](https://portal.azure.com), on the left menu, select **All services**.
62-
2. In the **All services** search box, enter **disks** and then select **Disks** to display the list of available disks.
71+
1. In the search box, enter **disks** and then select **Disks** to display the list of available disks.
6372
3. Select the disk that you would like to use. The **Disk** page for that disk opens.
64-
4. In the **Overview** page, ensure that **DISK STATE** is listed as **Unattached**. If it isn't, you might need to either detach the disk from the VM or delete the VM to free up the disk.
73+
4. In the **Essentials** section, ensure that **Disk state** is listed as **Unattached**. If it isn't, you might need to either detach the disk from the VM or delete the VM to free up the disk.
6574
4. In the menu at the top of the page, select **Create VM**.
6675
5. On the **Basics** page for the new VM, enter a **Virtual machine name** and either select an existing **Resource group** or create a new one.
6776
6. For **Size**, select **Change size** to access the **Size** page.
68-
7. Select a VM size row and then choose **Select**.
77+
7. The disk name should be pre-filled in the **Image** section.
6978
8. On the **Disks** page, you may notice that the "OS Disk Type" cannot be changed. This preselected value is configured at the point of Snapshot or VHD creation and will carry over to the new VM. If you need to modify disk type take a new snapshot from an existing VM or disk.
7079
9. On the **Networking** page, you can either let the portal create all new resources or you can select an existing **Virtual network** and **Network security group**. The portal always creates a new network interface and public IP address for the new VM.
7180
10. On the **Management** page, make any changes to the monitoring options.
@@ -76,4 +85,4 @@ After you have the managed disk VHD that you want to use, you can create the VM
7685

7786
## Next steps
7887

79-
You can also use PowerShell to [upload a VHD to Azure and create a specialized VM](create-vm-specialized.md).
88+
You can also [create an image definition and image version](../image-version.md) from your VHD.

0 commit comments

Comments
 (0)