A state that decides how much notice is owed
Two stages are published here, preview and generally available, and the distinction is not cosmetic: it decides how much notice a retirement owes. The hosted video model sits at preview stage, which is why the shorter of the platform's two commitments is the one a video production holds. As of 2026-09-22.
| What the page is asked | What Microsoft Foundry publishes | What that leaves open |
|---|---|---|
| How many stages are named | Two, preview and generally available | Plus retired, once a date has passed |
| What the stage decides | Thirty days of notice, or sixty | So the label carries a contractual weight |
| Which stage the video model is in | Preview, and therefore the shorter figure | A production here holds a month, not two |
| What follows the last stage | Requests return 410 Gone | A named status rather than a vague failure |
Inclusion rule. A state counts when the entry publishes the label itself. A marketing word such as new or classic is not a lifecycle state and does not fill a row. Order. How many stages first, then what each one obliges.
1A stage with a number attached is rare
Preview labels are everywhere in this field and almost always mean only that a vendor reserves the right to change things. Here the label is wired to a figure, which makes it the one place where a stage name tells a reader exactly what they are owed.
That also makes the label worth watching. A model moving from preview to general availability doubles the notice it carries, and nothing else about the product needs to change for that to happen.
2The shorter figure is the one in force for video
Because the hosted video model is at preview stage, this platform's commitment to a video production is thirty days. Reading the sixty-day figure as the applicable one is the easy mistake, and it doubles the runway a plan assumes.
The register records both figures and marks which applies. A commitment that depends on a stage is only useful to somebody who checked the stage.
3Retirement is a third condition, and it is final
Once a date passes the state is effectively retired: requests return a specific status and the dates themselves are stated to be non-extendable. There is no described way back.
Combined with the stage system, that gives this entry the most complete lifecycle vocabulary in the register after the three-state platform. The ending early reading covers what non-extendable does to a plan.
- Notice for a preview modelAt least 30 days before retirementwhich is the stage sora-2 sits in
- Notice for a generally available modelAt least 60 days before retirementsent to subscriptions with active deployments
- What the endpoint does after the retirement dateAll inference requests return 410 Gone
4Sources
Read from the model retirement schedule on learn.microsoft.com, 2026-09-22. The whole entry is on Microsoft Foundry, and the column it sits in is on Lifecycle states. Same column, other entries: Gemini API, Sora.