You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Which service(blob, file, queue, table) does this issue concern?
BlobServices
Which version of the SDK was used?
API version: 2022-05-01
SDK: 12.12.0
Which platform are you using? (ex: .NET Core 2.1)
.NET Core 3
What problem was encountered?
We trying deploying a storage account with soft delete enabled using EV2 in ChinaNorth2. However, we encountered an error OperationNotAllowedOnKind. Upon investigation we found the below in the portal. Can you confirm if this feature is supported in ChinaNorth2. The public documentation does not mention any such information. If there is such documentation, can you provide a link to it.
How can we reproduce the problem in the simplest way?
Try to create a storage account with container soft delete in ChinaNorth2.
Have you found a mitigation/solution?
No
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which service(blob, file, queue, table) does this issue concern?
BlobServices
Which version of the SDK was used?
API version: 2022-05-01
SDK: 12.12.0
Which platform are you using? (ex: .NET Core 2.1)
.NET Core 3
What problem was encountered?
We trying deploying a storage account with soft delete enabled using EV2 in ChinaNorth2. However, we encountered an error OperationNotAllowedOnKind. Upon investigation we found the below in the portal. Can you confirm if this feature is supported in ChinaNorth2. The public documentation does not mention any such information. If there is such documentation, can you provide a link to it.
How can we reproduce the problem in the simplest way?
Try to create a storage account with container soft delete in ChinaNorth2.
Have you found a mitigation/solution?
No
The text was updated successfully, but these errors were encountered: