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/lab-services/account-setup-guide.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,7 @@ You might want to create your images in your physical environment and then impor
88
88
If you decide to use the Shared Image Gallery service, you'll need to create or attach a shared image gallery to your lab account. You can postpone this decision for now, because a shared image gallery can be attached to a lab account at any time.
89
89
90
90
For more information, see:
91
+
91
92
- The "Shared image gallery" section of [Azure Lab Services - Administrator guide](./administrator-guide-1.md#shared-image-gallery)
92
93
- The "Pricing" section of [Azure Lab Services - Administrator guide](./administrator-guide-1.md#pricing)
93
94
@@ -126,11 +127,11 @@ When you set up a lab account, you also can peer your lab account with a virtual
126
127
127
128
After you've finished planning, you're ready to set up your lab account. You can apply the same steps to setting up [Azure Lab Services in Teams](./lab-services-within-teams-overview.md).
128
129
129
-
1.**Create your lab account**. For instructions, see [Create a lab account](./tutorial-setup-lab-account.md#create-a-lab-account).
130
+
1.**Create your lab account**. For instructions, see [Create a lab account](how-to-create-lab-accounts.md).
130
131
131
132
For information about naming conventions, see the "Naming" section of [Azure Lab Services - Administrator guide](./administrator-guide-1.md#naming).
132
133
133
-
1.**Add users to the Lab Creator role**. For instructions, see [Add users to the Lab Creator role](./tutorial-setup-lab-account.md#add-a-user-to-the-lab-creator-role).
134
+
1.**Add users to the Lab Creator role**. For instructions, see [Add a user to the Lab Creator role](how-to-add-lab-creator.md).
134
135
135
136
1.**Connect to a peer virtual network**. For instructions, see [Connect your lab network with a peer virtual network](./how-to-connect-peer-virtual-network.md).
To grant people the permission to create labs, add them to the Lab Creator role.
19
+
20
+
Follow these steps to [assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.yml).
21
+
22
+
> [!NOTE]
23
+
> Azure Lab Services automatically assigns the Lab Creator role to the Azure account you use to create the lab account.
24
+
25
+
1. On the **Lab Account** page, select **Access control (IAM)**.
26
+
27
+
1. From the **Access control (IAM)** page, select **Add** > **Add role assignment**.
28
+
29
+
:::image type="content" source="../../includes/role-based-access-control/media/add-role-assignment-menu-generic.png" alt-text="Screenshot that shows the Access control (I A M) page with Add role assignment menu option highlighted.":::
30
+
31
+
1. On the **Role** tab, select the **Lab Creator** role.
32
+
33
+
:::image type="content" source="../../includes/role-based-access-control/media/add-role-assignment-role-generic.png" alt-text="Screenshot that shows the Add role assignment page with Role tab selected.":::
34
+
35
+
1. On the **Members** tab, select the user you want to add to the Lab Creators role.
36
+
37
+
1. On the **Review + assign** tab, select **Review + assign** to assign the role.
38
+
39
+
## Next steps
40
+
41
+
In this article, you granted lab creation permissions to another user. To learn about how to create a lab, see [Manage labs in Azure Lab Services when using lab accounts](how-to-manage-classroom-labs.md).
Copy file name to clipboardExpand all lines: articles/lab-services/how-to-connect-peer-virtual-network.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Connect to a peer network
3
3
titleSuffix: Azure Lab Services
4
-
description: Learn how to connect your lab network with another network as a peer for lab accounts in Azure Lab Services. For example, connect your on-premises organization/university network with Lab's virtual network in Azure.
4
+
description: Learn how to connect your lab network with another network as a peer for lab accounts in Azure Lab Services. For example, connect your on-premises organization/university network with Lab's virtual network in Azure.
5
5
services: lab-services
6
6
ms.service: lab-services
7
7
author: ntrogh
@@ -20,39 +20,39 @@ This article provides information about peering your labs network with another n
20
20
21
21
Virtual network peering enables you to seamlessly connect Azure virtual networks. Once peered, the virtual networks appear as one, for connectivity purposes. The traffic between virtual machines in the peered virtual networks is routed through the Microsoft backbone infrastructure, much like traffic is routed between virtual machines in the same virtual network, through private IP addresses only. For more information, see [Virtual network peering](../virtual-network/virtual-network-peering-overview.md).
22
22
23
-
You may need to connect your lab's network with a peer virtual network in some scenarios including the following ones:
23
+
You might need to connect your lab's network with a peer virtual network in some scenarios including the following ones:
24
24
25
25
- The virtual machines in the lab have software that connects to on-premises license servers to acquire license.
26
26
- The virtual machines in the lab need access to data sets (or any other files) on university's network shares.
27
27
28
28
Certain on-premises networks are connected to Azure Virtual Network either through [ExpressRoute](../expressroute/expressroute-introduction.md) or [Virtual Network Gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md). These services must be set up outside of Azure Lab Services. To learn more about connecting an on-premises network to Azure using ExpressRoute, see [ExpressRoute overview](../expressroute/expressroute-introduction.md). For on-premises connectivity using a Virtual Network Gateway, the gateway, specified virtual network, and the lab account must all be in the same region.
29
29
30
30
> [!NOTE]
31
-
> When creating a Azure Virtual Network that will be peered with a lab account, it's important to understand how the virtual network's region impacts where labs are created. For more information, see the administrator guide's section on [regions/locations](./administrator-guide-1.md#regionslocations).
31
+
> When creating a Azure Virtual Network that will be peered with a lab account, it's important to understand how the virtual network's region impacts where labs are created. For more information, see the administrator guide's section on [regions/locations](./administrator-guide-1.md#regionslocations).
32
32
33
33
> [!NOTE]
34
-
> If your school needs to perform content filtering, such as for compliance with the [Children's Internet Protection Act (CIPA)](https://www.fcc.gov/consumers/guides/childrens-internet-protection-act), you will need to use 3rd party software. For more information, read guidance on [content filtering with Lab Services](./administrator-guide.md#content-filtering).
34
+
> If your school needs to perform content filtering, such as for compliance with the [Children's Internet Protection Act (CIPA)](https://www.fcc.gov/consumers/guides/childrens-internet-protection-act), you will need to use 3rd party software. For more information, read guidance on [content filtering with Lab Services](./administrator-guide.md#content-filtering).
35
35
36
36
## Configure at the time of lab account creation
37
37
38
-
During the new [lab account creation](tutorial-setup-lab-account.md), you can pick an existing virtual network that shows in the **Peer virtual network** dropdown list on the **Advanced** tab. The list only shows virtual networks in the same region as the lab account. The selected virtual network is connected (peered) to labs created under the lab account. All the virtual machines in labs that are created after the making this change have access to the resources on the peered virtual network.
38
+
When [creating a lab account](how-to-create-lab-accounts.md), you can pick an existing virtual network that shows in the **Peer virtual network** dropdown list on the **Advanced** tab. The list only shows virtual networks in the same region as the lab account. The selected virtual network is connected (peered) to labs created under the lab account. All the virtual machines in labs that are created after the making this change have access to the resources on the peered virtual network.
39
39
40
40

41
41
42
42
### Address range
43
43
44
-
There's also an option to provide an address range for virtual machines for the labs. The address range setting applies only if you enable a peer virtual network for the lab. If the address range is provided, all the virtual machines in the labs under the lab account are created in that address range. The address range should be in CIDR notation (for example, 10.20.0.0/20) and shouldn't overlap with any existing address ranges.
44
+
There's also an option to provide an address range for virtual machines for the labs. The address range setting applies only if you enable a peer virtual network for the lab. If the address range is provided, all the virtual machines in the labs under the lab account are created in that address range. The address range should be in CIDR notation (for example, 10.20.0.0/20) and shouldn't overlap with any existing address ranges.
45
45
46
-
When you provide an address range, it's important to think about the number of *labs* that you create. Azure Lab Services assumes a maximum of 512 virtual machines per lab. For example, an IP range with '/23' can create only one lab. A range with a '/21' allows for the creation of four labs.
46
+
When you provide an address range, it's important to think about the number of *labs* that you create. Azure Lab Services assumes a maximum of 512 virtual machines per lab. For example, an IP range with '/23' can create only one lab. A range with a '/21' allows for the creation of four labs.
47
47
48
-
If the address range isn't specified, Azure Lab Services uses the default address range given to it by Azure when creating the virtual network to be peered with your virtual network. The range is often something like 10.x.0.0/16. This large range might lead to IP range overlap, so make sure to either specify an address range in the lab settings or check the address range of your virtual network being peered.
48
+
If the address range isn't specified, Azure Lab Services uses the default address range given to it by Azure when creating the virtual network to be peered with your virtual network. The range is often something like 10.x.0.0/16. Large IP ranges might lead to IP range overlap. Make sure to either specify an address range in the lab settings or check the address range of your virtual network being peered.
49
49
50
50
> [!NOTE]
51
-
> Lab creation can fail if the lab account is peered to a virtual network but has too narrow of an IP address range. You can run out of space in the address range if there are too many labs in the lab account (each lab uses 512 addresses).
51
+
> Lab creation can fail if the lab account is peered to a virtual network but has too narrow of an IP address range. You can run out of space in the address range if there are too many labs in the lab account (each lab uses 512 addresses).
52
52
>
53
53
> For example, if you have a block of /19, this address range can accommodate 8192 IP addresses and 16 labs (8192/512 = 16 labs). In this case, lab creation fails on the 17th lab creation.
54
-
>
55
-
> If the lab creation fails, contact your lab account owner/admin and request for the address range to be increased. The admin can increase the address range using steps mentioned in the [Specify an address range for VMs in a lab account](#specify-an-address-range-for-vms-in-the-lab-account) section.
54
+
>
55
+
> If the lab creation fails, contact your lab account owner/admin and request for the address range to be increased. The admin can increase the address range using steps mentioned in the [Specify an address range for VMs in a lab account](#specify-an-address-range-for-vms-in-the-lab-account) section.
56
56
57
57
## Configure after the lab account is created
58
58
@@ -66,16 +66,17 @@ When you select a virtual network for the **Peer virtual network** field, the **
66
66
> The peered virtual network setting applies only to labs that are created after the change is made, not to the existing labs.
67
67
68
68
## Specify an address range for VMs in the lab account
69
-
The following procedure has steps to specify an address range for VMs in the lab. If you update the range that you previously specified, the modified address range applies only to VMs that are created after the change was made.
70
69
71
-
Here are some restrictions when specifying the address range that you should keep in mind.
70
+
The following procedure has steps to specify an address range for VMs in the lab. If you update the range that you previously specified, the modified address range applies only to VMs that are created after the change was made.
71
+
72
+
Here are some restrictions when specifying the address range that you should keep in mind.
72
73
73
-
- The prefix must be smaller than or equal to 23.
74
+
- The prefix must be smaller than or equal to 23.
74
75
- If a virtual network is peered to the lab account, the provided address range can't overlap with address range from peered virtual network.
75
76
76
77
1. On the **Lab Account** page, select **Lab settings** on the left menu.
77
78
2. For the **Address range** field, specify the address range for VMs that are created in the lab. The address range should be in the classless inter-domain routing (CIDR) notation (example: 10.20.0.0/23). Virtual machines in the lab are created in this address range.
78
-
3. Select **Save** on the toolbar.
79
+
3. Select **Save** on the toolbar
79
80
80
81

81
82
@@ -87,4 +88,4 @@ See the following articles:
87
88
-[Attach a compute gallery to a lab](how-to-attach-detach-shared-image-gallery-1.md)
88
89
-[Add a user as a lab owner](how-to-add-user-lab-owner.md)
89
90
-[View firewall settings for a lab](how-to-configure-firewall-settings.md)
90
-
-[Configure other settings for a lab](how-to-configure-lab-accounts.md)
91
+
-[Configure other settings for a lab](how-to-configure-lab-accounts.md)
Copy file name to clipboardExpand all lines: articles/lab-services/how-to-manage-classroom-labs.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
@@ -13,7 +13,7 @@ This article describes how to create and delete a lab. It also shows you how to
13
13
14
14
## Prerequisites
15
15
16
-
To set up a lab in a lab account, you must be a member of the **Lab Creator** role in the lab account. The account you used to create a lab account is automatically added to this role. A lab owner can add other users to the Lab Creator role by using steps in the following article: [Add a user to the Lab Creator role](tutorial-setup-lab-account.md#add-a-user-to-the-lab-creator-role).
16
+
To set up a lab in a lab account, you must be a member of the **Lab Creator** role in the lab account. The account you used to create a lab account is automatically added to this role. A lab owner can add other users to the Lab Creator role by using steps in the following article: [Add a user to the Lab Creator role](how-to-add-lab-creator.md).
17
17
18
18
## Create a lab
19
19
@@ -43,7 +43,7 @@ To set up a lab in a lab account, you must be a member of the **Lab Creator** ro
43
43
> Make a note of user name and password. They won't be shown again.
44
44
3. Disable **Use same password for all virtual machines** option if you want students to set their own passwords. This step is **optional**.
45
45
46
-
An educator can choose to use the same password for all the VMs in the lab, or allow students to set passwords for their VMs. By default, this setting is enabled for all Windows and Linux images except for Ubuntu. When you select **Ubuntu** VM, this setting is disabled and students are prompted to set a password when they sign in for the first time.
46
+
An educator can choose to use the same password for all the VMs in the lab, or allow students to set passwords for their VMs. By default, this setting is enabled for all Windows and Linux images except for Ubuntu. When you select **Ubuntu** VM, this setting is disabled and students are prompted to set a password when they sign in for the first time.
47
47
48
48
:::image type="content" source="./media/how-to-manage-classroom-labs/virtual-machine-credentials.png" alt-text="Screenshot that shows the Virtual machine credentials page of the New lab wizard.":::
49
49
@@ -63,10 +63,10 @@ To set up a lab in a lab account, you must be a member of the **Lab Creator** ro
63
63
8. On the **Template** page, do the following steps: These steps are **optional** for the tutorial.
64
64
65
65
1. Start the template VM.
66
-
1. Connect to the template VM by selecting **Connect**. If it's a Linux template VM, you choose whether you want to connect using an SSH terminal or a graphical remote desktop. Additional setup is required to use a graphical remote desktop. For more information, see [Enable graphical remote desktop for Linux virtual machines in Azure Lab Services](how-to-enable-remote-desktop-linux.md).
66
+
1. Connect to the template VM by selecting **Connect**. If it's a Linux template VM, you choose whether you want to connect using an SSH terminal or a graphical remote desktop. Extra setup is required to use a graphical remote desktop. For more information, see [Enable graphical remote desktop for Linux virtual machines in Azure Lab Services](how-to-enable-remote-desktop-linux.md).
67
67
1. Select **Reset password** to reset the password for the VM. The VM must be running before the reset password button is available.
68
68
1. Install and configure software on your template VM.
69
-
1.**Stop** the VM.
69
+
1.**Stop** the VM.
70
70
71
71
9. On **Template** page, select **Publish** on the toolbar.
0 commit comments