Hi @Brian Dietrich
Thank you for posting your query!
The issue arises because when you mount Azure Data Lake Storage (ADLS) containers in Databricks using a Service Principal (SP)
, all users inherit the permissions of that Service Principal for the mounted storage. In your case, the Service Principal has Storage Blob Data Reader
permissions on the storage account in Resource Group 2 (RG2)
.
However, Databricks mounts do not enforce read-only access; once mounted, users can perform both read and write operations, regardless of the Service Principal's permissions.
To restrict access to RG2 as read-only,consider below options:
Instead of mounting the storage, use abfss://
paths instead of mounts to enforce Azure RBAC permissions, ensuring users have only their assigned access.
Unity Catalog
with external locations to grant read/write
access for RG1 and read-only
access for RG2, avoiding mount-based access issues. Unity Catalog is the best approach.
Configure storage-level ACLs
to enforce read-only access, preventing unauthorized modifications even if the storage is mounted.
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.