Azure VM creation issue - OperationNotAllowed, disk size

Question

Azure VM creation issue - OperationNotAllowed, disk size

Pflipper 106

I'm trying to create a second VM on my Azure account. When I am in my account and select Virtual machines, click on "+ Add", then choose the "+ Virtual machine", I get an error - "Oops!, Could not create Virtual machine. Something went wrong while creating Virtual machine."

Oops. Great message for the user, Microsoft.

Figuring that there's always another way, I choose the "+ Start with preset configuration" option (the only other one). I make all the available option selections for my VM, start deployment, but it always fails with this message : "The specified disk size 64 GB is smaller than the size of the corresponding disk in the VM image: 127 GB. This is not allowed. Please choose equal or greater size or do not specify an explicit size. (Code: OperationNotAllowed)"

I can only imagine there there is some option to select the disk size, but there is nowhere in the preset configuration choice to choose a different disk size. And the first choice always gives me the "Oops" message. So I'm stuck between two options that do not work.

Since Microsoft is so nice as to not provide support for paying customers unless you pay and extra $30/month for basic support, I am here in the community asking if someone was run into this and has a solution.

Thanks in advance for any pointers!

Sam Cogan 10,812 Reputation points Microsoft Employee Volunteer Moderator

2021-02-11T09:50:18.54+00:00

What VM type are you trying to create?
Pflipper 106 Reputation points

2021-02-11T15:18:46.233+00:00

Sam, I'll tell you what I select, you tell me if you get the information you are requesting. And because this message board post limits responses to 1000 characters (!), I have to break the post up into a few entries.

First scenario - In my Azure account, Select Home, Select Virtual Machines icon at the top, Select +Add, Select +Virtual Machine, - Blam. Brick wall message -- "Oops!, Could not create Virtual machine. Something went wrong while creating Virtual machine."

Doesn't look like I get to select any VM type there.
Pflipper 106 Reputation points

2021-02-11T15:19:23.91+00:00
Second scenario - In my Azure account, Select Home, Select Virtual Machines at the top, Select +Add, this time Select +Start with a preset configuration, bypass all the preset workload options (I do not want D, or E, or F series which are the only options), Select "Skip this step", Now I get options, here's what I select:

an existing resource group

put in my virutal machine name (UADVM19)

keep my region (US West 2)

Choose Windows Server 2019 Datacenter - Gen1

Not a spot image, so don't check that

Size is B2s - 2 vcpus, 4GiB ---> maybe this is the type that you are referencing?

UserName, password of my choosing

Inbound port - allow RDP 3389

No check on Licensing Azure Hybrid
Now click next for Tags, bypass adding any tags, click on Review and Create. Once here I get the message that the Validation passed, and I click Create.
Pflipper 106 Reputation points

2021-02-11T15:19:42.487+00:00

Deployment begins, creates the publicIp, network security groups, virtual network and network interface, until the creation of the virtual machine, where I get the error:

{"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":"OperationNotAllowed","message":"The specified disk size 64 GB is smaller than the size of the corresponding disk in the VM image: 127 GB. This is not allowed. Please choose equal or greater size or do not specify an explicit size."}]}

So, if you can pick out anything here that I did wrong, did not do right, please let me know. I do have another VM up and running in Windows Server 2012 r2 (created sometime in the summer), and from what I can remember is was pretty easy to create.
prmanhas-MSFT 17,946 Reputation points Microsoft Employee Moderator

2021-02-16T16:10:28.927+00:00

@Pflipper Can you please confirm if you need any further help on the issue?

Thanks
Pflipper 106 Reputation points

2021-02-16T16:54:16.96+00:00

I can confirm that I do not need any further help on this at the moment. As mentioned, I do believe that something was corrected on the Azure side by Microsoft, either on my account or on the portal as a whole. Unfortunately, no Microsoft resource contacted me or posted that they fixed it, so I am left to wonder why there was no notification of this fix anywhere, or if any request by me to correct it was the impetus of the correction.

3 answers

Your answer

