Unable to change VM Size D2ds_v5 to D2ds_v6

Question

Unable to change VM Size D2ds_v5 to D2ds_v6

Sean Bernard 5

Hi,

I try to change the size of a vm in Germany West Central from Standard_D2ds_v5 to Standard_D2ds_v6. But I receive the following error:

Update-AzVM: Unable to resize the VM 'VMNAME' since changing from resource disk to non-resource disk VM size and vice-versa is not allowed. Please refer to https://aka.ms/AAah4sj for more details.

ErrorCode: OperationNotAllowed

ErrorMessage: Unable to resize the VM 'RemotePC01' since changing from resource disk to non-resource disk VM size and vice-versa is not allowed. Please refer to https://aka.ms/AAah4sj for more details.

ErrorTarget:

StatusCode: 409

ReasonPhrase:

OperationID : 520a14a5-3379-4255-bd97-6b5fa84bbe73

I don't know why. Because I change from an size with temp disk to an vm size also with an temp disk.

Could you help me?

Deepanshu katara 16,720 Reputation points MVP Moderator

2025-02-18T17:13:27.9966667+00:00
Hello Sean, Welcome to MS Q&A

The error you're encountering when trying to change the VM size from Standard_D2ds_v5 to Standard_D2ds_v6 in Germany West Central is due to the restriction on changing from a VM size with a resource disk to one without, and vice-versa. This is a common limitation in Azure when dealing with VM size changes.

To resolve this, you should check if the Standard_D2ds_v6 size is supported in the Germany West Central region and ensure that you have the necessary quotas available for that size. You might need to consider resizing to a different VM size that doesn't have this restriction or create a new VM with the desired size and migrate your workloads.

For more detailed information, you can refer to the following resources:

Ddsv6 sizes series

Dldsv6 sizes series

Please let us know if further questions

Kindly accept answer if it helps

Thanks

Deepanshu
Mounika Reddy Anumandla 6,840 Reputation points Microsoft External Staff Moderator

2025-02-20T03:21:55.5766667+00:00

Hi Sean Bernard,

Just checking in to see if you had a chance to review answer provided by Deepanshu katara on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please accept answer and click "Upvote" on the post.

Thank You.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mounika Reddy Anumandla 6,840 Reputation points Microsoft External Staff Moderator

2025-02-27T03:39:37.4433333+00:00

Hi Fernando Gomes,

I understand your concern. Although Deepanshu katara provided a solid explanation of potential resizing issues, and he identified that Azure has restrictions on resizing between certain VM sizes. However, since both D2ds_v5 and D2ds_v6 include temporary disks, the error message suggests another underlying reason—likely related to Azure’s SKU architecture.

Here's a more refined approach to troubleshooting and resolving this issue that Karishma addressed here: https://learn.microsoft.com/en-us/answers/questions/118056/unable-to-resize-vm-(d2s-v3-)-d2s-v4))

Hope this helps!
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Fernando Gomes 30 Reputation points

2025-02-27T10:08:54.8566667+00:00

Hi, @Sean Bernard I've struggled with this issue when I rushed to resize a test VM as soon as the V6 went into general availability.

At the time I didn't find any updated info regarding this issue you've just stumbled at.

You can read this thread which I started https://learn.microsoft.com/en-gb/answers/questions/2131146/why-cant-i-resize-a-ads-v5-vm-to-ads-v6

But you'll find that most people just mention the "you can only resize a VM with a local temporary disk to another VM with a local temporary disk" crap which does not apply to our needs.

What I can tell you is that the culprit has something to do with how these VMs don't consider a NVMe temporary disk as the old SCSI versions did.

You can come to this conclusion by creating and trying to resize a couple of test VMs which are availabe with both NVMe and SCSI: E2bds_v5

Virtual Machine A - E2bds_v5 with NMVe disabled (effectively SCSI disk controller)

Virtual Machine B - E2bds_v5 with NMVe enabled

Resizing VM A to Standard_D2ds_v6 you get the error you've mentioned. There is no path to resize here.

Resizing Virtual Machine B to Standard_D2ds_v6 you can convert to Standard_D2ds_v6 (with temp disk) and you can also convert to Standard_D2s_v6 (with NO temp disk).

The fact that you can convert a VM with a temp disk to a VM without temp disk is counter intuitive, but this is what happens.

We're going to test converting our E32ads V5 to a E32bds_V5, then convert that to NMVe (there is a script around for that, google it) and then convert to a E32ads_V6.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 answer

Your answer

Deepanshu katara 16,720 Reputation points MVP Moderator

2025-02-18T17:13:27.9966667+00:00

Hello Sean, Welcome to MS Q&A

The error you're encountering when trying to change the VM size from Standard_D2ds_v5 to Standard_D2ds_v6 in Germany West Central is due to the restriction on changing from a VM size with a resource disk to one without, and vice-versa. This is a common limitation in Azure when dealing with VM size changes.

To resolve this, you should check if the Standard_D2ds_v6 size is supported in the Germany West Central region and ensure that you have the necessary quotas available for that size. You might need to consider resizing to a different VM size that doesn't have this restriction or create a new VM with the desired size and migrate your workloads.

For more detailed information, you can refer to the following resources:

Ddsv6 sizes series

Dldsv6 sizes series

Please let us know if further questions

Kindly accept answer if it helps

Thanks

