<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Need to fetch Mount Point details in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156368#M54411</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/188867"&gt;@Danish11052000&lt;/a&gt;&amp;nbsp; !&lt;/P&gt;&lt;P&gt;Thank you for the question it really helped me to review my knowledge and go back and pay attention to this subject &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;&lt;P&gt;and guess what ? you are correct because&amp;nbsp;UC permissions alone will not give complete access governance for legacy DBFS mounts. For mounts, governance has to be built from DBKS mount inventory with audit logs, Azure Storage RBAC/ACLs and storage access logs.&lt;/P&gt;&lt;P&gt;So for the mount inventory you can use dbutils.fs.mounts() from each workspace because they are workspace level aliases between DBFS and cloud storage and they store the storage location, driver config and credentials needed to access the data. If you check the doc they are already deprecated so you need to think about migrating to UC external locations instead. &lt;A title="https://learn.microsoft.com/en-us/azure/databricks/dbfs/mounts" href="https://learn.microsoft.com/en-us/azure/databricks/dbfs/mounts" target="_self"&gt;https://learn.microsoft.com/en-us/azure/databricks/dbfs/mounts&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This is an example I did and it is working :&lt;/P&gt;&lt;PRE&gt;mounts = []

for m in dbutils.fs.mounts():
    mounts.append({
        "mount_point": m.mountPoint,
        "source": m.source,
        "encryption_type": getattr(m, "encryptionType", None)
    })

mount_df = spark.createDataFrame(mounts)
display(mount_df)

