Skip to content
This repository was archived by the owner on Aug 1, 2024. It is now read-only.
This repository was archived by the owner on Aug 1, 2024. It is now read-only.

Functionality impact of Azure Classic Resource provider retirement on WindowsAzure.Storage 5.0.2 #1095

@cv-gh

Description

@cv-gh

Which service(blob, file, queue, table) does this issue concern?

Blob

Which version of the SDK was used?

NuGet Gallery | WindowsAzure.Storage 5.0.2

Which platform are you using? (ex: .NET Core 2.1)

.Net Framework 4x

What problem was encountered?

None

How can we reproduce the problem in the simplest way?

N/A

Have you found a mitigation/solution?

N/A

Question is if Azure Classic Resource provider retires by 31-Aug'24 and the relevant APIs are removed, will it have impact on functional aspect of the library. WindowsAzure.Storage 5.0.2
Will library continue to function as it is today after the classic resource provider retirement?

See the article.
https://azure.microsoft.com/en-us/updates/azure-classic-resource-providers-will-be-retired-on-31-august-2024/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions