i'm troubleshooting some unattached premium disks i found in a resource group containing a functioning vm and its attached disks
prior to this i know of 2 actions that might have triggered this
- during the arm template debug cycle extra disks may have been created
- during the performance testing the vm disk was resized from the portal a few times
i'm wondering what the expected behaviour is for the latter action, resize vm disk from the portal
the question is, does/should resizing the vm disk from the portal leave the old disk orphaned or is it deleted?