Classic Azure storage account migration

Cristopher Waser 20 Reputation points
2023-09-12T18:20:21.41+00:00

Quick question,

After the 31 of August 2024 (when interaction with classic storage is terminated), will we still be able to make calls using the "Microsoft.Azure.Storage.Blob" package or are we forced to use "Azure.Storage.Blobs" to interact with our blob storage (its already migrated and we are currently using "Microsoft.Azure.Storage.Blob" to make file manipulations, just need to know if we have to switch the package).

(I know that "Microsoft.Azure.Storage.Blob" is deprecated, but would like to know if calls with it will still work)

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,621 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sumarigo-MSFT 45,406 Reputation points Microsoft Employee
    2023-09-13T05:54:58.8833333+00:00

    @Cristopher Waser Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

    **On August 31, 2024, we'll retire classic Azure storage accounts and they'll no longer be accessible.
    **
    After the 31st of August 2024, when interaction with classic storage is terminated, you will not be able to use the "Microsoft.Azure.Storage.Blob" package to interact with your blob storage. You will need to switch to the "Azure.Storage.Blobs" package to continue making file manipulations.

    While the "Microsoft.Azure.Storage.Blob" package is currently still supported, it is deprecated and will not receive any new features or updates. It is recommended that you switch to the "Azure.Storage.Blobs" package as soon as possible to ensure that your application remains compatible with Azure Blob Storage.

    We announced Azure Cloud Services (classic) will be retired on 31 August 2024. Because classic storage accounts are dependent on Azure Cloud Services (classic), they'll be retired on the same date. Before that date, you'll need to migrate them to Azure Resource Manager, which provides the same capabilities as well as new features, including:

    • A management layer that simplifies deployment by enabling you to create, update, and delete resources.
    • Resource grouping, which allows you to deploy, monitor, manage, and apply access control policies to resources as a group.

    Beginning 1 August 2022, you'll no longer be able to create new classic storage account resources, however, resources created before that date will be supported through 31 August 2024.

    Required action

    To avoid service disruptions, review Azure Resource Manager pricing and migrate your classic storage accounts before 31 August 2024.

    Microsoft.Azure.Storage.Blob's homepage in NuGet: https://www.nuget.org/packages/Microsoft.Azure.Storage.Blob/
    The Suggested is Azure.Storage.Blobs.

    For more information refer to this article: https://azure.github.io/azure-sdk/releases/deprecated/index.html

    User's image

    Please let us know if you have any further queries. I’m happy to assist you further.     


    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. 2024-07-10T21:11:17.5633333+00:00

    Hello,

    My applications access to storage account file shares using Microsoft.WindowsAzure.Storage.File packages, actually I'm testing these applications with new storage account created in the Prepare phase migration and these still work, after the 31 of August 2024 I need to know if calls with this package will still work

    Thanks in advance


  2. 2024-07-10T22:31:43.45+00:00

    Hello,

    Can you tell me if the time it takes to execute the migration phases (validation, preparation, commit) depends on the size or number of files contained in the classic storage account?

    We have a classic storage account that contains 2044727 files representing 1866.15 GiB. This information is important to determine the maintenance window for users

    Thanks in advance

    0 comments No comments