Not Able to Delete Storage Account - Ensure these image(s) and/or disk(s) are removed before deleting this storage account


 

While deleting an Azure Storage Account you might come across the following error.

Storage account portalvhds9x8ddnOgp9tn2 has some active image(s) and/or disk(s), e.g. annayakNE-annayakNE-O-201410240936090519. Ensure these image(s) and/or disk(s) are removed before deleting this storage account.

SCENARIO 1 – DISKS

Image1

A storage account can’t be deleted if it has VHDs that are attached as disk. These disks are created when creating Azure IaaS VM and you might have deleted the VMs but the disks are still around with a lease on the VHD located in this storage account.

Below steps which will help you the delete all VHD blobs and storage containers for your account.

Please follow the below steps :

1. Delete the necessary VM which has a lease on this VHD (If not already deleted).

2. Delete the associated disks/images, while deleting these, please ensure to select ”Delete the associated VHD“. You could also delete the VHDs manually.

clip_image004

clip_image006

clip_image008

3. Once the associated VHD’s are deleted, you will be able to delete the storage account.

clip_image010

Image6

SCENARIO 2 – IMAGES

Login to Azure portal.
Navigate to Virtual Machine -> Images.

clip_image001[4]

Select the image : Annayak-1-8-1-0-1-Ubuntu-12-10.
Delete the image.
You can chose to delete the associated VHD.
After deleting the VHD, you should be able to delete the storage account.

Hope this helps you delete your storage accounts when you get the error “Storage account portalvhds9x8ddnOgp9tn2 has some active image(s) and/or disk(s), e.g. annayakNE-annayakNE-O-201410240936090519. Ensure these image(s) and/or disk(s) are removed before deleting this storage account”.

 

 

Regards,
Angshuman Nayak
Cloud Integration Engineering


Comments (3)

  1. Satya says:

    Thank you Angshuman, Yes your blog helps.

  2. Jasee says:

    Thanks. This helped me get to the actual entity that needed deleted first... kind of weird, but I guess it's because the os disk was "classic".

  3. Marc says:

    great this helped a lot

Skip to main content