Azure Maps Render v1 API retires 17 September, and PostgreSQL 14 gets its end-of-life date (12 November 2026)

The monitored feeds were quiet tonight — no new or changed items across 56 sources — so both of tonight’s additions come from research rather than the wire: one imminent API retirement two weeks out, and one runtime end-of-life date worth pinning to the calendar early. No corrections are outstanding; the three re-verification flags this evening were again the Microsoft pages that render their dates in JavaScript (Sentinel SAP, Azure Automation runtimes, Exchange Web Services), each re-confirmed correct by hand against Microsoft’s own APIs and page metadata.

New: Azure Maps Render v1 API retires — 17 September 2026

Two weeks out and easy to miss: Microsoft is retiring the Azure Maps Render v1 REST API on 17 September 2026. The official Render v1 reference carries the banner — the service “is now deprecated and will be retired on 9/17/26,” and all calls must move to the latest version by that date.

This is the API that renders Azure Maps data into images on the server: static maps, map tiles, and imagery under the rest-maps-1.0 version. It’s what puts a map into a PDF report or an email, or behind a backend tile cache — anything that draws a map without a browser. After the date, v1 calls don’t degrade; the imagery just stops. There’s a second date in the same week: Microsoft automatically upgrades any remaining Azure Maps Gen1 accounts to Gen2 on 15 September 2026, so teams on older accounts face a pricing-tier migration and an API retirement almost together. The fix is to move to the Render v2 API — update the API version, adapt to the v2 request/response shapes, and test before cutting over.

New: PostgreSQL 14 reaches end of life — 12 November 2026

Backfilling a date every database team should have on its calendar: the PostgreSQL project’s official versioning policy gives each major version five years, and its table lists PostgreSQL 14 (current minor 14.24) with a final release on 12 November 2026. After that, the 14.x line gets no further minor releases — no bug fixes and no security patches. A 14 server keeps running; what changes is that the next vulnerability found in it never gets fixed on 14.

The exposure is largest where the database is internet-reachable or holds regulated data, and it reaches managed PostgreSQL too — AWS RDS, Azure Database for PostgreSQL, and Google Cloud SQL each set their own 14 retirement dates that generally track the community EOL, usually with a forced upgrade or paid extended support around the same window. The upgrade target is any supported major: 15 (2027), 16 (2028), 17 (2029), or 18 (2030) — jumping to 17 or 18 buys the longest runway. This entry is detectable: the lastcall CLI matches the postgres:14 container image tag (never a supported successor), so a cluster still built FROM postgres:14 surfaces as a warning instead of a November surprise.

On the board

• 4 September — one day out: we re-check Google’s widely-reported removal of Google Assistant on mobile again tomorrow. As of tonight there is still no first-party dated page — the working blog post says only “later this year” — so the entry stays without a countdown, per our no-inferred-dates rule. The moment Google publishes a date, we record it and start the clock.
• 7 September — four days out: OpenSSL 3.0 reaches end-of-life.

Further out: the GitHub Copilot MAI-Code-1-Flash deprecation (10 September), the Relay app and Microsoft Sentinel SAP connector agent retirements (14 September), OpenAI’s Sora 2 video API (24 September), Cloudflare’s Registrar API (27 September), then a cluster on 30 September and 1 October, the .NET 8 and 9 end of support (10 November), and further Cloudflare end-of-life dates through November and December. The full board with live countdowns is on the calendar.