An Azure service that is used to provision Windows and Linux virtual machines.
For a student creating a virtual machine (VM) for assignments, there are two common Azure paths in the provided information: Azure Lab Services (when the school provides lab VMs) and Azure for Students (when creating personal VMs in an Azure subscription).
- If the school uses Azure Lab Services
- Sign in to the Lab portal with the account provided by the institution.
- Confirm that the lab VM is in Running state before connecting. If it is Stopped, start it from the lab portal and wait 2–5 minutes for it to be fully available.
- If Remote Desktop cannot connect and shows a message like “Remote Desktop can’t connect to the remote computer…”, verify again in the lab portal that the VM is running and not still starting.
- If the error is “Your credentials did not work” when logging in:
- Make sure the correct username and password for the lab VM are used. If the lab was created with “Use same password for all virtual machines”, the same credentials work for all students.
- If the password was forgotten and a custom password is used, reset it from the lab as described in reset the password on the machine from the lab.
- If needed, reimage the VM (note this deletes all user data on that VM) using the steps in reimage the machine.
- If many students cannot log in with the common lab credentials and the lab uses a custom image, use the username/password from when the image was created or reset the password as described in the limitation.
- If there is concern the VM account was compromised (password changed by someone else), reset the password and use strong, unique passwords. Restrict lab access so only class members can use the machines.
- If using an Azure for Students subscription to create a personal VM
- Confirm eligibility and activation:
- Azure for Students requires being a full-time student at an accredited degree-granting institution and verifying academic status with the school email address.
- After sign-up, there is a free credit and the ability to deploy Windows 10/11 VMs without a separate Windows Enterprise license.
- When creating a VM (for example via tools like Azure Explorer in IntelliJ or directly in the portal), ensure the following are set correctly:
- Image/SKU: Choose an appropriate OS image (for example, a Windows 10/11 or Linux image) and version.
- Size: Select a VM size that fits within the available quota and credit (cores and memory).
- Administrator account:
- Choose Authentication type (SSH public key or password for Linux; password for Windows).
- Set User name and Password and keep them safe; these are needed to log in.
- Networking:
- Select or create a Virtual Network and Subnet.
- Decide whether to assign a Public IP (required for direct RDP/SSH from the internet).
- Configure Security group and inbound ports so that required ports (for example, RDP 3389 for Windows, SSH 22 for Linux) are open.
- If deployment fails or the VM stays in a
creatingorfailedstate, common causes are:- Provisioning failures due to incorrect or missing guest agent or image configuration (especially for custom Linux images). In that case, follow the Azure image requirements and ensure cloud-init or the Azure agent is configured correctly.
- Allocation failures if the chosen size is not available in the region; try a different VM size or region.
- Confirm eligibility and activation:
- If sign-in to Azure or education benefits is the problem
- For Azure Dev Tools for Teaching or Education Hub access, a valid Microsoft account is required. If the school email is not yet a Microsoft account, create a Microsoft account using that university email address.
- If using a personal email, it may be necessary to create or link a Microsoft account to that address.
If more detail is needed, specify where the issue occurs (signing into Azure, creating the VM, or connecting to the VM) and any error messages seen.
References: