My subscription usage exceeded what was included and my VM was auto-deleted. I removed the usage restriction such that I incur pay-as-you-go charges now.
I deleted the Disk (that was attached to the deleted VM) using Remove-AzureDisk -DiskName <disk name>. This completed successfully and the disk that was listed in the preview portal which was attached to a non-existent VM instance was removed.
I attempted to use the VM Portal to create a new disk based on the original VHD. This failed stating that there was a lease conflict. I thought this was weird since by deleting the VM Disk attached to the deleted VM, I had removed all leases.
So in order to get my VM back up ASAP, I used myazurestorage.com to make a copy of the VHD. I then created a new VM Disk based on the new (copied) VHD, and subsequently attached it to a new VM instance. This worked well.
I then tried to delete the original VHD using the myazurestorage.com interface, but it gave me the following error:
There is currently a lease on the blob and no lease ID was specified in the request
So I can neither create a new VM Disk based on the original VHD nor can I delete the VHD itself.
Is there some kind of delay between deleting a VM Disk via "Remove-AzureDisk" and the actual removal of the associated lease to the VHD?
I have previously gone through deleting a Disk that was attached to a deleted VM, creating a new disk from the same VHD, and then attaching it to a new VM...I'm puzzled as to why I get different results now from using the same method as before that worked
a week ago.
Any help would be appreciated!