Get answers to some of the most common questions about labs in Azure Lab Services.
Is the quota per user or per week or per entire duration of the lab?
The quota you set for a lab is for each student for entire duration of the lab. And, the scheduled running time of VMs doesn't count against the quota allotted to a user. The quota is for the time outside of schedule hours that a student spends on VMs. For more information on quotas, see Set quotas for users.
If educator turns on a student VM, does that affect the student quota?
No. It doesn't. When educator turns on the student VM, it doesn't affect the quota allotted to the student.
Do all VMs in the lab start automatically when a schedule is set?
No. Not all the VMs. Only the VMs that are assigned to users on a schedule. The VMs that aren't assigned to a user aren't automatically started. It's by design.
Why am I not able to create a lab because of unavailability of the address range?
Labs can create lab VMs within an IP address range you specify when creating your lab account in the Azure portal. When an address range is provided, each lab that's created after it's allotted 512 IP addresses for lab VMs. The address range for the lab account must be large enough to accommodate all the labs you intend to create under the lab account.
For example, if you have a block of /19 - 10.0.0.0/19, this address range accommodates 8192 IP addresses and 16 labs(8192/512 = 16 labs). In this case, lab creation fails on 17th lab creation.
What port ranges should I open on my organization's firewall setting to connect to Lab virtual machines via RDP/SSH?
The ports are: 49152–65535. Labs sit behind a load balancer. Each lab has a single public IP address and each virtual machine in the lab has a unique port.
You can also see the private IP address of each virtual machine on the Virtual machine pool tab of the home page for lab in the Azure portal. If you republish a lab, the public IP address of the lab will not change, but the private IP and port number of each virtual machine in the lab can change. You can learn more in the article: Firewall settings for Azure Lab Services.
What public IP address range should I open on my organization's firewall settings to connect to Lab virtual machines via RDP/SSH?
See Azure IP Ranges and Service Tags — Public Cloud, which provides the public IP address range for data centers in Azure. You can open the IP addresses for the regions where your lab accounts are in.
Virtual machine images
As a lab creator, why can't I enable additional image options in the virtual machine images dropdown when creating a new lab?
When an administrator adds you as a lab creator to a lab account, you're given the permissions to create labs. But, you don't have the permissions to edit any settings inside the lab account, including the list of enabled virtual machine images. To enable additional images, contact your lab account administrator to do it for you, or ask the administrator to add you as a Contributor role to the lab account. The Contributor role will give you the permissions to edit the virtual machine image list in the lab account.
Can I attach additional disks to a virtual machine?
No. it's not possible to attach additional disks to a VM in a classroom lab.
How many users can be in a classroom lab?
You can add up to 400 users to a classroom lab.
Subscribe to the Azure Lab Services blog.
Subscribe to Lab Services updates to stay informed about new features in Lab Services.
When I select my lab's automatic shutdown Settings, why is this page blank or why don't I see the setting to automatically disconnect users when VMs are idle?
In general, Linux labs only support automatic shut down when users disconnect and when VMs are started but users don't connect. However, support for these settings also varies depending on specific distributions and versions of Linux. Shutdown settings are not supported by the Data Science Virtual Machine - Ubuntu 18.04 image. For more information on the shutdown settings, see the following articles:
How can I use Ubuntu 18.04 Server LTS and install either the GNOME or MATE graphical desktops?
There is a known networking conflict between GNOME\MATE graphical desktops) and the Azure Linux VM Agent when using Ubuntu 18.04 LTS. As a result, we suggest the following:
- Instead of GNOME\MATE, consider using the XFCE graphical desktop which doesn't have this issue. For example, the Data Science VM image is configured by default to use XFCE.
- Instead of Ubuntu 18.04 LTS, consider using Ubuntu 20.04 or 21.04 LTS which don't have this networking conflict with the agent when GNOME\MATE is installed.
- Otherwise, to use 18.04 LTS and GNOME\MATE, you will need to apply a workaround to fix the networking conflict with the agent. See our ReadMe and scripts that set up Ubuntu Server 18.04\20.04\21.04 with GNOME\MATE. When you use these scripts to set up 18.04 with GNOME\MATE, they will apply the workaround for the networking conflict.
How do I prevent capacity constraints and Azure compute capacity limitations on my subscription?
When you start to use Azure Lab Services for the first time, you will need to submit a request to increase the Azure compute capacity limit that exists on your subscription. As your lab usage grows and increases in the number of VM cores you need, you may need to repeat this process to increase your quota limit further. As part of your up front planning each time that you deploy new labs, you also need to ensure that there is adequate VM core capacity in the region that you plan to deploy in. This is especially important for GPUs. For more information on how to plan for both capacity and Azure compute capacity limitations, read the following article:
What if my question isn't answered here?
If your question isn't listed here, let us know, so we can help you find an answer.
- Post a question at the end of this FAQ.
- To reach a wider audience, post a question on the Azure Lab Services — Tech community forum.