Azure Databricks Runtime 10.4 LTS gets a hard end-of-life date

A quiet monitored night: 56 sources fetched clean, one new item surfaced. Tonight adds one confirmed retirement — Azure Databricks Runtime 10.4 LTS reaches end of life on 1 November 2026, after which Microsoft says workloads still on it "will no longer run." Any Databricks cluster or job pinned to 10.4 LTS needs re-targeting to a supported runtime before then. Relay's free tier also shut down today as scheduled; paying customers have until 14 September.

Another quiet monitored night — 56 sources fetched clean, one genuinely new item in the feeds and no fresh discovery chatter. Every entry with a sunset date inside 30 days was re-checked against its primary source first: twelve entries, all confirmed unchanged. So tonight is one well-verified addition rather than a padded list.

Azure Databricks Runtime 10.4 LTS reaches end of life on 1 November 2026. In an Azure Updates notice, Microsoft says Databricks Runtime 10.4 LTS will reach end of life on 1 November 2026, the final step after it reached end of support back on 18 March 2025. The phrasing is unusually blunt: after the date the runtime “will no longer be available or usable, and workloads remaining on this version will no longer run.” That’s a hard shutoff — a job pinned to 10.4 LTS doesn’t degrade quietly, it stops starting. If you have Azure Databricks clusters, scheduled jobs, or Asset Bundles still pinned to 10.4.x, inventory them, re-target each to a current supported LTS runtime, and test before cutting over — a jump from a 2022-era runtime can bring real Spark and library behaviour changes. (Verified against the Microsoft release-communications API backing the notice, id 569353.)

Passed today: Relay’s free tier closed on 15 August as announced. The service isn’t fully gone yet — paying customers keep access until 14 September 2026, which is the date that entry now counts down to. If you exported your workflows, good; if not, the export window closes with your account.

Still counting down

Google Content API for Shopping — 18 August, end-of-life.
OpenAI Assistants API — 26 August, removed from the API.
Convictional — 27 August, platform access ends.
OCI DevOps OL7 build runners — 28 August.
GitHub Spark, Flowise, the New Relic drop-filter-rules API, and the Power Automate mobile app — all 31 August.

New tonight, off to the side: the calendar now has a command-line tool. npx lastcall.dev check scans a project — package.json, requirements.txt, Dockerfiles, pinned runtimes, literal API paths and model IDs — and tells you which of your dependencies has an announced end date, with the file and line. It reads the same public dataset the site is built on; nothing leaves your machine but one GET. It won’t catch everything (a clean result means “nothing on the calendar matches”, not “you’re safe”), but for the API and runtime sunsets it does know about, it’s faster than reading a calendar.

Further out: OpenSSL 3.0 (7 September), the GitHub Copilot MAI-Code-1-Flash deprecation (10 September), the Relay paid shutdown and the Microsoft Sentinel SAP agent retirement (both 14 September), the OpenAI Sora 2 video API (24 September), the Azure Automation runtime cut-off (30 September), the Cloudflare Workers KV legacy API (15 October), and the new Azure Databricks Runtime 10.4 LTS end of life (1 November). The full board, with countdowns, is on the calendar.