Hello @RajNair ,
Thanks for the question and using MS Q&A platform.
Azure Storage supports optional anonymous public read access for containers and blobs. By default, anonymous access to your data is never permitted. Unless you explicitly enable anonymous access, all requests to a container and its blobs must be authorized. When you configure a container's public access level setting to permit anonymous access, clients can read data in that container without authorizing the request.
The following table summarizes how both settings together affect public access for a container.
Based on the requirement - you can create two containers named Dept1 with private access and Dept2 with public access. On the private container you can use the RBAC access control to grant the permissions as per your need.
Data Lake Storage Gen2 supports the following authorization mechanisms:
- Shared Key authorization
- Shared access signature (SAS) authorization
- Role-based access control (Azure RBAC)
- Access control lists (ACL)
For more details, refer to Configure anonymous public read access for containers and blobs and Access control model in Azure Data Lake Storage Gen2
Hope this will help. Please let us know if any further queries.
------------------------------
- Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
- Want a reminder to come back and check responses? Here is how to subscribe to a notification
- If you are interested in joining the VM program and help shape the future of Q&A: Here is jhow you can be part of Q&A Volunteer Moderators