LLMSwaps

Which model each app runs today, and when it last changed

A date that arrives and cannot be moved

This entry approaches the column from the opposite side. Access cannot end earlier than the published date, and it cannot end later either: retirement dates are stated to be non-extendable. No exception route is described for a large customer with work in flight. As of 2026-09-22.

What the lifecycle policy says about a date moving in either direction. Recorded 2026-09-22.
What the page is askedWhat Microsoft Foundry publishesWhat that leaves open
Can the date be pushed backNo, dates are stated as non-extendableAnd no exception process is described
Can access end before itNothing published suggests it canThe notice period runs up to the date
How long is that noticeThirty days at preview stageSixty once a model is generally available
What happens on the dayRequests return 410 GoneWhich is a clean stop, not a taper

Inclusion rule. A cell is filled from a published sentence about access ending other than on a stated date. A reader's estimate of how fast a menu could change does not fill one. Order. What cannot move first, then what the date leads to.

1Refusing extensions is unusually direct

Most enterprise documents leave room for an exception, on the reasonable assumption that a large customer will eventually ask. Stating plainly that dates do not move closes a conversation many teams assume they can have.

It reads as unhelpful and plans better. A date that might move is a date nobody schedules against, and the whole value of a published schedule is that it can go into a calendar.

2Fixed in both directions is the most plannable arrangement here

Nothing suggests access ends early, and the notice period runs up to the date. So a production gets exactly the runway printed, which no other entry in this column can say.

Compare the platform that publishes months and then allows a fortnight of disuse to end access anyway. Length is not the only property of a window; predictability is the other, and the two come apart.

Length and predictability come apartOne platform publishes months and then allows a fortnight of disuse to end access anyway. Another publishes a month and states that the date cannot move in either direction. The second runway is shorter and the only one that goes into a calendar.Months, conditionalA month, fixedPublished lengthSix months or 45 daysThirty days at preview stageCan end soonerAfter 15 days of disuseNothing published suggests itCan be extendedNot addressedStated as non-extendableGoes in a calendarOnly tentativelyYesTwo properties of a window, and they do not travel together
Fig. 1 A date that might move is a date nobody schedules against, which is the whole value of publishing a schedule.

3The stage is what sets the length

Thirty days applies at preview stage, which is where the hosted video model sits. So the fixed runway is a month, and its fixity is what makes a month usable at all.

The state reading covers how the stage decides the figure. Reading the longer number as the applicable one is the easy mistake and it doubles what a plan assumes.

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 Ending early. Same column, other entries: Gemini API, LTX Studio.