Skip to content

Commit 890c9e6

Browse files
committed
edits
1 parent aa55f48 commit 890c9e6

File tree

12 files changed

+56
-42
lines changed

12 files changed

+56
-42
lines changed

articles/devtest-labs/add-artifact-vm.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ ms.custom: devx-track-azurepowershell, UpdateFrequency2
1414

1515
This article describes how to add *artifacts* to Azure DevTest Labs virtual machines (VMs). Artifacts are tools, actions, or software you can add to lab VMs. For example, artifacts can run Windows PowerShell scripts or Bash commands, install tools or applications, or take other actions like joining a domain.
1616

17-
DevTest Labs artifacts can come from the [public DevTest Labs Git repository](https://github.com/Azure/azure-devtestlab/tree/master/Artifacts) or from private Git repositories. Lab users can [create their own custom artifacts](devtest-lab-artifact-author.md) and store them in a repository, or use parameters to customize artifacts for their own needs.
17+
DevTest Labs artifacts can come from the [public DevTest Labs Git repository](https://github.com/Azure/azure-devtestlab/tree/master/Artifacts) or from private Git repositories. Lab users can [create their own custom artifacts](devtest-lab-artifact-author.md) and store them in a repository, and use parameters to customize existing artifacts for their own needs.
1818

1919
A lab administrator can [add artifact repositories to a lab](add-artifact-repository.md) so all lab users can access them. Lab administrators can also [specify mandatory artifacts to be installed on all lab VMs](devtest-lab-mandatory-artifacts.md) at creation.
2020

21-
You can't change or remove mandatory artifacts at VM creation time, but you can add and configure other available individual artifacts at or after creation time. This article describes how to add available artifacts to VMs by using the Azure portal or Azure PowerShell.
21+
You can't change or remove mandatory artifacts at VM creation time, but you can add and configure other available artifacts at or after VM creation time. This article describes how to add available artifacts to VMs by using the Azure portal or Azure PowerShell.
2222

2323
## Prerequisites
2424

@@ -38,7 +38,7 @@ You can't change or remove mandatory artifacts at VM creation time, but you can
3838
## Add artifacts to VMs
3939

4040
# [Azure portal](#tab/portal)
41-
41+
<a name="add-artifacts-to-vms-from-the-azure-portal"></a>
4242
You can use the Azure portal to add artifacts during VM creation or to add artifacts to an existing lab VM.
4343

4444
### Add artifacts during VM creation
@@ -54,12 +54,13 @@ You can use the Azure portal to add artifacts during VM creation or to add artif
5454

5555
1. By default, artifacts install in the order you add them. To rearrange the order, select the ellipsis **...** next to the artifact in the **Selected artifacts** list, and select **Move up**, **Move down**, **Move to top**, or **Move to bottom**.
5656

57-
- To edit an artifact's parameters after you add it, select the pencil icon, or select **...** next to the artifact and select **Edit**, to reopen the **Add artifact** pane.
57+
- To edit an artifact's parameters after you add it, select the pencil icon or select **...** next to the artifact and select **Edit** to reopen the **Add artifact** pane.
58+
5859
- To delete an artifact from the **Selected artifacts** list, select **...** and then select **Delete**.
5960

6061
1. When you're done adding, arranging, and configuring artifacts, select **OK** on the **Add artifacts** page.
6162
1. The **Artifacts** section of the **Create lab resource** screen shows the number of artifacts added. To add, edit, rearrange, or delete the artifacts before you create the VM, select **Add or Remove Artifacts** again.
62-
1. Optionally configure any **Advanced Settings** or **Tags**, and then select **Create** and **Create** again at the bottom of the **Create lab resource** screen to create the VM.
63+
1. Optionally configure any **Advanced Settings** or **Tags**, and then select **Create** and **Create** again at the bottom of the **Create lab resource** screen to create the VM with added artifacts.
6364

6465
After you create the VM, the installed artifacts appear on the VM's **Artifacts** page. To see details about each artifact's installation, select the artifact name.
6566

articles/devtest-labs/connect-virtual-machine-through-browser.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,22 @@
11
---
2-
title: Connect to lab VMs through Bastion
3-
description: Learn how to connect to Azure DevTest Labs virtual machines (VMs) in a browser if Bastion is enabled for the lab.
2+
title: Connect to lab VMs through a browser
3+
description: Learn how to connect to Azure DevTest Labs virtual machines (VMs) through an internet browser if Bastion is enabled for the lab.
44
ms.topic: how-to
55
ms.author: rosemalcolm
66
author: RoseHJM
77
ms.date: 03/24/2023
88
ms.custom: UpdateFrequency2
9+
10+
#customer intent: As a lab user, I want to connect to Bastion-enabled lab VMs through my browser, so I can connect securely without using public IP addresses or exposing RDP or SSH ports to the internet.
911
---
1012

11-
# Connect to lab VMs in a browser via Azure Bastion
13+
# Connect to lab VMs through a browser via Azure Bastion
1214

13-
This article describes how to connect to DevTest Labs virtual machines (VMs) through a browser by using [Azure Bastion](/azure/bastion/index). Bastion provides secure remote desktop protocol (RDP) or secure shell (SSH) access without using public IP addresses or exposing RDP or SSH ports to the internet.
15+
This article describes how to connect to your DevTest Labs virtual machines (VMs) through a browser by using [Azure Bastion](/azure/bastion/index). Bastion provides secure remote desktop protocol (RDP) or secure shell (SSH) access without using public IP addresses or exposing RDP or SSH ports to the internet.
1416

1517
> [!IMPORTANT]
16-
> The lab must be in an Azure Bastion-configured virtual network that has Bastion connections enabled. For more information, see [Enable browser connection to DevTest Labs VMs with Azure Bastion](enable-browser-connection-lab-virtual-machines.md).
18+
> The VM and lab must be in an Azure Bastion-configured virtual network that has Bastion connections enabled. For more information, see [Enable browser connection to DevTest Labs VMs with Azure Bastion](enable-browser-connection-lab-virtual-machines.md).
19+
> You must have ownership or sign-in permissions on the VM.
1720
1821
To connect to a lab VM through a browser:
1922

articles/devtest-labs/devtest-lab-add-devtest-user.md

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,14 @@ author: RoseHJM
77
ms.date: 03/24/2025
88
ms.custom: devx-track-azurepowershell, UpdateFrequency2
99

10-
#customer intent: As a lab owner, I want to add and configure users for my lab so I can grant only the access necessary to do specific lab tasks.
10+
#customer intent: As a lab owner, I want to add and configure users for my lab so I can grant the access necessary to do specific lab tasks.
1111
---
1212

13-
# Add and configure lab users in Azure DevTest Labs
13+
# Add and configure lab users in Azure DevTest Labs
1414

1515
Azure DevTest Labs uses Azure [role-based access control](/azure/role-based-access-control/overview) (RBAC) to define roles that have the access necessary to do specific lab tasks. DevTest Labs has three built-in roles: **Owner**, **Contributor**, and **DevTest Labs User**. This article describes the tasks each role can do, and how lab owners can add members to lab roles by using the Azure portal or an Azure PowerShell script.
1616

17+
<a name="devtest-labs-user"></a>
1718
## Owners, Contributors, and DevTest Labs Users
1819

1920
The following table shows the actions that the DevTest Labs Owner, Contributor, and DevTest Labs User roles can take.
@@ -26,22 +27,19 @@ The following table shows the actions that the DevTest Labs Owner, Contributor,
2627
|Configure user settings and roles.|X|||
2728
|Update lab virtual machine (VM) policies.|X|X||
2829
|Update cost settings.|X|X||
29-
| | | | | |
3030
|VM base tasks:||||
3131
|Enable Marketplace images.|X|X||
3232
|Add, update, and delete VM base formulas.|X|X|X|
3333
|Add and remove custom images.|X|X||
3434
|Add, update, and delete formulas.|X|X||
35-
| | | | | |
3635
|Individual VM tasks:||||
3736
|Create VMs.|X|X|X|
38-
|Start, stop, or delete own VMs.|X|X|X|
37+
|Start, stop, or delete owned VMs.|X|X|X|
3938
|Add or remove VM data disks.|X|X|X|
40-
| | | | | |
4139
|Artifact and template tasks:||||
4240
|Add and remove lab artifact and template repositories.|X|X||
4341
|Create artifacts and templates.|X|X|X|
44-
|Apply artifacts to own VMs.|X|X|X|
42+
|Apply artifacts to owned VMs.|X|X|X|
4543

4644
> [!NOTE]
4745
> Lab users automatically have the **Owner** role on VMs they create.
@@ -50,7 +48,7 @@ The following table shows the actions that the DevTest Labs Owner, Contributor,
5048

5149
Azure permissions propagate from parent scope to child scope. Owners of an Azure subscription that contains labs are automatically Owners of the subscription's labs.
5250

53-
Azure subscription [Owners](/azure/role-based-access-control/built-in-roles#owner) or [User Access Administrators](/azure/role-based-access-control/built-in-roles#user-access-administrator) can add Owners, Contributors, and DevTest Labs Users to labs in the subscription. To be added in a lab Owner role, users must have at least Contributor-level permissions in the Azure subscription.
51+
Azure subscription [Owners](/azure/role-based-access-control/built-in-roles#owner) or [User Access Administrators](/azure/role-based-access-control/built-in-roles#user-access-administrator) can add Owners, Contributors, and DevTest Labs Users to labs in the subscription. To be added as a lab Owner, users must have at least Contributor-level permissions in the Azure subscription.
5452

5553
Users that are granted the lab Owner role can add and configure Owners, Contributors, and DevTest Labs Users for their own labs. However, added lab Owners have a narrower scope of administration than Azure subscription-based Owners. Added Owners don't have full access to some resources that the DevTest Labs service creates.
5654

@@ -66,9 +64,9 @@ Lab Owners can add members to lab roles by using the Azure portal or an Azure Po
6664

6765
- Lab Owner role, either by assignment from a subscription owner or by inheritance as a subscription owner.
6866

69-
### Add a member:
67+
### Add a lab member
7068

71-
The following procedure adds a **DevTest Labs User** member to a lab. If you're also a subscription owner, you can also do this procedure from the subscription's **Access control (IAM)** page.
69+
The following procedure adds a **DevTest Labs User** member to a lab. If you're an Owner of the Azure subscription the lab is in, you can also do this procedure from the subscription's **Access control (IAM)** page.
7270

7371
1. On the lab's home page, select **Configuration and policies** from the left navigation.
7472
1. On the **Configuration and policies** page, select **Access control (IAM)** from the left navigation.
@@ -98,7 +96,7 @@ This PowerShell script requires the added user to be in the Microsoft Entra ID.
9896

9997
### Add a member
10098

101-
The following PowerShell script adds a member to a lab with DevTest Labs User role. To use the script, update the parameter values under the `# Values to change` comment. You can get the `subscriptionId`, `labResourceGroup`, and `labName` values from the lab's main page in the Azure portal.
99+
The following PowerShell script adds a member to a lab with DevTest Labs User role. To use the script, replace the parameter values under the `# Values to change` comment with your own values. You can get the `subscriptionId`, `labResourceGroup`, and `labName` values from the lab's main page in the Azure portal.
102100

103101
```azurepowershell
104102
# Values to change
@@ -107,7 +105,7 @@ $labResourceGroup = "<Lab's resource group name>"
107105
$labName = "<Lab name>"
108106
$userDisplayName = "<User's display name>"
109107
110-
# Log into your Azure account.
108+
# Sign into your Azure account.
111109
Connect-AzAccount
112110
113111
# Select the Azure subscription that contains the lab. This step is optional if you have only one subscription.

0 commit comments

Comments
 (0)