LLMSwaps

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

What happens to a request, and not to a file

The lifecycle page is precise about the interface and silent about material: after a retirement date all inference requests return 410 Gone. Nothing addresses output already generated, because on this platform output is returned to the caller rather than kept in a library. As of 2026-09-22.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryWhat Microsoft Foundry publishesWhat MicrosoftFoundry publishesWhat that leaves openWhat that leavesopenIs disposal of material address…Is disposal of material addressedIs disposal of material addressed — What Microsoft Foundry publishes: Not addressed on the lifecycle pageIs disposal of material addressed — What that leaves open: Output is returned to the caller, not storedWhat happens to a requestWhat happens to a request — What Microsoft Foundry publishes: All inference requests return 410 GoneWhat happens to a request — What that leaves open: A specific status rather than a vague failureIs there a degraded mode firstIs there a degraded mode first — What Microsoft Foundry publishes: None is describedIs there a degraded mode first — What that leaves open: The state changes on the date, not graduallyCan the date be deferredCan the date be deferred — What Microsoft Foundry publishes: Dates are stated to be non-extendableCan the date be deferred — What that leaves open: So the cut-off is the date on the page
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What the lifecycle page settles about the moment after a date. Recorded 2026-09-22.
What the page is askedWhat Microsoft Foundry publishesWhat that leaves open
Is disposal of material addressedNot addressed on the lifecycle pageOutput is returned to the caller, not stored
What happens to a requestAll inference requests return 410 GoneA specific status rather than a vague failure
Is there a degraded mode firstNone is describedThe state changes on the date, not gradually
Can the date be deferredDates are stated to be non-extendableSo the cut-off is the date on the page

Inclusion rule. Read from the platform's lifecycle and support policy page. Storage behaviour of other services on the same cloud is out of scope for this column. Order. The absence first, then what the page does describe.

1A status code is a useful kind of precision

Naming the exact response after a retirement is more than most pages manage. A caller can branch on it, alert on it, and tell it apart from a transient failure, which turns a retirement into a condition software can handle.

It also means the failure is unambiguous at the moment it happens. A production that watches for this status learns about the date from its own logs rather than from a page somebody forgot to re-read.

Losing the files and losing the means are separateA platform that never held the output has nothing to delete, so the retirement takes away only the ability to make more. For a series that is the more expensive half, because it is invisible until somebody needs another episode in the same look.RetentionReproducibilityWhat is lostFiles that already existThe ability to make moreVisibleImmediatelyOnly when you next need itAddressed hereNothing held, nothing to say410 Gone on the dateWhat protects youArchiving elsewhereNothing available at any priceTwo losses a single date can cause
Fig. 2 Recorded as not addressed with a structural explanation rather than as an unexplained silence.

2Where a platform keeps nothing, the column is quiet for a reason

On this layer the customer's files live wherever the customer put them. There is no gallery and no project store, so a retirement has nothing to delete and the page has nothing to promise.

Recorded as not addressed rather than as silence, because the structure of the product is the explanation. A consumer application with a library inside it has the same question and a much heavier answer.

3The part that is still a risk

Losing the ability to regenerate is not the same as losing the files, and it is the loss this platform does impose. Anything that depended on being able to produce more material in the same look stops on the date.

That is why keeping the outputs rather than the ability to remake them is the advice that survives every arrangement in this column, including the ones with nothing to delete.

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