Which models Microsoft Foundry carries

Microsoft Foundry (learn.microsoft.com) publishes a dated retirement table, and two of its rows are video: sora-2 version 2025-10-06 retired on 15 July 2026, and version 2025-12-08 is scheduled to retire on 15 October 2026. As of 2026-09-12.

Inclusion rule. Models the app names on its own public pages. A model the app does not name is not listed, and an end date is recorded only when the vendor that makes the model has announced one. Order. As the app orders them on its own page.

1How many models each application names

Inclusion rule. Entries whose own pages name a model, a version identifier or a lifecycle state. House tier names with no model behind them are not counted. Order. Alphabetical by entry name.

Inclusion rule. Counted only where the vendor that makes the model has announced a date in public. A date reported by press coverage alone is not counted. Order. Alphabetical by entry name.

2A reseller's date can outlast the maker's own

The maker of this model has already closed its own API: OpenAI states the Sora API is discontinued on 24 September 2026. The platform row here runs to 15 October 2026. Both statements come from the company that published them, both are current, and this register writes them side by side without reconciling them, because reconciling them would mean guessing at a hosting arrangement nobody has described in public.

That is the single most useful thing on this page for a production. The date that governs a pipeline is the date published by whoever you actually call, and it is not necessarily the one in the headline announcement. A team reading only the maker's notice would have retired this workload three weeks early; a team reading only the platform would have missed that the model's own vendor had already stopped selling it.

3Where this register finally gets a notice period in days

This platform commits to at least sixty days of warning for a generally available model and at least thirty for a preview one, says an endpoint answers requests with a gone response once the date passes, and states that dates are not extendable on request. Those are the answers this register has been recording as unpublished across every application it tracks.

The catch is which stage the video rows sit in. Both are preview, so thirty days is the applicable figure, and the platform's own documentation says preview deployments are either force-upgraded to a successor or terminated, with no option to stay. A commitment of thirty days plus a forced move is a real published policy and a thin one, and it is still more than any application page in this register offers. The other platform entry, Amazon Bedrock, states a longer one.

4Read column by column

This register reads Microsoft Foundry along notice period, named replacement, stored work, default tier, lifecycle states and ending early. One page each.

• Notice period — 60 days for a live model, 30 for a preview, and dates that cannot be moved
• Named replacement — one dated row names its successor, and it is a later version of the same model
• Stored work — requests return 410 Gone after the date, and nothing is said about material
• Default tier — a deployment names a version, so a default would defeat the point of the schedule
• Lifecycle states — preview and generally available are states, and which one applies decides the notice owed
• Ending early — a date that cannot be pushed back, which removes an exception people expect to negotiate

5Sources

Menu taken from the model retirement schedule on learn.microsoft.com, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.

• sora-2 version 2025-10-06
  15 July 2026retirement date, replaced by sora-2 version 2025-12-08Microsoft Foundry, retirement schedule / recorded 2026-09-22
• sora-2 version 2025-12-08
  15 October 2026retirement date, no replacement namedMicrosoft Foundry, retirement schedule / recorded 2026-09-22
• Notice for a generally available model
  At least 60 days before retirementsent to subscriptions with active deploymentsMicrosoft Foundry, lifecycle and support policy / recorded 2026-09-22
• Notice for a preview model
  At least 30 days before retirementwhich is the stage sora-2 sits inMicrosoft Foundry, lifecycle and support policy / recorded 2026-09-22
• What the endpoint does after the retirement date
  All inference requests return 410 GoneMicrosoft Foundry, lifecycle and support policy / recorded 2026-09-22
• Whether a date can be pushed back on request
  Retirement dates are not extendableMicrosoft Foundry, lifecycle and support policy / recorded 2026-09-22