Skip to content
Hugin

Hugin / Deadlines

The clock.

Every end date Microsoft has published, counting down.

0 upcoming3 passedSubscribe to Microsoft dates

Nothing scheduled for Microsoft: no published end date from this provider is in the future — not that nothing is coming.

Passed 3 · 0 filed · 3 not checked
  1. 21 days ago

    Microsoft · Retirement

    Azure OpenAI retires sora-2 (version 2025-12-08) — three weeks after OpenAI shut down its own Sora 2 API

    Nothing to move to. Microsoft's retirement schedule shows '—' in the Replacement column for sora-2 version 2025-12-08, and its lifecycle page says that when no replacement exists 'customers get 30 days notice before the model retires and inference returns 410 Gone.' OpenAI names no replacement on its side either.

    This date passed and nothing is filed

    The board is not claiming it happened. This desk has not checked.

    Sources and checks

    A Preview-stage 'not sooner than' date, not a committed shutdown. The schedule lists this sora-2 version as Preview, and Microsoft's lifecycle page says Preview models 'launch with a "not sooner than" retirement date (typically 90 days out), but are sometimes extended beyond that initial window, until a suitable replacement preview or GA model version is available.' The same page answers 'Can I get an exception to extend a model's retirement date?' with 'No.' — that is about a customer asking, not about Microsoft moving its own Preview date. Microsoft's schedule (page dated September 21, updated September 23), not an observation: this desk cannot test Azure deployments. The same table lists an earlier sora-2 version, 2025-10-06, with a July 15 retirement date and this version as its replacement.

    Operative page changed: Read, and something changed: 1 recorded term no longer on the page. Open the page before relying on this row.

  2. 33 days ago

    Microsoft · Retirement

    Moonshot AI's Kimi-K2.7-Code, a Preview model Azure sells, retires from Microsoft Foundry — the day after GitHub Copilot drops the same model

    Nothing to move to. Microsoft's retirement schedule shows '—' in the Replacement column for Kimi-K2.7-Code. GitHub's Copilot notice suggests Kimi K3 for the same model on October 2, but that is GitHub's recommendation for its own tool, not Microsoft's for Foundry.

    This date passed and nothing is filed

    The board is not claiming it happened. This desk has not checked.

    Sources and checks

    A Preview-stage 'not sooner than' date that Microsoft's lifecycle page says is 'sometimes extended beyond that initial window'. The Copilot removal on October 2 is a separate row; Moonshot AI's own API is not covered here.

    Operative page changed: Read, and something changed: 1 recorded term no longer on the page. Open the page before relying on this row.

  3. 35 days ago

    Microsoft · Retirement

    Microsoft retires its own image models MAI-Image-2.5, MAI-Image-2.5-Flash and MAI-Image-2.5-Pro from Foundry

    Nothing to move to. The retirement schedule shows '—' in the Replacement column for all three, although the same table lists MAI-Image-2.5 and MAI-Image-2.5-Flash as the replacements for MAI-Image-2 and MAI-Image-2e, retired August 15. Microsoft's MAI image how-to page lists the Preview models MAI-Image-2.6 and MAI-Image-2.6-Flash without calling them replacements.

    This date passed and nothing is filed

    The board is not claiming it happened. This desk has not checked.

    Sources and checks

    A Preview-stage 'not sooner than' date: all three are Preview models, and Microsoft's lifecycle page says Preview models 'launch with a "not sooner than" retirement date (typically 90 days out), but are sometimes extended beyond that initial window'. This desk cannot test Foundry deployments or see the 30-day notice the policy promises when no replacement exists.

    Operative page changed: Read, and something changed: 1 recorded term no longer on the page. Open the page before relying on this row.

Only dates a provider has published — nothing inferred, nothing from rumour. Every row is backed by a source anchor in the case files, and shows what this desk’s own re-read of the provider’s page last found.

The government board below it is a separate list with a separate rule: a duty a government body published in its own document, cited to the Federal Register document number and the sentence it rests on. Those dates are not in the calendar feed or the provider API yet.

Subscribe by calendar (when a date moves, the event moves) · Data · The case file · Corrections