Skip to content

Commit fa5f889

Browse files
Merge pull request #303193 from VincentLiu777/main
Add in a new section.
2 parents fdb0835 + fd83f44 commit fa5f889

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

articles/storage/files/files-data-protection-overview.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to protect your data in Azure Files. Understand the conce
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: overview
7-
ms.date: 08/04/2024
7+
ms.date: 07/23/2025
88
ms.author: kendownie
99
# Customer intent: "As a systems administrator, I want to implement data protection for Azure file shares, so that I can ensure recovery from accidental loss, protect against ransomware, and maintain business continuity."
1010
---
@@ -115,6 +115,16 @@ Storage account locks enable admins to lock the storage account to prevent users
115115

116116
For more information, see [Apply an Azure Resource Manager lock to a storage account](../common/lock-account-resource.md).
117117

118+
### Storage account recovery
119+
120+
You can recover an accidentally deleted storage account if the following criteria are met:
121+
- The storage account was deleted within the past 14 days.
122+
- The storage account was created with the Azure Resource Manager deployment model.
123+
- A new storage account with the same name hasn't been created since the original account was deleted.
124+
- The user who is recovering the storage account must be assigned an Azure RBAC role that provides the Microsoft.Storage/storageAccounts/write permission.
125+
126+
Storage account recovery is a feature and can't be disabled. For more information and step-by-step instructions, see [Recover a deleted storage account](../common/storage-account-recover.md).
127+
118128
### Soft delete
119129

120130
Soft delete works on a file share level to protect Azure file shares against accidental deletion. If a share with soft delete enabled is deleted, it moves to a soft deleted state internally and can be retrieved until the retention period expires. Azure file shares are still billed on the used capacity when they're soft deleted.

0 commit comments

Comments
 (0)