Dear Databricks Customer,

Starting September 30, 2026, new workspaces created in your account(s) will use Unity Catalog exclusively. This change will simplify and enhance governance across your data landscape, with benefits including unified governance, enterprise-grade security and access to advanced platform features that are unavailable with legacy metastores. Existing workspaces and their workflows will not be impacted.

Impacted Account(s)

Account ID
08096000-3228-47fa-b2c2-8eccba032552

Starting September 30, 2026, new workspaces will be provisioned without access to:

• DBFS root (AWS | GCP) and the ability to create DBFS mounts (AWS | GCP).
• Hive Metastore (AWS | GCP).
• No-isolation clusters (AWS | GCP).
• Databricks Runtime versions (AWS | GCP) prior to 13.3 LTS.

Disabling DBFS root and DBFS mounts does not disable the dbfs: URI itself. The following continue to work as expected:

• Unity Catalog Volumes (AWS | GCP): Volumes remain accessible via the dbfs:/Volumes prefix, as well as the POSIX-style /Volumes path.
• System Paths: dbfs:/databricks-datasets/, and other read-only data accessible via Databricks system paths, such as the MLflow resource paths, remain accessible.
• Internal Workspace system data (AWS | GCP): This includes content generated automatically by Databricks, such as notebook revisions, job run details, command results, and Spark logs.

1. Adjust CI/CD scripts and internal operational procedures for any workspace creation processes that might be using DBFS root, DBFS mounts, or Hive Metastore. For detailed steps, consult our migration guide (AWS | GCP).
2. Set a metastore to auto-assign (AWS | GCP) for every region in which you deploy workspaces. Failure to do so will require a metastore to be assigned manually when a workspace is provisioned.
3. If you plan to migrate existing workflows to new workspaces created after September 30, 2026, please ensure these workflows do not rely on these legacy features or capabilities exclusive to Databricks Runtime versions prior to 13.3 LTS. For detailed steps, consult our migration guide (AWS | GCP).
4. Existing workspaces are not impacted, although we highly recommend migrating to Unity Catalog in all workspaces. You can disable DBFS root, mounts and Hive metastore using the workspace-level settings available. See:
   • Disable access to DBFS root and mounts in your existing Databricks workspace (AWS | GCP).
   • Disable access to the Hive metastore used by your Databricks workspace (AWS | GCP).

If you'd like to test the new default behavior before September 30, 2026, you can do so by enabling the Disable legacy features setting in your account console. See Disable access to legacy features in new workspaces (AWS | GCP).

If you have any questions, please reach out to your Databricks account team or contact help@databricks.com.

Thanks,
Databricks