Deepanshu
Mounika Reddy Anumandla 6,840 Reputation points Microsoft External Staff Moderator

2025-02-20T03:21:55.5766667+00:00

Hi Sean Bernard,

Just checking in to see if you had a chance to review answer provided by Deepanshu katara on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please accept answer and click "Upvote" on the post.

Thank You.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mounika Reddy Anumandla 6,840 Reputation points Microsoft External Staff Moderator

2025-02-27T03:39:37.4433333+00:00

Hi Fernando Gomes,

I understand your concern. Although Deepanshu katara provided a solid explanation of potential resizing issues, and he identified that Azure has restrictions on resizing between certain VM sizes. However, since both D2ds_v5 and D2ds_v6 include temporary disks, the error message suggests another underlying reason—likely related to Azure’s SKU architecture.

Here's a more refined approach to troubleshooting and resolving this issue that Karishma addressed here: https://learn.microsoft.com/en-us/answers/questions/118056/unable-to-resize-vm-(d2s-v3-)-d2s-v4))

Hope this helps!
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Fernando Gomes 30 Reputation points

2025-02-27T10:08:54.8566667+00:00

Hi, @Sean Bernard I've struggled with this issue when I rushed to resize a test VM as soon as the V6 went into general availability.

At the time I didn't find any updated info regarding this issue you've just stumbled at.

You can read this thread which I started https://learn.microsoft.com/en-gb/answers/questions/2131146/why-cant-i-resize-a-ads-v5-vm-to-ads-v6

But you'll find that most people just mention the "you can only resize a VM with a local temporary disk to another VM with a local temporary disk" crap which does not apply to our needs.

What I can tell you is that the culprit has something to do with how these VMs don't consider a NVMe temporary disk as the old SCSI versions did.

You can come to this conclusion by creating and trying to resize a couple of test VMs which are availabe with both NVMe and SCSI: E2bds_v5

Virtual Machine A - E2bds_v5 with NMVe disabled (effectively SCSI disk controller)

Virtual Machine B - E2bds_v5 with NMVe enabled

Resizing VM A to Standard_D2ds_v6 you get the error you've mentioned. There is no path to resize here.

Resizing Virtual Machine B to Standard_D2ds_v6 you can convert to Standard_D2ds_v6 (with temp disk) and you can also convert to Standard_D2s_v6 (with NO temp disk).

The fact that you can convert a VM with a temp disk to a VM without temp disk is counter intuitive, but this is what happens.

We're going to test converting our E32ads V5 to a E32bds_V5, then convert that to NMVe (there is a script around for that, google it) and then convert to a E32ads_V6.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

TP 125.7K Volunteer Moderator

Hi Sean,

Unfortunately you cannot directly resize VM from Standard_D2ds_v5 to Standard_D2ds_v6 because Standard_D2ds_v6 effectively does not have a local temporary disk.

Please see screenshot below where Standard_D2ds_v6 shows 0 for ResourceDiskSizeInMB and Standard_D2ds_v5 shows 76800:

User's image

Yes, Standard_D2ds_v6 does have a local temporary disk, however, it is NVMe, and is presented to the VM as a raw disk each first time the VM boots after being allocated to a physical host. Since the disk is raw, the OS won't be able to initialize paging file on it during startup.

This is different than Standard_D2ds_v5, in which the local temporary disk is presented as NTFS/ext4 drive, ready for use by paging/swap file.

Azure prevents the resize in order to avoid potential issues since the current size (Standard_D2ds_v5) is likely configured with paging file on temporary disk.

Please see article below for things to consider when using VM sizes with temporary NVMe drives:

https://learn.microsoft.com/en-us/azure/virtual-machines/enable-nvme-temp-faqs#what-changes-should-i-prepare-for-when-configuring-my-vms-with-temp-nvme-disks-

Workaround/Solution:

You can follow steps in article below to manually migrate your VM to the new size:

https://learn.microsoft.com/en-us/azure/virtual-machines/azure-vms-no-temp-disk#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Fernando Gomes 30 Reputation points

2025-02-28T08:46:22.39+00:00

Finally a proper answer. Thank you for your explanation, this was helpful.
Fernando Gomes 30 Reputation points

2025-02-28T08:54:30.62+00:00

Hey, TP, can I ask you to post the same answer at this post so I can accept your answer, please?

https://learn.microsoft.com/en-gb/answers/questions/2131146/why-cant-i-resize-a-ads-v5-vm-to-ads-v6
TP 125.7K Reputation points Volunteer Moderator

2025-02-28T09:14:19.45+00:00

Hey, TP, can I ask you to post the same answer at this post so I can accept your answer, please?

@Fernando Gomes Sure. Please give me some time and I'll post over there.

Thank you.
Mounika Reddy Anumandla 6,840 Reputation points Microsoft External Staff Moderator

2025-03-12T15:43:30.8666667+00:00

Hi

I appreciate TP for driving us all to the appropriate answer and his contribution here.

and also @Fernando Gomes for his insightful feedback, which has been incredibly helpful!

I hope Sean Bernard has successfully resolved his issue! Since it has been a few days, I kindly request him to consider marking the answer as helpful by clicking 'Accept Answer' and 'Upvote.'

Doing so will assist other community members in finding the right solution more easily.

Share via

Unable to change VM Size D2ds_v5 to D2ds_v6

1 answer

Your answer