Hi Victor,
Reason you are not seeing E4s_v5 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:
What you can do is stop the VM, create snapshot of disk, create disk from snapshot, then create VM from disk, with E4s_v5 as size. Once you verify the new VM is working okay you can delete the old VM and its disk, network interface, snapshot, etc.
Below are instructions for the process I just described:
https://learn.microsoft.com/en-us/azure/virtual-machines/attach-os-disk?tabs=portal
When creating the new managed disk from the snapshot, be sure to select the correct disk size and type.
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