How to delete a file share that's within a lock protected storage account?

Hello @MichaelB-2136

Thank you for posting your query on Microsoft Q&A platform.

When Azure Backup is enabled for any Azure File Share in a storage account, Azure Backup automatically applies an Azure Resource Manager (ARM) delete lock named AzureBackupProtectionLock on the storage account.

This behavior is by design to prevent accidental deletion of backup‑protected Azure File Shares and their backup data. Because the lock is applied at the storage account level, individual file shares inside the account cannot be deleted while the lock exists.

Reference:

Azure Backup applies management locks to prevent accidental deletions: https://dotnet.territoriali.olinfo.it/azure/backup/backup-azure-files

Azure resource locks block delete operations for protected resources https://dotnet.territoriali.olinfo.it/azure/storage/common/lock-account-resource

Please have a look into below possible ways to delete the unneeded file share:

You must stop backup for that specific file share first. Because as long as a file share is protected by Azure Backup, Azure Backup intentionally prevents its deletion via the AzureBackupProtectionLock.

1. Go to Recovery Services Vault / Backup Center
2. Locate the Azure File Share backup item
3. Select Stop backup
   • Choose Retain backup data or Delete backup data as per requirement
   1. After protection is stopped, delete the Azure File Share from the storage account

This does not impact other protected file shares and does not break existing backups.

About removing the AzureBackupProtectionLock:

• The lock exists only to protect backed‑up resources
• The lock can be removed only after backups are stopped
• Removing the lock without stopping backups is not recommended

Removing or re‑applying the lock will not affect existing backups as long as:

• Backup is not stopped for production file shares
• Backup data is not deleted

Re‑applying the lock does not affect:

• Existing file shares
• Existing recovery points
• Ongoing backup schedules

The lock is a safety control, not the backup mechanism itself.

• AzureBackupProtectionLock is expected and by design
• Individual Azure File Shares cannot be deleted while protected
• Stop backup for the specific share, then delete it
• Other file shares and backups remain unaffected

To delete the new test file share, you must temporarily remove the AzureBackupProtectionLock from the storage account, delete the file share, and then re‑add the lock. Removing or re‑adding the lock does not affect existing Azure File Share backups as long as backup protection is not stopped and backup data is not deleted. Changing the lock type to read‑only does not allow deletion and is not a valid workaround.

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out, we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thanks,

Suchitra.

Azure Backup applies a delete lock (AzureBackupProtectionLock) on the storage account to prevent accidental deletion of the account and any file shares in it. Because of this lock, deleting the test file share directly is blocked.

To delete the unneeded file share, use one of these approaches:

1. Remove or change the storage account lock
   • Go to the storage account in the Azure portal.
   • Open Locks.
   • Either remove the AzureBackupProtectionLock or change it from a delete lock to a read lock (if currently a modify/delete lock), depending on what is configured.
   • After the delete restriction is removed, delete the file share (for example, via File shares → select share → Delete share, or using Remove-AzRmStorageShare / az storage share-rm delete).
   • Be aware that removing or loosening the lock temporarily exposes the storage account and all file shares to possible accidental deletion.
2. Remove locks/leases created by value-added services
   • Azure Backup and other services may also place share leases or additional locks on specific file shares or snapshots.
   • Follow the guidance in the Azure Files troubleshooting article to remove resource locks and leases that block modification or deletion of the share. This may involve running the provided PowerShell script that removes all resource locks and leases on the storage account and its file shares.
   • After locks/leases are removed, delete the test file share.

Note: Removing locks or leases that Azure Backup uses can affect backup and restore operations and may allow deletion of protected shares or snapshots. Review backup requirements before permanently changing locks.

References:

• Troubleshoot Azure Files connectivity and access issues (SMB)
• Frequently asked questions about backing up Azure Files
• How to modify an Azure file share