https://community.databricks.com/t5/community-articles/unity-catalog-only-workspace-for-new-azure-databricks/m-p/154609#M1150 <P><STRONG>Big shift coming for Azure Databricks users</STRONG></P><P>Starting<SPAN>&nbsp;</SPAN><STRONG>30 September 2026</STRONG>, all new Azure Databricks workspaces will be Unity Catalog only.</P><P>- No DBFS root.<BR />- No Hive Metastore.<BR />- No legacy runtimes below 13.3 LTS.<BR />- No “old way” of doing things.</P><P>Disabling DBFS root and DBFS mounts does not disable the dbfs: URI. The following continue to work as expected:</P><P>- Volumes remain accessible via the dbfs:/Volumes prefix, as well as the POSIX-style /Volumes path.</P><P>- System paths: dbfs:/databricks-datasets/, and other read-only data accessible via Databricks system paths, such as the MLflow resource paths, remain accessible.</P><P>- Internal&nbsp;workspace system data: This includes content generated automatically by Databricks, such as notebook revisions, job run details, command results, and Spark logs.</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="szymon_dybczak_0-1776238695305.png" style="width: 400px;"><img src="https://community.databricks.com/t5/image/serverpage/image-id/26080i4B6DEDE8C74AE946/image-size/medium?v=v2&amp;px=400" role="button" title="szymon_dybczak_0-1776238695305.png" alt="szymon_dybczak_0-1776238695305.png" /></span></P><P>&nbsp;</P><P>&nbsp;</P> Wed, 15 Apr 2026 07:38:25 GMT szymon_dybczak 2026-04-15T07:38:25Z https://community.databricks.com/t5/community-articles/unity-catalog-only-workspace-for-new-azure-databricks/m-p/154609#M1150 <P><STRONG>Big shift coming for Azure Databricks users</STRONG></P><P>Starting<SPAN>&nbsp;</SPAN><STRONG>30 September 2026</STRONG>, all new Azure Databricks workspaces will be Unity Catalog only.</P><P>- No DBFS root.<BR />- No Hive Metastore.<BR />- No legacy runtimes below 13.3 LTS.<BR />- No “old way” of doing things.</P><P>Disabling DBFS root and DBFS mounts does not disable the dbfs: URI. The following continue to work as expected:</P><P>- Volumes remain accessible via the dbfs:/Volumes prefix, as well as the POSIX-style /Volumes path.</P><P>- System paths: dbfs:/databricks-datasets/, and other read-only data accessible via Databricks system paths, such as the MLflow resource paths, remain accessible.</P><P>- Internal&nbsp;workspace system data: This includes content generated automatically by Databricks, such as notebook revisions, job run details, command results, and Spark logs.</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="szymon_dybczak_0-1776238695305.png" style="width: 400px;"><img src="https://community.databricks.com/t5/image/serverpage/image-id/26080i4B6DEDE8C74AE946/image-size/medium?v=v2&amp;px=400" role="button" title="szymon_dybczak_0-1776238695305.png" alt="szymon_dybczak_0-1776238695305.png" /></span></P><P>&nbsp;</P><P>&nbsp;</P> Wed, 15 Apr 2026 07:38:25 GMT https://community.databricks.com/t5/community-articles/unity-catalog-only-workspace-for-new-azure-databricks/m-p/154609#M1150 szymon_dybczak 2026-04-15T07:38:25Z