Hey @GeertS , I did some digging and here is what I found.

Likely cause

The workspace is running in a Unity Catalog–only state, which hides or locks the “Disable legacy access” toggle. This is typically driven by an account-level policy applied to new workspaces.

In that mode, direct Hive metastore access is disabled by design, and the workspace-level control may not appear at all. That’s why you can’t find it under Workspace Admin → Security. The behavior aligns with the symptoms and screenshot description in the post.

Why this happens

• The “Disable legacy access” control normally appears under Workspace admin → Security and allows admins to disable direct access to the legacy Hive metastore.

• Databricks introduced an account-level policy called Disable legacy features that applies to newly created workspaces. When enabled at the account level, new workspaces default to legacy access being disabled. The workspace-level setting may be hidden or locked to enforce Unity Catalog–only mode.

• In UC-only mode, the goal is to prevent bypassing Unity Catalog governance and block direct access to tables registered in the Hive metastore.

If you need to query legacy Hive tables, the recommended approach is to use Hive metastore federation under Unity Catalog rather than re-enabling legacy access.

What to check next

• In the Account Console, verify whether Disable legacy features is enabled. If it is, that explains why the workspace-level “Disable legacy access” toggle is missing and why Hive metastore access cannot be re-enabled in newly provisioned workspaces. Only an account admin can change this setting.

• If you must work with existing Hive metastore tables, consider federating them into Unity Catalog instead of attempting to re-enable legacy access. This allows you to query those tables under UC governance controls.

Practical recommendations

• If short-term testing truly requires direct Hive metastore access, use or create a workspace where the account-level policy is not enforcing UC-only mode. Otherwise, the toggle will remain hidden or locked.

• Prefer the long-term path: keep UC-only mode enabled and use Hive metastore federation to access legacy tables through Unity Catalog.

The strategic direction is clear: Unity Catalog is the control plane. Federation is the bridge. Re-enabling legacy access is a temporary workaround, not the target state.

Cheers, Louis.

@Louis_Frolio 

Thanks for the information but when I go to the account console I cannot even find the "Disable legacy features" option. I can only see the options shown in the screenshot below:

Any idea why it is missing,

Geert

Did a bit more digging:

A few quick clarifications on when you won’t see this setting and why.

First, make sure you’re in the right place. If you’re in a workspace, you won’t see it. This is an account-level setting and lives in Account Console → Settings → Feature enablement. It does not appear in a workspace’s admin settings.

Second, check your role. You must be an account admin to view or edit anything under Feature enablement. If you’re not an account admin, you simply won’t see it.

Third, consider when the account was created. If the Databricks account was created after December 18, 2025, legacy features are disabled by default. In that case, the toggle may be locked or not visible at all because the account-level behavior is already enforcing it.

Fourth, understand the scope. The account-level toggle applies only to new workspaces. If you’re trying to affect an existing workspace, you need to use the workspace-level controls such as Disable legacy access (Hive metastore) and Disable DBFS root and mounts.

Hope that clears it up.

Hi Louis,

Thanks for the explanation. I do know that Unity Catalog is the way to go forward in the future. I just wanted to give an internal training to some new employees and explain them the difference between the old(hive) and the new (UC) of working. 

Last week I did create a new Azure Tenant and a new Databricks account and to my surprise I did not see the legacy hive megastore anymore. If I understand point three in your comment correctly, it means that if the Databricks account is created after December 18, you do not even have the option anymore to reenable the legacy hive metastore ?

Is this new behaviour documented somewhere? I tried searching for I but could not find anything?