# here u can persist for gov
mount_df.write.mode("overwrite").saveAsTable("governance_legacy.databricks_mount_inventory")&lt;/PRE&gt;&lt;P&gt;this gives you the mapping :&lt;/P&gt;&lt;PRE&gt;/mnt/raw/customers  -&amp;gt;  abfss://raw@storageaccount.dfs.core.windows.net/customers&lt;/PRE&gt;&lt;P&gt;For ACLs, the permissions are not stored on the DBKS mount itself and they&amp;nbsp;are enforced at the underlying ADLS Gen2 layer through Azure RBAC and POSIX ACLs. Try to check this doc it explains that part :&lt;/P&gt;&lt;P&gt;&lt;A title="https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-access-control" href="https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-access-control" target="_self"&gt;https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-access-control&lt;/A&gt;&lt;/P&gt;&lt;P&gt;for a single path you can check ACL with Azure CLI:&lt;/P&gt;&lt;PRE&gt;az storage fs access show \
  --account-name &amp;lt;storage-account&amp;gt; \
  --file-system &amp;lt;container&amp;gt; \
  --path &amp;lt;directory-or-file-path&amp;gt; \
  --auth-mode login&lt;/PRE&gt;&lt;P&gt;With&amp;nbsp;az storage fs access show&amp;nbsp;you can get ACL for a directory or file and for broader auditing you typically need to crawl the mounted ADLS path and extract ACLs using Azure CLI, PS or Azure Storage SDK.&lt;/P&gt;&lt;P&gt;You can list paths with&amp;nbsp;FileSystemClient.get_paths()&amp;nbsp;and read ACL with&amp;nbsp;get_access_control()&lt;/P&gt;&lt;P&gt;You can also use audit logs to identify mount and unmount events but this is not the same as a full current permission model because DBKS audit logs include DBFS operational events such as mount and unmount&amp;nbsp;with params like mountPoint and owner.&lt;/P&gt;&lt;P&gt;For storage access auditing, personally I use Azure Storage diagnostic and Azure Blob or ADLS logs can be routed to log analytics and to your info supported categories include only&amp;nbsp;StorageRead, StorageWrite&amp;nbsp;and StorageDelete.&lt;/P&gt;</description>
    <pubDate>Thu, 07 May 2026 09:34:15 GMT</pubDate>
    <dc:creator>amirabedhiafi</dc:creator>
    <dc:date>2026-05-07T09:34:15Z</dc:date>
    <item>
      <title>Need to fetch Mount Point details</title>
      <link>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156341#M54403</link>
      <description>&lt;DIV&gt;&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I’m currently working on building a consolidated view of access permissions across our Databricks environment.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;For &lt;STRONG&gt;Unity Catalog (UC)&lt;/STRONG&gt; objects, I’m able to retrieve permission details using &lt;STRONG&gt;system tables (privileges / audit logs)&lt;/STRONG&gt;.&lt;/LI&gt;&lt;LI&gt;However, for &lt;STRONG&gt;legacy (non-UC) setups&lt;/STRONG&gt;, I understand that access is primarily managed via &lt;STRONG&gt;mount points and underlying ADLS ACLs&lt;/STRONG&gt;, which are not captured in UC system tables.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Could you please guide on the following:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;How can we fetch a complete list of &lt;STRONG&gt;mount points along with their mapping to ADLS paths&lt;/STRONG&gt;?&lt;/LI&gt;&lt;LI&gt;Is there any recommended approach to extract or audit &lt;STRONG&gt;ACL / permission details applied on these mount points (or underlying storage)?&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;Are there any existing tools, logs, or governance sources (e.g., APIs) that provide &lt;STRONG&gt;mount-level access visibility&lt;/STRONG&gt;?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;From my current understanding, UC permissions alone are not sufficient, and &lt;STRONG&gt;mount point access details are a key missing piece for complete access governance&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Any guidance, references, or best practices would be really helpful.&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 07 May 2026 04:40:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156341#M54403</guid>
      <dc:creator>Danish11052000</dc:creator>
      <dc:date>2026-05-07T04:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: Need to fetch Mount Point details</title>
      <link>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156368#M54411</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/188867"&gt;@Danish11052000&lt;/a&gt;&amp;nbsp; !&lt;/P&gt;&lt;P&gt;Thank you for the question it really helped me to review my knowledge and go back and pay attention to this subject &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;&lt;P&gt;and guess what ? you are correct because&amp;nbsp;UC permissions alone will not give complete access governance for legacy DBFS mounts. For mounts, governance has to be built from DBKS mount inventory with audit logs, Azure Storage RBAC/ACLs and storage access logs.&lt;/P&gt;&lt;P&gt;So for the mount inventory you can use dbutils.fs.mounts() from each workspace because they are workspace level aliases between DBFS and cloud storage and they store the storage location, driver config and credentials needed to access the data. If you check the doc they are already deprecated so you need to think about migrating to UC external locations instead. &lt;A title="https://learn.microsoft.com/en-us/azure/databricks/dbfs/mounts" href="https://learn.microsoft.com/en-us/azure/databricks/dbfs/mounts" target="_self"&gt;https://learn.microsoft.com/en-us/azure/databricks/dbfs/mounts&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This is an example I did and it is working :&lt;/P&gt;&lt;PRE&gt;mounts = []

for m in dbutils.fs.mounts():
    mounts.append({
        "mount_point": m.mountPoint,
        "source": m.source,
        "encryption_type": getattr(m, "encryptionType", None)
    })

mount_df = spark.createDataFrame(mounts)
display(mount_df)

