On the radar·Experiments·since November 2026 Beta

MLflow

In Beta, the MLflow UI can show traces stored in Unity Catalog without you selecting a SQL warehouse.

What Beta promises

Open to most customers but not for production: support runs through engineering, and the shape of it can still move. On by default on Premium, off on Enterprise.

Who can use itMost customers
Production useNo
SupportEngineering only
On by defaultPremium yes, Enterprise no

The definitions are Databricks' own, on its release types page. The label on this page is the one the feature's documentation states, last checked on 1 Nov 2026.

Where to read more

It is part of something we wrote up: MLflow Tracing for GenAI applications — MLflow Tracing records each GenAI request as a tree of spans carrying inputs, outputs, latency and token counts, stored in an MLflow experiment or in Unity Catalog.

The Databricks documentation for MLflow

In the news

Newsletter

Hear when MLflow changes label

We re-read the documentation behind every preview and tell you when a label moves, or when a feature quietly disappears.

Choose what you get5 of 43
Your stack · Platform & governance

Tick what you run, and untick “Everything worth knowing” to get only that.

Data engineering · Lakeflow
Data warehousing & BI
AI & ML
Your learning paths

Each one is a section of the letter, and you only get the ones you tick. Every email carries a link back to this list, so you can change it later without an account.

Double opt-in: we send one email to check the address is yours. Nothing else until you confirm.