Hi,
Reason you are not seeing B4ms is because it includes temporary disk whereas the current size does not include temporary disk. When using resize capability, you are limited to sizes with no temporary disk. If your current size included temporary disk, you would be limited to sizes that do include temporary disk. Please see FAQ:
Can I resize a VM size that has a local temp disk to a VM size with no local temp disk?
Workaround/Solution:
What you can do is stop the VM, create snapshot of disk, create disk from snapshot, then create VM from disk, with B4ms 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 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