Sam Cogan 10,812 Reputation points Microsoft Employee Volunteer Moderator

2021-02-11T09:50:18.54+00:00

What VM type are you trying to create?
Pflipper 106 Reputation points

2021-02-11T15:18:46.233+00:00

Sam, I'll tell you what I select, you tell me if you get the information you are requesting. And because this message board post limits responses to 1000 characters (!), I have to break the post up into a few entries.

First scenario - In my Azure account, Select Home, Select Virtual Machines icon at the top, Select +Add, Select +Virtual Machine, - Blam. Brick wall message -- "Oops!, Could not create Virtual machine. Something went wrong while creating Virtual machine."

Doesn't look like I get to select any VM type there.
Pflipper 106 Reputation points

2021-02-11T15:19:23.91+00:00

Second scenario - In my Azure account, Select Home, Select Virtual Machines at the top, Select +Add, this time Select +Start with a preset configuration, bypass all the preset workload options (I do not want D, or E, or F series which are the only options), Select "Skip this step", Now I get options, here's what I select:

an existing resource group

put in my virutal machine name (UADVM19)

keep my region (US West 2)

Choose Windows Server 2019 Datacenter - Gen1

Not a spot image, so don't check that

Size is B2s - 2 vcpus, 4GiB ---> maybe this is the type that you are referencing?

UserName, password of my choosing

Inbound port - allow RDP 3389

No check on Licensing Azure Hybrid
Now click next for Tags, bypass adding any tags, click on Review and Create. Once here I get the message that the Validation passed, and I click Create.
Pflipper 106 Reputation points

2021-02-11T15:19:42.487+00:00

Deployment begins, creates the publicIp, network security groups, virtual network and network interface, until the creation of the virtual machine, where I get the error:

{"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":"OperationNotAllowed","message":"The specified disk size 64 GB is smaller than the size of the corresponding disk in the VM image: 127 GB. This is not allowed. Please choose equal or greater size or do not specify an explicit size."}]}

So, if you can pick out anything here that I did wrong, did not do right, please let me know. I do have another VM up and running in Windows Server 2012 r2 (created sometime in the summer), and from what I can remember is was pretty easy to create.
prmanhas-MSFT 17,946 Reputation points Microsoft Employee Moderator

2021-02-16T16:10:28.927+00:00

@Pflipper Can you please confirm if you need any further help on the issue?

Thanks
Pflipper 106 Reputation points

2021-02-16T16:54:16.96+00:00

I can confirm that I do not need any further help on this at the moment. As mentioned, I do believe that something was corrected on the Azure side by Microsoft, either on my account or on the portal as a whole. Unfortunately, no Microsoft resource contacted me or posted that they fixed it, so I am left to wonder why there was no notification of this fix anywhere, or if any request by me to correct it was the impetus of the correction.

Answer 1

Michal Barták 231

Was actually kind of surprised by this error so I tried to deploy it with your config and everything went fine.

Could you please share the template json so we can check the full config?

Answer 2

Hi michalbartak,
'
'You wouldn't happen to be the former Access program manager would you? If you are, I've met you at a Denver Access users group. Hope you are well.

I tried again, and wouldn't you know it both areas seem to be fixed. From my first attempts about two days ago until this morning, both areas were problems as described here in this post. Upon getting your post I tried again and for the first scenario there was no error and I was allowed to create a VM environment that included more options. I continued through the options, reviewed, then created the VM without issue. I'm in the VM testing it out now.

I do believe that something was corrected on the Azure side, so hopefully this post or another request to Azure technical services (where I did not pay for a developer help plan but instead created a support request to increase my "quota" for VMs, which is free to do) worked to have someone look at and correct the issue.

Regardless, all is fixed now. Thanks!

Answer 3

Michal Barták 231

Hi,

I am sadly not a former Access program manager nor I have been to Denver, but I hope you are well also :)

It could be there was a bug in Azure. It's not always flawless especially during Covid.

Happy it works now :)

Share via

Azure VM creation issue - OperationNotAllowed, disk size

3 answers

Your answer