How to Fix Incorrect Disk Resize on SQL VM?

If your data disks are in a storage pool, you won’t be able to just resize the disk directly. You might need to add more disks to the pool instead. If it’s not in a pool, try extending the disk within the OS and see what happens!

While adding another disk is an option, I personally wouldn't recommend it. You end up paying more for multiple smaller disks, and you'll hit limits on your VM's capacity faster. My go-to approach is to avoid storage pools altogether:

1. Get new disks for both your data and log files at the sizes you need and attach them to the VM.
2. Stop and disable the SQL Server services.
3. Transfer all the files from the old disks to the new ones, ensuring permissions are intact.
4. Change the drive letters of the old disks.
5. Reassign the drive letters of the new disks to match the old ones.
6. Restart the SQL Server services.

This gives you fresh disks that you can extend easily down the line, but you won’t be able to extend them through Azure as before, which is fine in my opinion.

You can add another disk of the same size to your existing storage pool. Just keep in mind, doing it this way won’t really boost performance. If you're looking for both more space and better performance, you might want to create a new storage pool with multiple disks.