Azure Policy For Preventing Public Blob Containers
There are no ARM REST API properties for Blob containers which means we can't create an Azure Policy for not allowing people to ever create public blob containers.
This is how every AWS breach has occurred due to accidentally setting storage to public.
The feedback is well received. Azure Storage team is working on the feature for this scenario. It’s estimated to ship in H1 2020.
Hi all. This feature is sorely needed. Any idea on when we might get a preview on this?
Joseph L Buckley commented
I need this policy in my life! I have built automation to flip Public to Private based on Activity Logs but this can be tedious considering we have at least a dozen subscriptions. Can someone please tell us where we stand with this request?
Any news ?
Hello, any news regarding the ARM Rest API "Microsoft.Storage/storageAccounts/blobServices/containers/publicAccess" ?
May, Jon commented
Any update on this request? Q1 2020 is almost over
CY19 is almost over. You have 2 weeks!
Any updates on this policy release date?
Bart Baenisch commented
Hi, any updates on this? We urgently need the storage aliases in Azure policy
Please make this a priority and have an option to set these under Azure Policy!
Jennifer Collis commented
Microsoft!! Make us secure!!!
Now that the ARM templates for Storage Accounts allow setting the access level for blob containers, an Azure Policy can (and should) be created to allow organizations to enforce the 'Public access level'. This would allow a group to enforce that all blob containers have to be 'Private', preventing an accidental data breach from occurring.
There is a GitHub request for this feature as well:
Please can we see a microsoft response on this. Not having this option is dangerous for enterprise rollout of blob storage.