@Girish Prajwal Question, if a user can read a blob from a storage account, the name of the storage account is present in the URL/properties of the blob (so, the user can still tell there is an account and access via script/programmatically).
‘Storage Blob Data Reader’ may limit the ability to list the account (: https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#storage-blob-data-reader)
You need a read permission or Reader role on the subscription to enumerate resources, including storage accounts.
Storage Blob Data Reader role grants permissions for reading blob content and metadata in the storage account.
Also, Let me explain how this roles works and the define of the RBAC, see here
If it's for Azure Files You can do an AD integration with SMB to grant access to users. Here you can learn more about it : https://azure.microsoft.com/en-us/blog/better-security-with-enhanced-access-control-experience-in-azure-files/ also if possible review the RBAC roles article What is Azure role-based access control (Azure RBAC)?
Hope this helps!
Kindly let us know if the above helps or you need further assistance on this issue.
------------------------------------------------------------------------------------------------------------
Please don’t forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.