Azure RBAC share-level permissions for Azure file shares work only after an identity source (on-premises AD DS, Microsoft Entra Domain Services, or Microsoft Entra Kerberos) is enabled for identity-based access on the storage account. A storage account uses only one identity source for file access authentication, and it applies to all file shares in that account, so every account that holds file shares needs it enabled before a group such as Group4 can be granted a share-level role like Storage File Data SMB Share Reader on its shares. Enabling identity-based access on storage2 lets its file shares be covered as well. Enabling hierarchical namespace is unrelated to Azure Files RBAC, SAS tokens are a different authorization mechanism and do not grant Azure RBAC permissions, and merely changing an account to StorageV2 does not itself enable identity-based Azure Files authorization.
Community Discussion