Microsoft deprecated NuGet package support for the Migrated Storage Account

Question

Considering the classic storage accounts are migrated to Azure Resource Manager, will the deprecated NuGet packages

1. Microsoft.WindowsAzure.Storage
2. Microsoft.Azure.Storage

be able to call Azure Resource Manager (migrated account)?

Note: NuGet packages are used in the console and library applications to call the storage account. It uses the storage account SAS URI to consume the blob files for add/delete/update/list operations.

The below question is based on this information: https://www.nuget.org/packages/Microsoft.Azure.Storage.Blob/11.2.3?_src=template

So, my question is: Will the deprecated NuGet packages (Microsoft.WindowsAzure.Storage and Microsoft.Azure.Storage) be able to call Azure Resource Manager (migrated account) after August 31st, 2024?

Answer 1

As of August 31st, 2024, Azure will fully transition to Azure Resource Manager (ARM) for managing Azure Storage resources. The deprecated NuGet packages you mentioned—Microsoft.WindowsAzure.Storage and Microsoft.Azure.Storage—are not compatible with the new Azure Resource Manager (ARM) model.yourtexas-benefits.com

Here's a breakdown of the implications:

Deprecated Packages:

• Microsoft.WindowsAzure.Storage and Microsoft.Azure.Storage are deprecated and no longer actively maintained.
  • These packages were designed for use with the older Azure Service Management (ASM) model.
  Compatibility:

    - Since the ARM model uses different APIs and service management models, the older packages will not support the new features and requirements of ARM-managed storage accounts.
    
    
       - Specifically, operations involving SAS URIs for blobs may continue to work as long as they use the existing storage endpoints and APIs, but you won't be able to leverage new ARM-specific features or manage resources through the ARM interface.
    
       
       **Recommended Action**:
    
       
          - **Update NuGet Packages**: To ensure compatibility with the new ARM-managed storage accounts, you should migrate to the `Azure.Storage.Blobs` NuGet package. This package is designed to work with ARM-managed storage accounts and is actively maintained.
    
          
             - **Migration to New SDK**: The `Azure.Storage.Blobs` SDK provides updated functionality and aligns with the latest Azure storage capabilities.
    
             
             **Code Migration**:
    
             
                - **Updating Code**: If you migrate to the `Azure.Storage.Blobs` SDK, you will need to update your code to accommodate any changes in API methods and classes. This SDK is compatible with the latest Azure Storage services and supports modern features and performance improvements.
    ```To summarize, after August 31st, 2024, it is advisable to move away from the deprecated NuGet packages and use the new `Azure.Storage.Blobs` SDK to ensure full compatibility with ARM-managed storage accounts and to benefit from ongoing support and updates.
  

Answer 2

Please find the answer here.

MS-Q&A by Sumarigo-MSFT.

Answer 3

@Gowtham Sekar

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

Issue: Will the deprecated NuGet packages (Microsoft.WindowsAzure.Storage and Microsoft.Azure.Storage) be able to call Azure Resource Manager (migrated account) after August 31st, 2024? Will the old package with the new storage account completely break after Aug 31?

Solution: As shared by the Customer:

Referenced from: https://learn.microsoft.com/en-us/answers/questions/1861725/unsure-if-code-changes-are-needed-for-classic-stor

"If your Cloud Service is only using the older Microsoft.WindowsAzure.Storage.Blob library to upload/download files and is not dynamically creating, updating, or deleting storage accounts, then you should be able to continue using the library after the migration cut-off date of August 31st.

However, it is still recommended to update your applications to use Azure Resource Manager APIs for account management, as this will ensure that your applications are using the latest and most secure APIs for managing storage accounts.

If you do decide to update your applications to use Azure Resource Manager APIs, you can follow the guidance provided in the documentation to make the necessary changes to your code, scripts, or templates. This will involve updating your code to use the latest Azure Storage SDK, which supports both classic and ARM storage accounts.

If you choose not to update your applications to use Azure Resource Manager APIs, you should still be able to continue using the older Microsoft.WindowsAzure.Storage.Blob library to upload/download files, but you may not be able to take advantage of the latest features and security enhancements provided by Azure Storage.

Note: To simulate the behavior after the deadline, you could consider setting up a test environment to migrate your Cloud Service (extended support) and Storage Account (classic) to ARM and observe the behavior of your application using the Microsoft.WindowsAzure.Storage.Blob library. This would give you an indication of any potential issues that might arise post-migration."