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/cost-management-guide.md
+44-44Lines changed: 44 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,20 +13,20 @@ For Azure Lab Services, cost management can be broken down into two distinct are
13
13
14
14
## Estimate the lab costs
15
15
16
-
Each lab dashboard has a **Costs & Billing** section that lays out a rough estimate of what the lab will cost for the month. The cost estimate summarizes the hour usage with the maximum number of users by the estimated cost per hour. To get the most accurate estimate, set up the lab, including the [schedule](how-to-create-schedules.md). The dashboard will reflect the estimated cost.
16
+
Each lab dashboard has a **Costs & Billing** section that lays out a rough estimate of what the lab will cost for the month. The cost estimate summarizes the hour usage with the maximum number of users by the estimated cost per hour. To get the most accurate estimate, set up the lab, including the [schedule](how-to-create-schedules.md). The dashboard will reflect the estimated cost.
17
17
18
18
This estimate might not show all the possible costs. A few resources aren't included:
19
19
20
-
- The template preparation cost. It can vary significantly in the amount of time needed to create the template. The cost to run the template is the same as the overall lab cost per hour.
21
-
- Any [shared image gallery](how-to-use-shared-image-gallery.md) costs, because a gallery can be shared among multiple labs.
20
+
- The template preparation cost. It can vary significantly in the amount of time needed to create the template. The cost to run the template is the same as the overall lab cost per hour.
21
+
- Any [shared image gallery](how-to-use-shared-image-gallery.md) costs, because a gallery can be shared among multiple labs.
22
22
- Hours incurred when the lab creator starts a virtual machine (VM).
23
23
24
24
> [!div class="mx-imgBorder"]
25
25
> 
26
26
27
27
## Analyze the previous month's usage
28
28
29
-
The cost analysis is for reviewing the previous month's usage to help you determine any adjustments for the lab. You can find the breakdown of past costs in the [subscription cost analysis](../cost-management-billing/costs/quick-acm-cost-analysis.md). In the Azure portal, you can enter **Subscriptions** in the search box and then select the **Subscriptions** option.
29
+
The cost analysis is for reviewing the previous month's usage to help you determine any adjustments for the lab. You can find the breakdown of past costs in the [subscription cost analysis](../cost-management-billing/costs/quick-acm-cost-analysis.md). In the Azure portal, you can enter **Subscriptions** in the search box and then select the **Subscriptions** option.
30
30
31
31
> [!div class="mx-imgBorder"]
32
32
> 
@@ -52,7 +52,7 @@ The following screenshot is an example of a cost analysis.
52
52
> [!div class="mx-imgBorder"]
53
53
> 
54
54
55
-
By default, there are six columns: **Resource**, **Resource type**, **Location**, **Resource group name**, **Tags**, and **Cost**. The **Resource** column contains the information about the lab account, lab name, and VM. The rows that show the lab account, lab name, and default (second and third rows) are the cost for the lab. The used VMs have a cost that you can see for the rows that show the lab account, lab name, default, and VM name.
55
+
By default, there are six columns: **Resource**, **Resource type**, **Location**, **Resource group name**, **Tags**, and **Cost**. The **Resource** column contains the information about the lab account, lab name, and VM. The rows that show the lab account, lab name, and default (second and third rows) are the cost for the lab. The used VMs have a cost that you can see for the rows that show the lab account, lab name, default, and VM name.
56
56
57
57
In this example, adding the first and second rows (both start with **aaalab / dockerlab**) will give you the total cost for the lab "dockerlab" in the "aaalab" lab account.
58
58
@@ -63,7 +63,7 @@ To get the overall cost for the image gallery, change the resource type to `Micr
63
63
64
64
## Separate the costs
65
65
66
-
Some universities have used the lab account and the resource group as ways to separate the classes. Each class has its own lab account and resource group.
66
+
Some universities have used the lab account and the resource group as ways to separate the classes. Each class has its own lab account and resource group.
67
67
68
68
In the cost analysis pane, add a filter based on the resource group name with the appropriate resource group name for the class. Then, only the costs for that class will be visible. This allows a clearer delineation between the classes when you're viewing the costs. You can use the [scheduled export](../cost-management-billing/costs/tutorial-export-acm-data.md) feature of the cost analysis to download the costs of each class in separate files.
69
69
@@ -78,83 +78,83 @@ Automatic shutdown features enable you to prevent wasted VM usage hours in the l
78
78
> [!div class="mx-imgBorder"]
79
79
> 
80
80
81
-
You can configure these settings at both the lab account level and the lab level. If you enable them at the lab account level, they're applied to all labs within the lab account. For all new lab accounts, these settings are turned on by default.
81
+
You can configure these settings at both the lab account level and the lab level. If you enable them at the lab account level, they're applied to all labs within the lab account. For all new lab accounts, these settings are turned on by default.
82
82
83
83
#### Automatically disconnect users from virtual machines that the OS deems idle
84
84
85
85
> [!NOTE]
86
86
> This setting is available only for Windows virtual machines.
87
87
88
-
When the **Disconnect users when virtual machines are idle** setting is turned on, the user is disconnected from any machines in the lab when the Windows OS deems the session to be idle (including the template virtual machines). The [Windows OS definition of idle](/windows/win32/taskschd/task-idle-conditions#detecting-the-idle-state) uses two criteria:
88
+
When the **Disconnect users when virtual machines are idle** setting is turned on, the user is disconnected from any machines in the lab when the Windows OS deems the session to be idle (including the template virtual machines). The [Windows OS definition of idle](/windows/win32/taskschd/task-idle-conditions#detecting-the-idle-state) uses two criteria:
89
89
90
-
* User absence: no keyboard or mouse input.
91
-
* Lack of resource consumption: All the processors and all the disks were idle for a certain percentage of time.
90
+
- User absence: no keyboard or mouse input.
91
+
- Lack of resource consumption: All the processors and all the disks were idle for a certain percentage of time.
92
92
93
-
Users will see a message like this in the VM before they're disconnected:
93
+
Users will see a message like this in the VM before they're disconnected:
94
94
95
95
> [!div class="mx-imgBorder"]
96
96
> 
97
-
98
-
The virtual machine is still running when the user is disconnected. If the user reconnects to the virtual machine by signing in, windows or files that were open or work that was unsaved before the disconnect will still be there. In this state, because the virtual machine is running, it still counts as active and accrues cost.
99
-
97
+
98
+
The virtual machine is still running when the user is disconnected. If the user reconnects to the virtual machine by signing in, windows or files that were open or work that was unsaved before the disconnect will still be there. In this state, because the virtual machine is running, it still counts as active and accrues cost.
99
+
100
100
To automatically shut down idle Windows virtual machines that are disconnected, use the combination of **Disconnect users when virtual machines are idle** and **Shut down virtual machines when users disconnect** settings.
101
101
102
102
For example, if you configure the settings as follows:
103
-
104
-
***Disconnect users when virtual machines are idle**: 15 minutes after the idle state is detected.
105
-
***Shut down virtual machines when users disconnect**: 5 minutes after the user disconnects.
106
-
107
-
The Windows virtual machines will automatically shut down 20 minutes after the user stops using them.
108
-
103
+
104
+
-**Disconnect users when virtual machines are idle**: 15 minutes after the idle state is detected.
105
+
-**Shut down virtual machines when users disconnect**: 5 minutes after the user disconnects.
106
+
107
+
The Windows virtual machines will automatically shut down 20 minutes after the user stops using them.
108
+
109
109
> [!div class="mx-imgBorder"]
110
110
> 
111
111
112
112
#### Automatically shut down virtual machines when users disconnect
113
-
113
+
114
114
The **Shut down virtual machines when users disconnect** setting supports both Windows and Linux virtual machines. When this setting is on, automatic shutdown will occur when:
115
-
116
-
* For Windows, a Remote Desktop (RDP) connection is disconnected.
117
-
* For Linux, an SSH connection is disconnected.
118
-
119
-
> [!NOTE]
120
-
> Only [specific distributions and versions of Linux](../virtual-machines/extensions/diagnostics-linux.md#supported-linux-distributions) are supported.
121
-
122
-
You can specify how long the virtual machines should wait for the user to reconnect before automatically shutting down.
115
+
116
+
- For Windows, a Remote Desktop (RDP) connection is disconnected.
117
+
- For Linux, a SSH connection is disconnected.
118
+
119
+
> [!IMPORTANT]
120
+
> Only [specific distributions and versions of Linux](../virtual-machines/extensions/diagnostics-linux.md#supported-linux-distributions) are supported. Shutdown settings are not supported by the [Data Science Virtual Machine - Ubuntu 18.04](https://azuremarketplace.microsoft.com/marketplace/apps/microsoft-dsvm.ubuntu-1804) image.
121
+
122
+
You can specify how long the virtual machines should wait for the user to reconnect before automatically shutting down.
123
123
124
124
#### Automatically shut down virtual machines that are started but users don't connect
125
-
125
+
126
126
In a lab, a user might start a virtual machine but never connect to it. For example:
127
-
128
-
* A schedule in the lab starts all virtual machines for a class session, but some students don't show up and don't connect to their machines.
129
-
* A user starts a virtual machine but forgets to connect.
130
-
131
-
The **Shut down virtual machines when users do not connect** setting will catch these cases and automatically shut down the virtual machines.
132
-
127
+
128
+
- A schedule in the lab starts all virtual machines for a class session, but some students don't show up and don't connect to their machines.
129
+
- A user starts a virtual machine but forgets to connect.
130
+
131
+
The **Shut down virtual machines when users do not connect** setting will catch these cases and automatically shut down the virtual machines.
132
+
133
133
For information on how to configure and enable automatic shutdown of VMs on disconnect, see these articles:
134
134
135
-
*[Configure automatic shutdown of VMs for a lab account](how-to-configure-lab-accounts.md)
136
-
*[Configure automatic shutdown of VMs for a lab](how-to-enable-shutdown-disconnect.md)
135
+
-[Configure automatic shutdown of VMs for a lab account](how-to-configure-lab-accounts.md)
136
+
-[Configure automatic shutdown of VMs for a lab](how-to-enable-shutdown-disconnect.md)
137
137
138
138
### Scheduled time vs. quota time
139
139
140
-
Understanding [scheduled time](classroom-labs-concepts.md#schedules) and [quota time](classroom-labs-concepts.md#quota) will help you to configure a lab to better fit the needs of the professor and the students.
140
+
Understanding [scheduled time](classroom-labs-concepts.md#schedules) and [quota time](classroom-labs-concepts.md#quota) will help you to configure a lab to better fit the needs of the professor and the students.
141
141
142
-
Scheduled time is a set time where all the student VMs have been started and are available for connection. Scheduled time is commonly used when all the students have their own VMs and are following the professor's directions at a set time during the day (like class hours). The downside is that all the student VMs are started and are accruing costs, even if a student doesn't log in to a VM.
142
+
Scheduled time is a set time where all the student VMs have been started and are available for connection. Scheduled time is commonly used when all the students have their own VMs and are following the professor's directions at a set time during the day (like class hours). The downside is that all the student VMs are started and are accruing costs, even if a student doesn't log in to a VM.
143
143
144
-
Quota time is time allocated to each student for use at their discretion and is often used for independent studying. The VMs aren't started until the student starts the VM.
144
+
Quota time is time allocated to each student for use at their discretion and is often used for independent studying. The VMs aren't started until the student starts the VM.
145
145
146
146
A lab can use either quota time or scheduled time, or a combination of both. If a class doesn't need scheduled time, then use only quota time for the most effective use of the VMs.
147
147
148
148
### Scheduled event: stop only
149
149
150
150
In the schedule, you can add a stop-only event type that will stop all machines at a specific time. Some lab owners have set a stop-only event for every day at midnight to reduce the cost and quota usage when a student forgets to shut down the VM they're using. The downside to this type of event is that all VMs will be shut down, even if a student is using a VM.
151
151
152
-
### Other costs related to labs
152
+
### Other costs related to labs
153
153
154
-
Some costs aren't rolled into Lab Services but can be tied to a lab service. You can connect a shared image gallery to a lab, but it won't show under the Lab Services costs and does have costs. To help keep overall costs down, you should remove any unused images from the gallery because the images have an inherent storage cost.
154
+
Some costs aren't rolled into Lab Services but can be tied to a lab service. You can connect a shared image gallery to a lab, but it won't show under the Lab Services costs and does have costs. To help keep overall costs down, you should remove any unused images from the gallery because the images have an inherent storage cost.
155
155
156
156
Labs can have connections to other Azure resources through a virtual network. When a lab is removed, you should remove the virtual network and the other resources.
157
157
158
158
## Conclusion
159
159
160
-
Hopefully, the information in this article has given you a better understanding of the tools that can help you reduce usage costs.
160
+
Hopefully, the information in this article has given you a better understanding of the tools that can help you reduce usage costs.
0 commit comments