Hi,
Reason you are not seeing D2sv5 is because it does not include temporary disk whereas the current size does include temporary disk. When using resize capability, you are limited to sizes with temporary disk since your current VM size has a temporary disk. Please see FAQ, excerpt below:
Can I resize a VM size that has a local temp disk to a VM size with no local temp disk? No. The only combinations allowed for resizing are:
- VM (with local temp disk) -> VM (with local temp disk); and
- VM (with no local temp disk) -> VM (with no local temp disk). If interested in a work around, please see next question.
Workaround/Solution:
Excerpt from FAQ article below:
How do I migrate from a VM size with local temp disk to a VM size with no local temp disk?
You can migrate by following these steps:
1. Connect to your Virtual Machine that has a local temporary disk (for example, a D: Drive) as a local admin.
2. Follow the guidelines on the "Temporarily move pagefile.sys to C drive" section of Use the D: drive as a data drive on a Windows VM to move the page file from the local temporary disk (D: drive) to the C: drive.
Note Follow the guidelines on the "Temporarily move pagefile.sys to C drive" section of Use the D: drive as a data drive on a Windows VM to move page file from the local temporary disk (D: drive) to C: drive. Deviation from the steps outlined will lead to the error message - "Unable to resize the VM since changing from resource disk to non-resource disk VM size and vice-versa is not allowed.
3. Take a snapshot of the VM by following the steps outlined in Create a snapshot using the portal or Azure CLI.
4. Use snapshot to create a new diskless VM (such as, Dv5, Dsv5, Dasv5, Ev5, Esv5, Easv5 series) by following the steps outlined in Create a virtual machine from a snapshot with CLI.
Please click Accept Answer and upvote if the above was helpful. If you are unsure about how to perform the steps above and/or still need assistance, add a comment below.
Thanks.
-TP