Files deleted after update

Luis Alberto Garrido 0 Reputation points
2026-10-17T15:23:02.2666667+00:00

I have an Azure File Storage account and yesterday saturday october 16, 2026, after MS upgrade from GPv1 to GPv2, we have a massive production data loss. I need those files back. How can I recover those files?

Azure Storage
Azure Storage

Globally unique resources that provide access to data management services and serve as the parent namespace for the services.

0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-17T15:23:18.74+00:00

    Recovery depends on what was deleted and what protection was enabled.

    1. If the storage account itself was deleted The account can be recovered only if all of these are true:
      • it was deleted within the past 14 days
      • it used the Azure Resource Manager deployment model
      • no new storage account with the same name was created
      • the recovering user has an Azure RBAC role with Microsoft.Storage/storageAccounts/write
      Also verify that:
      • the original resource group still exists; if it was deleted, it must be recreated first
      • if the account used customer-managed keys and the key vault was deleted, restore the key vault first
      In Azure portal, there are two supported recovery paths:
      • From the storage accounts list, select Restore, choose the subscription, select the deleted account from the list, and select Restore.
      • Or create a support request in Help + support with:
        • Issue type: Technical
        • Service: Storage Account Management
        • Problem type: Deletion and Recovery
        • Problem subtype: Recover deleted storage account
      Important: storage account recovery is a best-effort attempt, not guaranteed. Linked private endpoints are deleted with the account and are not automatically recreated after recovery.
    2. If the file share was deleted If soft delete was enabled for Azure file shares, the deleted share can be undeleted during the retention period. Soft-deleted shares remain recoverable until that retention expires. If the share is in the soft-deleted state and Azure Backup is being used, the share must be undeleted first before restore. If the file share was permanently deleted, Azure Backup can't restore the contents and snapshots.
    3. If files or folders inside the share were deleted or need rollback If Azure Backup protected the Azure file share, item-level recovery can restore individual files or folders:
      • Go to Resiliency > Protected inventory > Protected items with datasource type Azure Storage (Azure Files)
      • Select the file share
      • Select File Recovery
      • Select the restore point
      • Choose Original Location or Alternate Location
      • Use Add File to select the files or folders
      • Select Restore
      For Original Location, choose whether to skip or overwrite conflicts. For Alternate Location, select the destination storage account, file share, folder name, and conflict behavior.
    4. If no soft delete or backup was enabled before the loss The available context does not provide a supported file-level recovery path for permanently deleted Azure Files data without prior protection.

    To prevent repeat loss:

    • enable soft delete for Azure file shares
    • use Azure Backup for restore points and item-level recovery
    • apply a storage account lock:
      • CannotDelete to block account deletion
      • ReadOnly to block deletion and configuration changes
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. kagiyama yutaka 5,740 Reputation points
    2026-10-18T06:56:37.8533333+00:00

    I think this needs Azure Storage support case. GPv1-to-GPv2 preserves data, so the upgrade alone doesn't explain the missing files. Check the share in Azure portal > File shares > Browse and compare with SMB. A Browse failure can also be a permissions issue.

    If the share is deleted, check Show deleted shares. If files are missing, check pre-loss snapshots and Azure Backup recovery points. An existing vaulted recovery point can restore the full share elsewhere, even if the source snapshot is gone. Avoid overwrites. Send Support the resource ID, share name, UTC timestamps and errors.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.