What Microsoft Foundry owes you before a model goes

Microsoft Foundry publishes a notice period as policy rather than per retirement: at least 60 days before a generally available model goes, at least 30 for a preview one. Notices reach subscriptions with active deployments. The dates are stated to be non-extendable, and after one passes every request returns 410 Gone. As of 2026-09-22.

Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.

The four questions this column asks, answered from the lifecycle policy page. Recorded 2026-09-22.
What the page is asked	What Microsoft Foundry publishes	What that leaves open
How much notice for a live model	At least 60 days	Which subscriptions count as having a deployment
How much notice for a preview model	At least 30 days	That is the stage the video model sits in
Can the date be pushed back	Retirement dates are not extendable	No exception route is described anywhere
What the endpoint does afterwards	All inference requests return 410 Gone	No grace window is described after the date

Inclusion rule. Rows are the questions this register asks in this column, answered only from the platform's own lifecycle page. A figure quoted in coverage of the platform does not fill a row. Order. Policy figures first, then what happens once a date arrives.

1A policy published before anything is scheduled

The figure here is not attached to a particular model. It is a commitment made in advance about every model the platform will ever retire, which is a different instrument from a notice that happens to arrive two months early.

That distinction is the reason this reading exists. A number published before the schedule exists can be designed around by somebody who has not yet chosen a model; a number observed after the fact only tells you what one team decided once.

Fig. 2 Which figure applies is decided by the model's stage, not by the size of the customer holding the deployment.

2Thirty days is the figure that applies to video

The shorter of the two periods covers preview models, and the video model this platform hosts is at preview stage. So the commitment a video production actually holds here is a month, not two, and the longer figure belongs to somebody else's workload.

A month is enough to stop starting new work and not enough to regenerate a season. Read against the register's other columns, that makes this platform the fastest-moving entry that has committed to anything at all.

3Non-extendable cuts both ways

Stating that a date cannot be pushed back removes a conversation many teams assume they can have. There is no described route by which a large customer with work in flight gets another fortnight, which is unusually direct for a platform document.

It is also the more plannable position. A date that might move is a date nobody schedules against, and a production that knows the day is fixed can put the migration in a calendar instead of keeping it as an open worry.

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
Whether a date can be pushed back on request
Retirement dates are not extendableMicrosoft 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

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 Notice period. Same column, other entries: Amazon Bedrock, Gemini API.