AI Info Guide
AI news for everyone

Microsoft lists October 15 retirement for Azure Sora 2, without a named replacement

October 15, 2026 · Central Time

Microsoft's current Foundry model retirement schedule lists October 15, 2026 as the retirement date for sora-2 version 2025-12-08. The table identifies that version as Preview and leaves its replacement column blank. This is a documented retirement date, not a live test showing that every deployment has already stopped responding at a particular hour.

The version matters. The same table gives the earlier sora-2 version 2025-10-06 a July 15, 2026 retirement date and names the 2025-12-08 version as its replacement. Those are separate entries for the same model name. An application inventory needs its deployed version as well as its model family to interpret the schedule correctly.

A blank replacement entry means Microsoft does not name a replacement in this table. It does not establish that every other video tool has disappeared, that a specific competing service is compatible, or that there is an automatic migration path for an existing video workflow.

Microsoft describes the replacement column as its recommended replacement and, where supported, the target for automatic upgrades at retirement. It says customers do not need to wait for a replacement to be listed before evaluating or manually migrating to another compatible model. That guidance does not make any particular alternative a drop-in replacement for Sora 2.

The documentation recommends evaluating available models with the application's own data and comparing quality, latency and cost. For a video workflow, a date on the retirement table alone is not enough to establish matching output behavior, commercial terms or integration requirements. Those need to be checked against the chosen service and tested workflow.

Teams using the listed version should check their deployment inventory and the current Microsoft schedule rather than relying on a general model name. The source supports an October 15 retirement date and no named replacement for this version. It does not establish a universal shutdown timestamp, a tested endpoint-error response or automatic cancellation of related billing commitments.

Original sources

↑ Back to top