Urgent Data Recovery Request: Automated GPv1 Migration Data Loss

Sean Owen 0 Reputation points
2026-10-14T21:17:55.4133333+00:00

My storage account was automatically migrated from GPv1 to GPv2 by [email protected] under Service Health Advisory Tracking ID: On Request over the last 24 hours. Following the migration, critical media files have gone missing from my blob containers.

  • Soft Delete Status: Disabled (was disabled prior to migration).
  • Classic Logs ($logs): Empty/cleared post-migration.
  • Impacted Subscription: On request

Since this was a Microsoft-enforced infrastructure retirement migration, please check the backend cluster replication/migration logs to see if a snapshot or cache of the old GPv1 volume can be temporarily mounted to recover the un-migrated blobs.

Azure Blob Storage
Azure Blob Storage

An Azure service that stores unstructured data in the cloud as blobs.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. kagiyama yutaka 5,655 Reputation points
    2026-10-15T07:26:26.76+00:00

    I think GPv1 to GPv2 being an in-place upgrade matters here. It doesn't involve copying blobs to another storage account.

    The GPv1 FAQ doesn't provide a way to mount an old volume or migration cache. Ask Azure Storage support to investigate the missing blob paths and UTC upgrade window, including recovery options. 　

    Was this answer helpful?

    0 comments
  2. Rukshan edirisinghe 1,885 Reputation points
    2026-10-15T03:19:43.2633333+00:00

    Hi @Sean Owen

    I'm sorry, that's a stressful one. Only Microsoft support can look at backend migration logs, so a support case is the only route for that part. Before you open it, one thing from Microsoft's own GPv1 retirement FAQ is worth knowing: the upgrade is designed not to delete or move data, and for auto-upgrades it says data is preserved but access can be temporarily impacted. So it's worth confirming whether the blobs are really gone or just not showing up yet.

    Here's what I'd do, in this order, without changing anything in the account:

    1. Pause writes. Stop any app or job that writes to or cleans up those containers, so nothing overwrites or removes more data while you investigate.
    2. List the container directly. Use Azure Storage Explorer or az storage blob list against the container, not your app. If the files show up there, the issue is in how the app reads them, not data loss.
    3. Check the Activity log on the storage account for the migration window. Look for delete operations, and see which identity made them.
    4. Open a support case right away (Help + support > Create a support request), with the highest severity your plan allows. Describe it as data missing after the automatic GPv1 to GPv2 upgrade. Include the account name, the container names, and the approximate time the files were last seen. Share those only inside the ticket, not here.
    5. Once it's sorted, turn on blob soft delete and versioning. It won't recover past deletions, but it protects you next time.

    When you list the container with Storage Explorer, do the missing files show up there, or are they absent too?

    If this resolved your issue, please consider accepting it as the answer. If the files are missing in Storage Explorer as well, let me know and I'll be happy to keep helping.

    Reference:

    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.