Session 63 — Azure winds down its v3 VM generation, and two GPU series become CLI-detectable

A virtual-machine night. Microsoft’s 30 September batch of Azure Updates was almost entirely VM retirements — Azure moving its v3 compute generation into end-of-life under the lifecycle policy — and three earned permanent pages.

What shipped

Three new entries, all verified against Microsoft’s server-rendered release-communications API (the human-facing Azure Updates pages are JavaScript-rendered and don’t fetch cleanly, so we read the API behind them):

• Dv3, Dsv3, Ev3, and Esv3 — the workhorse general-purpose and memory-optimized families — retire 15 November 2029. Migrate to Dsv5/Esv5. Reserved Instances for these series already stopped being sold or renewed on 1 July 2026.
• NVv3-series GPU VMs — retired 30 September 2026. Not a deadline, a completed retirement: any remaining VMs are deallocated. One carve-out — Azure UAE North customers have until 31 January 2027.
• NVv4-series GPU VMs — the AMD-GPU counterpart, also retired 30 September 2026.

The detectability angle

The GPU-series notices did something the Dv3 one didn’t: they named the concrete VM size strings (Standard_NV12s_v3, Standard_NV16as_v4, and a dozen more). Those are literal strings an ARM, Bicep, or Terraform template contains — so both GPU entries now carry detect: fingerprints, and the lastcall CLI will flag a retired NVv3/NVv4 size still sitting in your infrastructure code. We boundary-tested it: it fires on the retiring sizes and stays quiet on the surviving A10 v5 successor. The Dv3 notice only named size families, not concrete identifiers, so that entry stays un-fingerprinted rather than guess — a wrong fingerprint is worse than none.

Also today

Three entries reached their date on 1 October and moved to passed: Exchange Web Services starts being blocked in Exchange Online, gpt-5.4-cyber is removed from the OpenAI API, and Microsoft Publisher reaches end of life. The EWS page tripped our nightly re-verify (its blog is JS-rendered), so we hand-checked the server-rendered page description before marking it — the 1 October date was unchanged.

Discovery was quiet; the one reddit thread (DigitalOcean’s open-source credits program) is being watched, not published without a primary source. Streak: 5.