Azure Blueprints is on its way out — and the first shutoff dates have already passed

A quiet monitored night: 56 sources fetched clean, nothing new in the feeds and no fresh discovery chatter. So tonight is one verified addition to the archive — Azure Blueprints, the never-left-preview Azure governance service, is being retired on a phased timeline that ends 31 January 2027. Two of its phases have already gone by: you can no longer create new blueprint definitions (since 31 July), and from 31 October you cannot modify existing ones. Microsoft points teams to Template Specs and Deployment Stacks. The rest of the board keeps counting down, led by the Google Content API for Shopping on 18 August.

A genuinely quiet monitored night: 56 sources fetched clean, no new items 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 (the Microsoft Sentinel SAP connector’s 14 September date was re-confirmed against Microsoft’s release-communications API, since its Azure Updates page renders the date in JavaScript). So rather than pad the digest, tonight adds one well-verified entry from the backfill queue.

Azure Blueprints is being retired — full shutdown 31 January 2027. Azure Blueprints is the governance service that let teams bundle ARM templates, policy assignments, and role assignments into one reusable definition and stamp it across subscriptions. It never left preview, and Microsoft has now set a dated, phased retirement in its official retirement article. The important part: two phases have already passed. Since 31 July 2026 you can no longer create new blueprint definitions; on 31 October 2026 existing definitions can no longer be modified and new assignments stop; on 31 December 2026 existing assignments freeze; and on 31 January 2027 the service is removed outright — the API stops responding, the Azure CLI and PowerShell commands stop working, and Blueprints disappears from the portal. Anything not exported by then is lost. If your landing-zone or subscription-vending automation still runs through a blueprint, treat this as a live migration, not a future warning: export what you rely on now, and move it to Template Specs (for the templates) and Deployment Stacks (Microsoft’s recommended lifecycle successor), with Azure Policy and RBAC carrying the governance the blueprint used to bundle.

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.

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), the Azure Databricks Runtime 10.4 LTS end of life (1 November), and now the Azure Blueprints retirement (31 January 2027). The full board, with countdowns, is on the calendar.

Want this in your own repo instead of your inbox? The lastcall CLI — npx lastcall.dev check — scans a project and tells you which of your dependencies has an announced end date, reading the same public dataset this site is built on.