What is ending
The opposite page to the preview radar. Runtimes losing support, models being retired, APIs going away, and behaviour changes with a date attached — on one countdown, nearest first.
6 inside ninety days
Inside thirty days
4This is not planning any more. If it is in production, it is this week’s work.
- in 2 days14 Sept 2026Workspace entitlement inheritance becomes mandatory Behaviour change Workspace
The enforcement date for inherited entitlements, with no opt-out left.
Check any automation that sets entitlements on system groups: that is what breaks.
- in 18 days30 Sept 2026The Supervisor API API Agents
The Beta API for supervisor agents reaches end of life and stops being available.
Move to a custom agent deployed on Databricks Apps, which is the documented path.
- in 20 days2 Oct 2026Gemini 2.5 Flash and 2.5 Pro Model Serving
Both retire on the same day, Flash from pay-per-token and Pro from provisioned throughput.
Databricks points at Gemini 3.1 Pro or 3.5 Flash. Budget time for re-evaluating, not just renaming the endpoint.
- in 27 days9 Oct 2026Claude Sonnet 4 on Foundation Model APIs Model Serving
Retired from pay-per-token serving. Requests to it will stop working.
Move to Claude Sonnet 4.6 and re-run your evaluations: a newer model is not a drop-in for prompt behaviour.
This quarter
2Time to schedule the upgrade, not to start investigating it.
- in 50 days1 Nov 2026Databricks Runtime 10.4 LTS Runtime Compute
The last announced end of life among the old long-term support releases.
Move the workloads still pinned to it. Anything this old will need testing, not just a version bump.
- in 87 days8 Dec 2026Old-format OpenSharing recipient tokens Behaviour change Discover Sharing data with OpenSharing
Tokens issued in the old format expire, at the latest, on this date.
Rotate recipient credentials before then, or the sharing partner loses access without warning.
Within the year
2Dated and certain. Put it in a plan while the plan is still cheap.
- in 142 days1 Feb 2027Databricks Runtime 14.3 LTS Runtime Compute
Long-term support ends, so no more fixes and no more support tickets against it.
Plan the jump to 16.4 LTS or later. Check the behaviour changes between them rather than assuming a clean swap.
- in 341 days19 Aug 2027Databricks Runtime 15.4 LTS Runtime Compute
Long-term support ends.
Still comfortable, but note it is the floor for several features, so upgrading unlocks as much as it costs.
Beyond a year
3Far enough away to choose deliberately: build on the long-term support version, not the one ending first.
- in 605 days9 May 2028Databricks Runtime 16.4 LTS Runtime Compute
Long-term support ends.
A reasonable target for anything being upgraded today.
- in 771 days22 Oct 2028Databricks Runtime 17.3 LTS Runtime Compute
Long-term support ends.
The safer target if the workload can take the newer behaviour.
- in 1002 days10 Jun 2029Databricks Runtime 18 LTS Runtime Compute
Long-term support ends. The longest runway currently published.
Where a new project should start.
No date, but on the way out
5Still works. Do not start anything new on it.
- no dateannounced 1 Oct 2022Trigger.Once in Structured Streaming Feature Streaming Trigger intervals in Structured Streaming
Deprecated since Databricks Runtime 11.3 LTS, and still all over older tutorials.
Use Trigger.AvailableNow, which processes in several batches instead of one and does not fall over on a large backlog.
- no dateannounced 1 Jan 2026dbx by Databricks Labs Feature Ecosystem & Tools Databricks Labs, the tools around the platform Declarative Automation Bundles and the Databricks CLI
No longer actively maintained. Its own README points elsewhere.
Deployments move to bundles. Expect to find dbx in repositories for years yet.
- no dateannounced 1 Jan 2026Hyperopt Feature Experiments
The open-source project is no longer maintained and it is gone from the machine learning runtime after 16.4 LTS.
Optuna on a single node, or Ray Tune when the search has to be distributed.
- no dateannounced 1 Jan 2026Personal access tokens Feature Workspace
Now documented as the legacy way to authenticate.
Use OAuth, and in continuous integration use workload identity federation rather than a long-lived token in a secret.
- no dateannounced 18 Aug 2026Deprecated system table columns and schemas Behaviour change Catalog System tables
Two lineage columns stopped being populated during 2026, and two schemas now hold empty tables.
Queries against them return nothing rather than failing, which is the worse failure mode. Check any dashboard built on them.
Already gone
6Here because older tutorials still recommend them, and because an incident on one of these starts with an upgrade.
- 195 days ago1 Mar 2026Databricks Runtime 12.2 LTS Runtime Compute
Support ended in March 2026.
Upgrade. There is no support path left for it.
- 120 days ago15 May 2026Llama 3.1 405B Model Serving
Retired from pay-per-token in February 2026 and from provisioned throughput in May.
The documented replacement is GPT OSS 120B.
- 59 days ago15 Jul 2026Databricks Runtime 18.0 Runtime Compute
A non-long-term-support release, supported for about six months.
Move to 18 LTS. This is the pattern for every non-LTS version, so pin to LTS unless you need something newer.
- 58 days ago16 Jul 2026GPT-5.1 Codex Max, Codex Mini and GPT-5.2 Codex Model Serving
Three OpenAI coding models retired together in July 2026.
GPT-5.5 replaces the Max and 5.2 variants, GPT-5.4 Codex Mini replaces the Mini.
- 43 days ago31 Jul 2026The legacy SQL editor Feature SQL Editor
Retired in late July 2026, and the individual opt-out went with it.
Nothing to do beyond learning where things moved in the current editor.
- 21 days ago22 Aug 2026Databricks Runtime 13.3 LTS Runtime Compute
Support ended in August 2026.
Clusters pinned here are running unsupported. Treat any incident on them as an upgrade first.
Dates come from the Databricks documentation and are re-checked by the agent. A runtime version is supported for roughly six months, and a long-term support version for three years from its general availability. Model retirements get at least three months of notice after the deprecation is announced.