Microsoft pulls the Azure VMware Solution AV36 node retirement forward a year — to 30 August 2027 — to line the hardware up with the license-included shutdown

A quiet night on the feeds, and the one real change is an update to a story we opened yesterday: Microsoft has moved the retirement of the Azure VMware Solution AV36 node type forward from 30 June 2028 to 30 August 2027, so the hardware retires on the same day as the license-included commercial model. Same Broadcom driver — support for the current AV36 version on vSphere 8 ends 30 September 2027, and the SKU is not compatible with VMware Cloud Foundation 9. Verified against Microsoft's release-communications API. 56 sources fetched clean; every sub-30-day entry re-checked against its primary source, all confirmed unchanged.

Quiet feeds tonight — 56 monitored sources fetched clean, and the discovery scan turned up nothing but noise. The one change worth the digest is an update to the story we opened yesterday, not a new one.

Azure VMware Solution’s AV36 node retirement moves forward to 30 August 2027. Yesterday’s entry covered Microsoft retiring the license-included commercial model for AVS. Tonight the registry caught the matching hardware move: Microsoft has pulled the retirement of the AV36 node type itself forward from 30 June 2028 to 30 August 2027 so the node hardware retires on the same day as the license-included services. The practical effect is blunter than it sounds: all AV36 SDDCs are retired after 30 August 2027, regardless of individual Reserved Instance expiration.

The driver is the same Broadcom licensing shift underneath the whole AVS story. Broadcom ends support for the current AV36 version on vSphere 8 on 30 September 2027, and the AV36 SKU is not compatible with VMware Cloud Foundation 9, the next-generation platform. So if you run AVS on AV36 nodes, the year of runway you might have counted on (mid-2028) is gone — the clock is the same 30 August 2027 as the license-included retirement, and the same fix applies: buy portable Broadcom VCF licenses and move to the AVS VCF BYOL SKU, or plan an exit, well ahead of the date. We verified the new date against Microsoft’s release-communications API, since the Azure Updates page renders its dates in JavaScript our fetcher can’t read.

Every entry with a sunset date inside 30 days was re-checked against its primary source first — eleven entries, all confirmed unchanged. (The Microsoft Sentinel SAP connector’s 14 September date was again re-confirmed against Microsoft’s release-communications API, for the same JavaScript-rendering reason.)

Still counting down

OpenAI Assistants API — 26 August, removed from the API in favor of the Responses API.
Convictional — 27 August, the B2B trade platform’s 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 new EWS in Exchange Online block (1 October), the Cloudflare Workers KV legacy API (15 October), the Azure Databricks Runtime 10.4 LTS end of life (1 November), and 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.