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/classroom-labs/administrator-guide.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,19 +51,19 @@ A lab account serves as a container for one or more classroom labs. When getting
51
51
52
52
The following list highlights scenarios where more than one lab account may be beneficial:
53
53
54
-
-**Manage different policy requirements across classroom labs.**
54
+
-**Manage different policy requirements across classroom labs**
55
55
56
56
When you set up a lab account, you set policies that apply to *all* classroom labs under the lab account, such as:
57
57
- The Azure virtual network with shared resources that the classroom lab can access. For example, you may have a set of classroom labs that need access to a shared data set within a virtual network.
58
58
- The virtual machine (VM) images that the classroom labs can use to create VMs. For example, you may have a set of classroom labs that need access to the [Data Science VM for Linux](https://azuremarketplace.microsoft.com/marketplace/apps/microsoft-dsvm.linux-data-science-vm-ubuntu) Marketplace image.
59
59
60
60
If you have classroom labs that have unique policy requirements from one another, it may be beneficial to create separate lab accounts to manage these classroom labs separately.
61
61
62
-
-**Separate budget by lab account.**
62
+
-**Separate budget by lab account**
63
63
64
64
Instead of reporting all classroom lab costs through a single lab account, you may need a more clearly separated budget. For example, you can create lab accounts for your university's Math department, Computer Science department, and so forth, to separate the budget across departments. You can then view the cost for each individual lab account using [Azure Cost Management](https://docs.microsoft.com/azure/cost-management-billing/cost-management-billing-overview).
65
65
66
-
-**Isolate pilot labs from active\production labs.**
66
+
-**Isolate pilot labs from active\production labs**
67
67
68
68
You may have cases where you want to pilot policy changes for a lab account without potentially impacting active\production labs. In this type of scenario, creating a separate lab account for piloting purposes allows you to isolate changes.
69
69
@@ -75,15 +75,15 @@ A classroom lab contains virtual machines (VMs) that are each assigned to a sing
75
75
76
76
Consider the following points when determining how to structure your classroom labs:
77
77
78
-
-**All VMs within a classroom lab are deployed with the same image that's published**.
78
+
-**All VMs within a classroom lab are deployed with the same image that's published**
79
79
80
80
As a result, if you have a class that requires different lab images be published at the same time, separate classroom labs must be created for each one.
81
81
82
-
-**Usage quota is set at the lab level and applies to all users within the lab**.
82
+
-**Usage quota is set at the lab level and applies to all users within the lab**
83
83
84
84
To set different quotas for users, you must create separate classroom labs. However, it's possible to add more hours to a specific user after you have set the quota.
85
85
86
-
-**The startup or shutdown schedule is set at the lab level and applies to all VMs within the lab**.
86
+
-**The startup or shutdown schedule is set at the lab level and applies to all VMs within the lab**
87
87
88
88
Similar to the previous point, if you need to set different schedules for users, you need to create separate classroom labs.
0 commit comments