Skip to content
This repository has been 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

Open
cv-gh opened this issue Jan 18, 2024 · 0 comments

Comments

@cv-gh
Copy link

cv-gh commented Jan 18, 2024

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/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant