An Azure service that is used to implement corporate governance and standards at scale for Azure resources.
Hello Makeki, it looks like your Azure for Students subscription has an Azure Policy in place that only allows deployments into a specific set of regions. When you try to spin up a VM outside those regions (or with a disallowed SKU), you’ll hit the “RequestDisallowedByAzure” error on every resource in your template.
Here’s how you can unblock yourself:
- Identify exactly which regions are allowed • Run this in Cloud Shell or Azure CLI (replace
<SUB_ID>with your subscription ID):
• That will spit out the array of allowed Azure regions for your Student subscription (typically things like East US 2, West US 2, Central US, North Europe, West Europe, Australia East, etc.).az policy assignment list \ --scope /subscriptions/<SUB_ID> \ --query "[?contains(name,'SubscriptionLocation')].parameters.allowedLocations.value" \ -o table - Redeploy into one of those locations • Update your ARM template or CLI command to use one of the allowed regions. For example:
• Make sure the VM SKU you choose (e.g. Standard_B2s) is also on the “allowed SKUs” list for your subscription.az vm create \ --name myVM \ --resource-group myRG \ --image UbuntuLTS \ --size Standard_B2s \ --location eastus2 - Double-check your subscription status • In the portal go to Subscriptions → Azure for Students and confirm it’s “Active”. • Under “Usage + quotas” you should see your remaining credit. If it still shows zero or “no active subscription” at microsoftazuresponsorships.com, you may need to raise a support ticket so the sponsorship account gets properly re-activated.
- If you need other regions or SKUs • Student subscriptions are locked down by policy—you can’t modify or disable that yourself. • File a support request and reference the policy assignment blocking your deployments. Support can either grant you an exception or guide you on next steps.
Hope that gets you unstuck! If you’re still seeing the same policy error after picking an allowed region, let us know:
• Which region(s) you tried
• Exact VM size you’re requesting
• The full JSON error (with policyAssignmentId) from your failed deployment
References
• Troubleshoot “Resource creation was disallowed by policy”:
• Resolve RequestDisallowedByPolicy for Azure VMs:
https://dori-uw-1.kuma-moon.com/azure/governance/policy/tutorials/create-and-manage#troubleshooting
• List policy assignments via CLI:
https://dori-uw-1.kuma-moon.com/cli/azure/policy/assignment#az_policy_assignment_list