# here u can persist for gov
mount_df.write.mode("overwrite").saveAsTable("governance_legacy.databricks_mount_inventory")&lt;/PRE&gt;&lt;P&gt;this gives you the mapping :&lt;/P&gt;&lt;PRE&gt;/mnt/raw/customers  -&amp;gt;  abfss://raw@storageaccount.dfs.core.windows.net/customers&lt;/PRE&gt;&lt;P&gt;For ACLs, the permissions are not stored on the DBKS mount itself and they&amp;nbsp;are enforced at the underlying ADLS Gen2 layer through Azure RBAC and POSIX ACLs. Try to check this doc it explains that part :&lt;/P&gt;&lt;P&gt;&lt;A title="https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-access-control" href="https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-access-control" target="_self"&gt;https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-access-control&lt;/A&gt;&lt;/P&gt;&lt;P&gt;for a single path you can check ACL with Azure CLI:&lt;/P&gt;&lt;PRE&gt;az storage fs access show \
  --account-name &amp;lt;storage-account&amp;gt; \
  --file-system &amp;lt;container&amp;gt; \
  --path &amp;lt;directory-or-file-path&amp;gt; \
  --auth-mode login&lt;/PRE&gt;&lt;P&gt;With&amp;nbsp;az storage fs access show&amp;nbsp;you can get ACL for a directory or file and for broader auditing you typically need to crawl the mounted ADLS path and extract ACLs using Azure CLI, PS or Azure Storage SDK.&lt;/P&gt;&lt;P&gt;You can list paths with&amp;nbsp;FileSystemClient.get_paths()&amp;nbsp;and read ACL with&amp;nbsp;get_access_control()&lt;/P&gt;&lt;P&gt;You can also use audit logs to identify mount and unmount events but this is not the same as a full current permission model because DBKS audit logs include DBFS operational events such as mount and unmount&amp;nbsp;with params like mountPoint and owner.&lt;/P&gt;&lt;P&gt;For storage access auditing, personally I use Azure Storage diagnostic and Azure Blob or ADLS logs can be routed to log analytics and to your info supported categories include only&amp;nbsp;StorageRead, StorageWrite&amp;nbsp;and StorageDelete.&lt;/P&gt;</description>
      <pubDate>Thu, 07 May 2026 09:34:15 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156368#M54411</guid>
      <dc:creator>amirabedhiafi</dc:creator>
      <dc:date>2026-05-07T09:34:15Z</dc:date>
    </item>
    <item>
      <title>Re: Need to fetch Mount Point details</title>
      <link>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156387#M54416</link>
      <description>&lt;DIV&gt;&lt;P&gt;Thanks for the explanation. Based on your example, mount points are retrieved using dbutils.fs.mount, and since mounts are being deprecated, migration to Unity Catalog is required.&lt;/P&gt;&lt;P&gt;Currently, I am already using Unity Catalog, so dbutils.mounts won't work. Is there an alternative way to retrieve these details via an API?&lt;/P&gt;&lt;P&gt;Also, since non-UC workspaces will gradually migrate to UC, how should we handle this situation in the meantime?&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 07 May 2026 13:43:36 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156387#M54416</guid>
      <dc:creator>Danish11052000</dc:creator>
      <dc:date>2026-05-07T13:43:36Z</dc:date>
    </item>
    <item>
      <title>Re: Need to fetch Mount Point details</title>
      <link>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156450#M54423</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/188867"&gt;@Danish11052000&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Not exactly. dbutils.fs.mounts() is for legacy DBFS mounts, and it can still work in some Unity Catalog-enabled workspaces if those mounts still exist and the cluster/access mode permits DBFS access. However, mounts are deprecated and are not the Unity Catalog model.&lt;/P&gt;
&lt;P&gt;In Unity Catalog, the equivalents to inspect are external locations, storage credentials, and volumes rather than mounts. So there isn’t a direct "list mounts" UC API; instead, you’d use commands/APIs such as SHOW EXTERNAL LOCATIONS, SHOW STORAGE CREDENTIALS, and SHOW VOLUMES, plus the Files API/SDK for volume file operations.&lt;/P&gt;
&lt;P&gt;During migration, support both patterns... use dbutils.fs.mounts() only for remaining legacy mounts, and use UC metadata objects for UC-governed storage.&lt;/P&gt;
&lt;P&gt;Lastly, when you mention that non-UC workspaces will gradually migrate to UC, I assume this is an activity you will be handling. I want to clarify that this process will not happen automatically, in case you had that impression.&lt;/P&gt;
&lt;P class="p1"&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;I&gt;&lt;/I&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 May 2026 12:45:10 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/need-to-fetch-mount-point-details/m-p/156450#M54423</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-05-08T12:45:10Z</dc:date>
    </item>
  </channel>
</rss>

