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.
I am not able to create a storage account with public network access disable due to the police: "Storage accounts should restrict network access".
It requires to have DefaultAction = "Deny", even when it is not applicable. With public access disabled, this rule should not require the network rule, since it only becomes accessible via private link services (that can only be exposed via private endpoint).
How can we reproduce the problem in the simplest way?
Setup a private network and try to create a storage account with public network access disabled.
I am not quite sure how that translates to the API/SDK, but that's what it takes.
Have you found a mitigation/solution?
I set DefaultAction to "Deny", even though it is not applicable. The main problem here is finding the root cause effectively, since this is not an error to be expected in this setup.
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?
None in particular, but instead the storage account as a whole
Which version of the SDK was used?
This is from azurerm terraform provider, which seems to be using these:
Which platform are you using? (ex: .NET Core 2.1)
Terraform AzureRM 3.97.1
What problem was encountered?
I am not able to create a storage account with public network access disable due to the police: "Storage accounts should restrict network access".
It requires to have DefaultAction = "Deny", even when it is not applicable. With public access disabled, this rule should not require the network rule, since it only becomes accessible via private link services (that can only be exposed via private endpoint).
How can we reproduce the problem in the simplest way?
Setup a private network and try to create a storage account with public network access disabled.
I am not quite sure how that translates to the API/SDK, but that's what it takes.
Have you found a mitigation/solution?
I set DefaultAction to "Deny", even though it is not applicable. The main problem here is finding the root cause effectively, since this is not an error to be expected in this setup.
The text was updated successfully, but these errors were encountered: