This feature is maybe a good idea, but crashes decommission processes. While it might be really nice to be protected against attacks or accidental deletions it makes the life hard if you have to remove customer data, especially if you are liable to do that after contract cancellations. It fully prevents the deletion of backups for 14 days if you want that or not. It makes it impossible to set up the backup again with the same vault names, even if you move vault out of the current resourcegroup. A renaming of the vault seem to be also not possible. So we urgently need an administrator role which makes it possible to override the soft delete! Why having that feature mandatory at backup vaults, whilst for storage blob immuteable policy you can choose to lock it or not? It is not a standardization as I would expect it in Azure when everything is handled in different ways.
295 votesplanned · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
This is still coming. The work is being completed now and we will be able to expose it in a few months.
Any news here? It should be normal that associated devices will be removed with the VM. Normally it is not needed anymore. Why keep it?
I do not understand why this is not yet implemented. Firewall on the account is absolutely senseless if you cannot access console. Btw. I also notice the same problem exists for Azure Functions which cannot access protected storage accounts and Azure Logic Apps even that are all Azure internal services. So I did not find any possibility to automate the removal of old files.