Forum Discussion
SKU, quota and policy restrictions on Azure for Students and Free Subscriptions
Hi CvWyk, going direct to your questions
| Additional backend restrictions beyond visible policies? | Yes, behavior strongly indicates additional subscription/SKU restrictions beyond visible policies. |
| Dynamic VM restrictions per student? | Evidence strongly suggests yes in practice, though Microsoft does not publicly document the exact mechanism. |
| Regional capacity controls different across students? | Yes — capacity and eligibility appear to vary per subscription and region. |
| Best way to identify deployable SKUs? | Use az vm list-skus and verify against each student’s allowed regions before labs. |
and for your students, here's a list to make things easier
Azure for Students VM Troubleshooting Checklist
Quick Student Guide
Use this checklist when your Azure VM deployment fails.
Step 1 — Confirm You Are Using an Allowed Region
Your student subscription only works in certain Azure regions.
Check allowed regions:
- Open Azure Portal
- Search for Policy
- Go to:
- Authoring → Assignments
- Open:
- Allowed resource deployment regions
- Write down your allowed regions
Only deploy VMs in those regions.
Step 2 — Try Another Allowed Region
Even allowed regions may fail temporarily due to Azure capacity shortages.
If deployment fails:
- Try another allowed region
- Test several approved regions
Some students only succeed after changing regions multiple times.
Step 3 — Use Recommended VM Sizes
Some older VM sizes are restricted or retired.
Recommended VM sizes:
- Standard_B2ats_v2
- Standard_B2ts_v2
- Standard_B2als_v2
Avoid:
- B1s
- older B-series VM sizes
Step 4 — Do NOT Select Availability Zones
Availability Zones can block VM creation on student subscriptions.
Best practice:
- Leave zone selection on default
- Use:
- “No infrastructure redundancy required”
This avoids:
- “Unsupported availability zone”
- “SKU unavailable in selected zone”
Step 5 — Check VM Quotas
You may hit VM quota limits even with free credit available.
Check quotas:
- Go to:
- Subscriptions → Usage + quotas
- Look for:
- Total Regional vCPU quota
- VM family quotas
Common error:
- “Total Regional Core quota exceeded”
Step 6 — If No VM Sizes Appear
Possible causes:
- region capacity exhausted
- restricted subscription
- unsupported VM family
- temporary Azure capacity issue
Try:
Another allowed region
Another Bsv2 VM size
Removing Availability Zones
Trying again later
Step 7 — Use CLI to Check Available VM Sizes (Advanced)
The Azure Portal sometimes shows incomplete information.
Azure CLI command:
Shell
az vm list-skus \
--location <region> \
--resource-type virtualMachines \
--output table
Show more lines
Example:
Shell
az vm list-skus \
--location denmarkeast \
--size Standard_B \
--all
``
Show more lines
This shows which VM sizes are actually available for your subscription
Step 8 — Still Not Working?
Document the following before asking for help:
Subscription type
Region used
VM size attempted
Exact error message
Screenshot of:
- Allowed regions
- Usage + quotas page
This makes troubleshooting much faster.
Recommended “Safe” Student Deployment Setup
|
Setting |
Recommended Value |
|
Region |
One of your allowed regions |
|
VM Size |
B2ats_v2 / B2ts_v2 |
|
Availability Zone |
None |
|
OS |
Ubuntu Gen2 |
|
vCPU usage |
Keep under 4 cores |
Important Reality Check
Azure for Students subscriptions can behave differently between students because:
- allowed regions differ
- VM capacity changes dynamically
- some VM sizes are restricted
- region availability is not always consistent
A deployment that works for one student may fail for another student with the same subscription type.
- CvWykJun 04, 2026Copper Contributor
I appreciate your quick response Carlos Chavez 🤩
Thank you for confirming that our troubleshooting sheet matching your steps is correct. Our teachers discovered these independently and we figured it all out ourselves. I am unsure if any documentation exists to warn educators.We understand your steps. However, sometimes its a block on all 5 allowed regions. So it was a question of, can the policies clash so badly that a student cannot find a size or an available region?
The one student even had an error basically saying that the policy has 'not started', so it seems it was stuck?