How to get access to creating VMs?

Question

Hey guys, I run a charity and just signed up for Azure - and it's most confusing thing I've ever had to configure. I've registered for multiple services (compute, network etc) but anytime I try to create a VM I get a message that either it's not available as part of my subscription or region - for every single option I tried and it fails. There's no way to raise a support ticket - it literally loops me in a circle of not having the right access to sub and checking another region - and if I try to use the request for extra region way the form simply does not allow me to proceed as it's telling me I've already got access and quotas to the vms im requesting.

This is extremely frustrating, CoPilot is absolutely useless at giving me advice - so any guidance or help is much appreciated

Many thanks

Answer 1

Welcome to Microsoft Q&A

Hello @Catalin Rolea,

I totally understand your frustration. This is extremely confusing for new users, but it is actually a safety setting on Microsoft's end, not a broken account.

You are trying to build a VM in a "busy" region (like East US or London), but your new Charity account hasn't been given permission to use those crowded spots yet.

The Solution:

1. Try a different Region: When you create the VM, change the "Region" dropdown.
   • Instead of the default, try selecting "North Europe", "West US 2", or "Central US".
   • Often, changing the location instantly fixes the "not available" error because those regions have more free space for new accounts.
2. Pick a smaller VM Size:
   • Click "See all sizes".
   • Look for the "B-Series" (like Standard_B2s). These are the most common "starter" VMs and are usually available when others are blocked.

You can try using Copilot suggesting VMsize using charity subscription just let me know if you were able to create the VM.

😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!

Answer 2

Hi @Catalin Rolea

Thank you for contacting us about the VM issue.

VM creation is blocked by an Azure Policy with a Deny effect applied at a higher scope. The fix is to either deploy a VM that complies with the policy, create a policy exemption, or update the policy assignment.

How to identify the exact policy blocking VM creation :

Please follow the steps below to identify the blocking policy:

1. In the Azure portal, go to Azure Policy
2. Navigate to Authoring → Assignments
3. Check for policy assignments at:
   • Management Group
     • Subscription
       • Resource Group
4. Look for policies with Effect = Deny that apply to:
   • Microsoft.compute/VM's
   • VM images, regions, or sizes

You can also confirm this from the deployment error message, which typically includes:

Please follow the below link to create a Policy Assignment request

https://learn.microsoft.com/en-us/azure/governance/policy/assign-policy-portal

Portal>Policy>Assignments>Assign Policy >Basics Tab > Policy Definitions >Next and create Review.

Pls follow the link for the detailed steps.

Alternative workaround to work :

1.Make the deployment compliant :
Update the VM configuration so it complies with the assigned policy:

• Select an allowed region
• Choose an approved VM size
• Use an approved marketplace image
• Add any required tags

2.Create a policy exemption

Portal>Policy>Assignments>Assign Policy >Basics Tab > Policy Definitions >Next and create Review.

https://learn.microsoft.com/en-us/azure/governance/policy/tutorials/create-and-manage

Please try this steps and lets us know if you encounter any errors.

Also share the best available timings to connect with you offline.

Thanks

Manish.