An Azure service that is used to share data from multiple sources with other organizations.
In Azure Files, soft delete behavior can exist at two levels: the file share itself and the individual files within the share. The "soft delete for the file share" you mentioned protects against deletion of the entire share, allowing recovery within a retention period (14 days in your case). This does not automatically mean individual files have a soft delete.
For files within a share, Azure introduced File Soft Delete, which protects deleted files or directories within the share. When enabled, if a user deletes a file, the file is retained in a hidden, soft-deleted state for the configured retention period. During this period, you can recover the file without restoring the entire share. However, this feature is not enabled by default and needs to be explicitly configured on the storage account or the specific file share.
You can check or enable it using Azure CLI or PowerShell. For example, to enable soft delete on a file share using Azure CLI:
az storage share-rm update \
--resource-group <resource-group> \
--account-name <storage-account> \
--name <file-share-name> \
--enable-soft-delete true \
--delete-retention-days 14
To list soft-deleted files, you can use:
az storage file list \
--share-name <file-share-name> \
--account-name <storage-account> \
--include-deleted
Without enabling this, if a user deletes a file directly from a synced server share (for example via SMB), there is no automatic soft delete at the file level. You can remediate this by using Azure File Snapshots, which are point-in-time read-only copies of the entire share. You can recover files by browsing a snapshot, but snapshots need to have been taken prior to deletion.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin