my azure account is ""; so far I am not successful getting any Quick Start successfully run :(
average@Azure:~$ az vm create \
> --resource-group myResourceGroup \
> --name myVm1 \
> --image UbuntuLTS \
> --generate-ssh-keys \
> --no-wait
Azure Error: InvalidTemplateDeployment
Message: The template deployment failed with error: 'The resource with id: '/subscriptions/26429ee2-925c-4abd-8922-b071069fe5f1/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVm1' failed validation with message: 'The requested size for resource '/subscriptions/26429ee2-925c-4abd-8922-b071069fe5f1/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVm1' is currently not available in location 'eastus' zones '' for subscription '26429ee2-925c-4abd-8922-b071069fe5f1'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.'.'.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Another issue : after I copy snippet by pressing tryit button doesn't move focus to shell
This issue is not important but misleading tutorial / quickstart will discourage me from evaluating Azure.
@forvaidya This error has to do with an issue with your subscription, not with the tutorial. As is stated in the error, you can go to https://aka.ms/azureskunotavailable for instructions on how to see what region and VM sizes you are able to deploy.
Use the --size parameter of the az vm create cmd to specify a specific size for your subscription.
I apologize for the inconvenience with VM allocations, Azure is experiencing an abnormally high usage with the current global situation. Many accounts have temporary regional and SKU restrictions put in place, and this is why you are getting the deployment failure.
--size parameter I am also curious to know how will it know size otherwise, is there a place where defaults are configured ?
Please don't close this ticket as I look forward learn about azure within limits of 1 month credit
az vm list-sizes --location eastus | jq '.[] .name' |wc -l gave me some 280 sizes ? Please guide me which one applicable for my trial subscription ?
@forvaidya I would find a size with a low core count for your trial. Standard_A0, D1_V2, B1, B1ms, and Standard_A1 are all great sizes to use for trials. Find one with a low core count that shows available capacity and does not have the "notavailableforsubscription" restriction.
For the AZ VM command:
az vm create
> --resource-group myResourceGroup
> --name myVm1
> --image UbuntuLTS
> --generate-ssh-keys
> --no-wait
> --size "Standard_A0"
This too failed
average@Azure:~$ az vm create --resource-group myResourceGroup --name myVm1 --image UbuntuLTS --generate-ssh-keys --size Standard_A0 --no-wait
Azure Error: InvalidTemplateDeployment
Message: The template deployment failed with error: 'The resource with id: '/subscriptions/26429ee2-925c-4abd-8922-b071069fe5f1/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVm1' failed validation with message: 'The requested size for resource '/subscriptions/26429ee2-925c-4abd-8922-b071069fe5f1/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVm1' is currently not available in location 'eastus' zones '' for subscription '26429ee2-925c-4abd-8922-b071069fe5f1'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.'.'.
average@Azure:~$
I have tried for following sizes ; eastus region and failed each time
Standard_A0"
"Standard_A1"
"Standard_A10"
"Standard_A11"
"Standard_A1_v2"
"Standard_A2"
"Standard_A2m_v2"
"Standard_A2_v2"
"Standard_A3"
"Standard_A4"
"Standard_A4m_v2"
"Standard_A4_v2"
"Standard_A5"
"Standard_A6"
"Standard_A7"
"Standard_A8"
"Standard_A8m_v2"
"Standard_A8_v2"
"Standard_A9"
@forvaidya did that size / region show a "notavailableforsubscription" restriction when you run the following command?
az vm list-skus --location eastus --output table
OK - This size StandardSSD_LRS Did not work
Can you introduce a step in your scripts to determine lowest possible size (programatically) in current region so that tutorial step is successful
Will explore further over weekend
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
"details": [
{
"code": "BadRequest",
"message": "{\r\n \"error\": {\r\n \"code\": \"InvalidParameter\",\r\n \"message\": \"The requested VM size StandardSSD_LRS is not available in the current region. The sizes available in the current region are: Standard_B1ls,Standard_B1ms,Standard_B1s,Standard_B2ms,Standard_B2s,Standard_B4ms,Standard_B8ms,Standard_B12ms,Standard_B16ms,Standard_B20ms,Standard_DS1_v2,Standard_DS2_v2,Standard_DS3_v2,Standard_DS4_v2,Standard_DS5_v2,Standard_DS11-1_v2,Standard_DS11_v2,Standard_DS12-1_v2,Standard_DS12-2_v2,Standard_DS12_v2,Standard_DS13-2_v2,Standard_DS13-4_v2,Standard_DS13_v2,Standard_DS14-4_v2,Standard_DS14-8_v2,Standard_DS14_v2,Standard_DS15_v2,Standard_DS2_v2_Promo,Standard_DS3_v2_Promo,Standard_DS4_v2_Promo,Standard_DS5_v2_Promo,Standard_DS11_v2_Promo,Standard_DS12_v2_Promo,Standard_DS13_v2_Promo,Standard_DS14_v2_Promo,Standard_F1s,Standard_F2s,Standard_F4s,Standard_F8s,Standard_F16s,Standard_D2s_v3,Standard_D4s_v3,Standard_D8s_v3,Standard_D16s_v3,Standard_D32s_v3,Standard_D1_v2,Standard_D2_v2,Standard_D3_v2,Standard_D4_v2,Standard_D5_v2,Standard_D11_v2,Standard_D12_v2,Standard_D13_v2,Standard_D14_v2,Standard_D2_v2_Promo,Standard_D3_v2_Promo,Standard_D4_v2_Promo,Standard_D5_v2_Promo,Standard_D11_v2_Promo,Standard_D12_v2_Promo,Standard_D13_v2_Promo,Standard_D14_v2_Promo,Standard_F1,Standard_F2,Standard_F4,Standard_F8,Standard_F16,Standard_A1_v2,Standard_A2m_v2,Standard_A2_v2,Standard_A4m_v2,Standard_A4_v2,Standard_A8m_v2,Standard_A8_v2,Standard_D2_v3,Standard_D4_v3,Standard_D8_v3,Standard_D16_v3,Standard_D32_v3,Standard_D48_v3,Standard_D64_v3,Standard_D48s_v3,Standard_D64s_v3,Standard_E2_v3,Standard_E4_v3,Standard_E8_v3,Standard_E16_v3,Standard_E20_v3,Standard_E32_v3,Standard_E48_v3,Standard_E64_v3,Standard_E2s_v3,Standard_E4-2s_v3,Standard_E4s_v3,Standard_E8-2s_v3,Standard_E8-4s_v3,Standard_E8s_v3,Standard_E16-4s_v3,Standard_E16-8s_v3,Standard_E16s_v3,Standard_E20s_v3,Standard_E32-8s_v3,Standard_E32-16s_v3,Standard_E32s_v3,Standard_E48s_v3,Standard_E64-16s_v3,Standard_E64-32s_v3,Standard_E64s_v3,Standard_A0,Standard_A1,Standard_A2,Standard_A3,Standard_A5,Standard_A4,Standard_A6,Standard_A7,Basic_A0,Basic_A1,Basic_A2,Basic_A3,Basic_A4,Standard_D15_v2,Standard_E64i_v3,Standard_E64is_v3,Standard_H8,Standard_H8_Promo,Standard_H16,Standard_H16_Promo,Standard_H8m,Standard_H8m_Promo,Standard_H16m,Standard_H16m_Promo,Standard_H16r,Standard_H16r_Promo,Standard_H16mr,Standard_H16mr_Promo,Standard_D1,Standard_D2,Standard_D3,Standard_D4,Standard_D11,Standard_D12,Standard_D13,Standard_D14,Standard_NV6,Standard_NV12,Standard_NV24,Standard_NV6_Promo,Standard_NV12_Promo,Standard_NV24_Promo,Standard_NC6s_v2,Standard_NC12s_v2,Standard_NC24rs_v2,Standard_NC24s_v2,Standard_F2s_v2,Standard_F4s_v2,Standard_F8s_v2,Standard_F16s_v2,Standard_F32s_v2,Standard_F48s_v2,Standard_F64s_v2,Standard_F72s_v2,Standard_NC6,Standard_NC12,Standard_NC24,Standard_NC24r,Standard_NC6_Promo,Standard_NC12_Promo,Standard_NC24_Promo,Standard_NC24r_Promo,Standard_L8s_v2,Standard_L16s_v2,Standard_L32s_v2,Standard_L48s_v2,Standard_L64s_v2,Standard_L80s_v2,Standard_NV6s_v2,Standard_NV12s_v2,Standard_NV24s_v2,Standard_NV12s_v3,Standard_NV24s_v3,Standard_NV48s_v3,Standard_DC8_v2,Standard_DC1s_v2,Standard_DC2s_v2,Standard_DC4s_v2,Standard_NP10s,Standard_NP20s,Standard_NP40s,Standard_DS1,Standard_DS2,Standard_DS3,Standard_DS4,Standard_DS11,Standard_DS12,Standard_DS13,Standard_DS14,Standard_HC44rs,Standard_D2a_v4,Standard_D4a_v4,Standard_D8a_v4,Standard_D16a_v4,Standard_D32a_v4,Standard_D48a_v4,Standard_D64a_v4,Standard_D96a_v4,Standard_D2as_v4,Standard_D4as_v4,Standard_D8as_v4,Standard_D16as_v4,Standard_D32as_v4,Standard_D48as_v4,Standard_D64as_v4,Standard_D96as_v4,Standard_E2a_v4,Standard_E4a_v4,Standard_E8a_v4,Standard_E16a_v4,Standard_E20a_v4,Standard_E32a_v4,Standard_E48a_v4,Standard_E64a_v4,Standard_E96a_v4,Standard_E2as_v4,Standard_E4as_v4,Standard_E8as_v4,Standard_E16as_v4,Standard_E20as_v4,Standard_E32as_v4,Standard_E48as_v4,Standard_E64as_v4,Standard_E96as_v4,Standard_ND6s,Standard_ND12s,Standard_ND24rs,Standard_ND24s,Standard_DC2s,Standard_DC4s,Standard_M208ms_v2,Standard_M208s_v2,Standard_M416s_v2,Standard_M416ms_v2,Standard_NC6s_v3,Standard_NC12s_v3,Standard_NC24rs_v3,Standard_NC24s_v3,Standard_PB6s,Standard_HB60rs,Standard_ND40s_v3,Standard_M8-2ms,Standard_M8-4ms,Standard_M8ms,Standard_M16-4ms,Standard_M16-8ms,Standard_M16ms,Standard_M32-8ms,Standard_M32-16ms,Standard_M32ls,Standard_M32ms,Standard_M32ts,Standard_M64-16ms,Standard_M64-32ms,Standard_M64ls,Standard_M64ms,Standard_M64s,Standard_M128-32ms,Standard_M128-64ms,Standard_M128ms,Standard_M128s,Standard_M64,Standard_M64m,Standard_M128,Standard_M128m,Standard_A8,Standard_A9,Standard_A10,Standard_A11,Standard_ND40rs_v2,Standard_NV4as_v4,Standard_NV8as_v4,Standard_NV16as_v4,Standard_NV32as_v4.\r\nFind out more on the available VM sizes in each region at https://aka.ms/azure-regions.\",\r\n \"target\": \"vmSize\"\r\n }\r\n}"
}
]
}
@forvaidya I am unsure why that command is pulling disk sizes & other objects, but you want to start where the Resourcetype = VirtualMachines for a proper SKU
OK - can microsoft santize and verify tutorial (atleast most common ones) and make it autonomous.
1st times user should not be required to dig around and just copy paste of steps should work to make quickstart / tutorials a pleasent experience
I look forward to hear from Azure soon
@forvaidya This tutorial has been validated and is working as expected. As I have stated before, this is an issue with your specific subscription that is a result of the abnormally high usage Azure has been receiving.
If you would like further assistance in getting this working with your subscription, I would be happy to work with you. Please Email me at [email protected] with your subscription ID and a link to this post if you would like to continue.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.