You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/devtest-labs/devtest-lab-add-vm.md
+16-19Lines changed: 16 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Create and add a virtual machine to a lab
2
+
title: Create and add a VM to a lab
3
3
description: Learn how to use the Azure portal to add a virtual machine (VM) to a lab in Azure DevTest Labs. Configure basic settings, artifacts, and advanced settings.
4
4
ms.topic: how-to
5
5
ms.author: rosemalcolm
@@ -12,9 +12,7 @@ ms.custom: UpdateFrequency2
12
12
13
13
# Create lab VMs in Azure DevTest Labs
14
14
15
-
This article describes how to create Azure virtual machines (VMs) in Azure DevTest Labs by using the Azure portal.
16
-
17
-
You can also create DevTest Labs VMs by using [PowerShell](devtest-lab-vm-powershell.md), [Azure CLI](devtest-lab-vmcli.md), an [ARM template](devtest-lab-use-resource-manager-template.md), or from a [shared image gallery](add-vm-use-shared-image.md).
15
+
This article describes how to create Azure virtual machines (VMs) in Azure DevTest Labs by using the Azure portal. You can also create DevTest Labs VMs by using [PowerShell](devtest-lab-vm-powershell.md), [Azure CLI](devtest-lab-vmcli.md), an [ARM template](devtest-lab-use-resource-manager-template.md), or from a [shared image gallery](add-vm-use-shared-image.md).
18
16
19
17
## Prerequisite
20
18
@@ -51,17 +49,17 @@ You can also create DevTest Labs VMs by using [PowerShell](devtest-lab-vm-powers
51
49
52
50
The default **Virtual machine size** that appears in **Basic Settings** depends on the **Image Base** architecture and the lab's **Allowed virtual machine** sizes.
53
51
54
-
-If the lab's **Configuration and policies** > **Allowed virtual machine sizes** policy allows **All sizes**:
55
-
- For an image base with x64 architecture, the default size is **D4s_v5**.
56
-
- For an image base with ARM64 architecture, the default size is **D4pls_v5**.
52
+
If the lab's **Configuration and policies** > **Allowed virtual machine sizes** policy allows **All sizes**:
53
+
- For an image base with x64 architecture, the default size is **D4s_v5**.
54
+
- For an image base with Arm64 architecture, the default size is **D4pls_v5**.
57
55
58
-
-If the lab's **Configuration and policies** > **Allowed virtual machine sizes** policy allows only limited **Selected sizes**:
59
-
- If **D4s_v5** VM size is allowed, the default size is **D4s_v5** for an image base with x64 architecture.
60
-
- If **D4pls_v5** VM size is allowed, the default size is **D4pls_v5** for an image base with ARM64 architecture.
61
-
- If **D4s_v5** size isn't allowed for x64 architectures, or **D4pls_v5** size isn't allowed for ARM64 architectures:
62
-
- If a 4-core non-premium CPU size is available, the first available 4-core non-premium CPU size is selected.
63
-
- If no 4-core non-premium CPU size is available, the first available 4-core CPU size is selected.
64
-
- If no 4-core CPU size is available, the first available CPU size is selected.
56
+
If the lab's **Configuration and policies** > **Allowed virtual machine sizes** policy allows only limited **Selected sizes**:
57
+
- If **D4s_v5** VM size is allowed, the default size is **D4s_v5** for an image base with x64 architecture.
58
+
- If **D4pls_v5** VM size is allowed, the default size is **D4pls_v5** for an image base with Arm64 architecture.
59
+
- If **D4s_v5** size isn't allowed for x64 architectures, or **D4pls_v5** size isn't allowed for Arm64 architectures:
60
+
- If a 4core nonpremium CPU size is available, the first available 4core nonpremium CPU size is selected.
61
+
- If no 4core nonpremium CPU size is available, the first available 4core CPU size is selected.
62
+
- If no 4core CPU size is available, the first available CPU size is selected.
65
63
66
64
<aname="add-artifacts-during-installation"></a>
67
65
<aname="add-optional-artifacts"></a>
@@ -84,7 +82,7 @@ To add or configure artifacts during VM creation:
84
82
85
83
To add artifacts to VMs after VM creation, see [Add artifacts to VMs after creation](add-artifact-vm.md#add-artifacts-to-vms-from-the-azure-portal). For more information about adding artifacts, see [Add artifacts to DevTest Labs VMs](add-artifact-vm.md).
1. Optionally, select the **Advanced Settings** tab on the **Create lab resource** screen, and change any of the following values:
@@ -95,7 +93,7 @@ To add artifacts to VMs after VM creation, see [Add artifacts to VMs after creat
95
93
-**Expiration date**: Leave at **Will not expire**, or [set an expiration date](devtest-lab-use-resource-manager-template.md#set-vm-expiration-date) and time for the VM.
96
94
-**Make this machine claimable**: Leave at **No** to keep yourself as the owner of the VM. Select **Yes** to make the VM claimable by any lab user after creation. For more information, see [Create and manage claimable VMs](devtest-lab-add-claimable-vm.md).
97
95
-**Number of instances**: To create more than one VM with this configuration, enter the number of VMs to create.
98
-
-**View ARM template**: Select this button to view and save the VM configuration as an Azure Resource Manager (ARM) template. You can use the ARM template to [deploy new VMs](/azure/azure-resource-manager/templates/overview.md).
96
+
-**View ARM template**: Select this button to view and save the VM configuration as an Azure Resource Manager (ARM) template. You can use the ARM template to [deploy new VMs](/azure/azure-resource-manager/templates/overview).
99
97
100
98
:::image type="content" source="./media/devtest-lab-add-vm/portal-lab-vm-advanced-settings.png" alt-text="Screenshot that shows the VM Advanced Settings page.":::
101
99
@@ -113,7 +111,7 @@ Or, if you chose **Make this machine claimable** during VM creation, select **Cl
113
111
114
112
When you create a VM in DevTest Labs, you automatically have permission to access that VM, and you can see the VM listed both on the lab **Overview** page and the **All resources** page.
115
113
116
-
DevTest Labs users in the **Owner** and **Contributor** roles can see all lab VMs on the lab's **All Resources** page. Users in the **DevTest Labs User** role don't automatically have read access to VM resources that other users have created, so they don't see those VMs on the **All resources** page.
114
+
DevTest Labs users in the **Owner** and **Contributor** roles can see all lab VMs on the lab's **All Resources** page. Users in the **DevTest Labs User** role can't automatically access VM resources that other users created, so they don't see those VMs on the **All resources** page.
117
115
118
116
## Copy existing Azure VMs into a lab
119
117
@@ -123,9 +121,8 @@ You can copy existing VMs to DevTest Labs as follows:
123
121
1. Use the VHD file to [create a custom image](devtest-lab-create-template.md) in your lab.
124
122
1. Create a lab VM from your custom image.
125
123
126
-
<aname="add-artifacts-after-installation"></a>
127
124
## Related content
128
125
129
126
- For information about creating labs, see [Create a lab in the Azure portal](devtest-lab-create-lab.md).
130
-
- Explore the DevTest Labs public repositories of [artifacts](https://github.com/Azure/azure-devtestlab/tree/master/Artifacts), [environments](https://github.com/Azure/azure-devtestlab/tree/master/Environments), and [QuickStart ARM templates](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates).
127
+
- Explore the [artifacts](https://github.com/Azure/azure-devtestlab/tree/master/Artifacts), [environments](https://github.com/Azure/azure-devtestlab/tree/master/Environments), and [QuickStart ARM templates](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates)DevTest Labs public repositories.
Copy file name to clipboardExpand all lines: articles/devtest-labs/devtest-lab-concepts.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ A DevTest Labs lab is the infrastructure that encompasses a group of resources s
29
29
30
30
### Roles
31
31
32
-
[Azure role-based access control (Azure RBAC)](/azure/role-based-access-control/overview) defines DevTest Labs access and roles. DevTest Labs has three roles that define lab member permissions: **Owner**, **Contributor**, and **DevTest Labs User**.
32
+
[Azure role-based access control (RBAC)](/azure/role-based-access-control/overview) defines DevTest Labs access and roles. DevTest Labs has three roles that define lab member permissions: **Owner**, **Contributor**, and **DevTest Labs User**.
33
33
34
34
- Lab **Owners** can do all lab tasks, including creating labs and managing policies and users. For more information about managing user access and roles, see [Add lab owners, contributors, and users](devtest-lab-add-devtest-user.md).
35
35
@@ -53,7 +53,7 @@ You can use ARM templates to create and update DevTest Labs labs, environments,
53
53
54
54
[!INCLUDE [About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)] For more information about ARM template structure and properties, see [Template format](/azure/azure-resource-manager/templates/syntax#template-format).
55
55
56
-
For more information about using ARM templates in DevTestLabs, see:
56
+
For more information about using ARM templates in DevTest Labs, see:
57
57
58
58
-[Create labs from ARM templates](create-lab-windows-vm-template.md)
59
59
-[Create environments from ARM templates](devtest-lab-create-environment-from-arm.md)
@@ -105,6 +105,6 @@ For more information about custom images and formulas, see [Compare custom image
105
105
106
106
## Environments
107
107
108
-
A DevTest Labs environment is a collection of Azure platform-as-a-service (PaaS) resources, such as an Azure Web App or a SharePoint farm, that's defined by an ARM template. Lab administrators can add public or privately created environment tamplates to labs, and lab users can use them to quickly create environments. For more information, see [Use ARM templates to create DevTest Labs environments](devtest-lab-create-environment-from-arm.md).
108
+
A DevTest Labs environment is a collection of Azure platform-as-a-service (PaaS) resources, such as an Azure Web App or a SharePoint farm, thatan ARM template defines. Lab administrators can add public or privately created environment templates to labs, and lab users can use them to quickly create environments. For more information, see [Use ARM templates to create DevTest Labs environments](devtest-lab-create-environment-from-arm.md).
Copy file name to clipboardExpand all lines: articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,12 +16,12 @@ ms.custom: UpdateFrequency2
16
16
17
17
In this article, you learn how to use Azure Storage Explorer to upload a virtual hard disk (VHD) file to a lab storage account in Azure DevTest Labs. Storage Explorer is a standalone app that runs on Windows, macOS, and Linux. After you upload your VHD file to your lab, you can create a custom image from the uploaded file and use the image to create lab virtual machines (VMs).
18
18
19
-
Storage Explorer supports several connection options. This article describes how to connect to a storage account that's associated with your Azure subscription. For information about other Storage Explorer connection options, see [Get started with Storage Explorer](/azure/vs-azure-tools-storage-manage-with-storage-explorer).
19
+
Storage Explorer supports several connection options. This article describes how to connect to a storage account associated with your Azure subscription. For information about other Storage Explorer connection options, see [Get started with Storage Explorer](/azure/vs-azure-tools-storage-manage-with-storage-explorer).
20
20
21
21
## Prerequisites
22
22
23
23
- Write access to a lab in DevTest Labs.
24
-
- A VHD or VHDX virtual hard disk file to upload.
24
+
- A VHD or virtual hard disk v2 (VHDX) virtual hard disk file to upload.
25
25
- The [latest version of Storage Explorer](https://www.storageexplorer.com) installed.
26
26
27
27
## Upload a VHD file to a lab
@@ -59,7 +59,7 @@ When you open Storage Explorer, the Explorer pane shows all the Azure subscripti
59
59
60
60
:::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/upload-dir.png" alt-text="Screenshot that shows the expanded Blob Containers node with the uploads directory.":::
61
61
62
-
1. In the Storage Explorer right pane, on the blob editor toolbar, select **Upload**, and then select**Upload Files**.
62
+
1. In the Storage Explorer right pane, on the blob editor toolbar, select **Upload** >**Upload Files**.
63
63
64
64
:::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/upload-button.png" alt-text="Screenshot that shows the Upload button and Upload Files.":::
65
65
@@ -73,7 +73,7 @@ When you open Storage Explorer, the Explorer pane shows all the Azure subscripti
73
73
74
74
:::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/upload-status.png" alt-text="Screenshot that shows the Activities pane with upload status.":::
75
75
76
-
After you upload the VHD file, you can see it in your lab storage account in the Azure portal.
76
+
After the VHD file uploads, you can see it in your lab storage account in the Azure portal.
77
77
78
78
1. Open your lab storage account by searching for and selecting it in the Azure Search bar, or by selecting it from **Storage accounts**.
79
79
1. On the storage account's **Overview** page, select **Data storage** > **Containers** from the left navigation.
0 commit comments