This size is currently unavailable in the **** location for this subscription: NotAvailableForSubscription

Hello @Dasha Rogozinskaya ,

The reason for failure is that the free subscription doesn't have availability of the B1s in all the regions due to which when you are trying to create VMs in your choice of regions you are seeing the failure with error code "NotAvailableForSubscription".

Solution?

You can try command as az vm list-skus in more details with your preferred regions and see if you have the restrictions with those regions using Azure CLI.

To check for all regions with all the details, I used below command and it showed me which regions had:-

az vm list-skus \
 --resource-type virtualMachines \
 --all \
 --query "[?name=='Standard_B1s'].{
     Name: name,
     Locations: locations,
     Restrictions: restrictions
 }" \
 --output json

In the output, if you see ReasonCode: "NotAvailableForSubscription" then you won't be able to create VM in that region.

Based on this output you can find out what regions doesn't have reasonCode as "NotAvailableForSubscription" and you can select the region to create the VM.

Additionally, please note there is a bug in the Marketplace Free VM offer that has public IP set to Standard SKU (correct), but still has allocation set to Dynamic (incorrect). What you can do is manually create VM using correct parameters to qualify for free. To start the process you may use link below (this is for Linux with notes for Windows VM after):

https://portal.azure.com/#create/Microsoft.VirtualMachine

For Linux, when creating, set

Size: Standard_B1s Image: Ubuntu Server 22.04 LTS - x64 Gen2 OS disk size: 64 GiB (P6) OS disk type: Premium SSD (locally-redundant storage) Monitoring tab: Boot diagnostics: Disable

Don't enable any of the options if you want to avoid charges, for example, if you turned on Backup that has a charge associated with it.

After creating VM, please monitor costs (at least daily) by navigating to your subscription. If you used correct parameters for the VM you should not see any charges accrue related to it, except for the public IP address. Charges are delayed, so it will take typically several hours (after creation) before any would show up.

If you associate Public IP address with the VM you will be charged for this (about $3.65/month each). You can minimize the charges by dissociating it from the VM's network interface and deleting it when you are not using the VM.

When you want to use VM again you would create Public IP and associate it with VM's network interface.

For Windows you would use [smalldisk] Windows Server images with P6 LRS disk.

After creating Linux VM you should expand the partition so you are using the full 64 GiB:

https://learn.microsoft.com/en-us/azure/virtual-machines/linux/expand-disks?tabs=ubuntu#expand-a-disk-partition-and-filesystem

After creating Windows VM you should expand disk so you are using full 64 GiB:

https://learn.microsoft.com/en-us/azure/virtual-machines/windows/expand-disks