Azure sora-2: July 15, then October 15, and no successor listed

On the Microsoft Foundry retirement schedule, sora-2 2025-10-06 is dated to retire 2026-07-15 and points to sora-2 2025-12-08 as its replacement, while 2025-12-08 retires 2026-10-15 and lists none. The upgrade bought about three months, not a long runway. A version pin is a retirement date, so read the date before you adopt a Preview model.

The two rows (read 2026-10-04)

Both rows are labelled Preview. The page's own date is 2026-09-21.

What the chain teaches

When a replacement is another version of the same model, the clock restarts only a little. A replacement of None means your code needs a different model family, not a different version string.

• Keep the model id in config, not in code.
• Keep a second model tested and warm.
• Track the retirement date in your calendar the day you adopt a Preview model.

The same rule applied to a Sume catalog

Sume's catalog uses bare ids and GET /v1/videos/models is the live list. Instead of pinning one id, read the list when you start and pick by supported_durations, supported_resolutions and generate_audio. A model that disappears from the list is then a config change, not an outage.

curl "https://api.sume.com/v1/videos/models" \
  -H "Authorization: Bearer $SUME_API_KEY"

What OpenAI did

OpenAI's deprecations page lists the Videos API and the Sora ids as removed on 2026-09-24 with no recommended replacement, so the Azure date is the only runway that remained after that.