azure
Every record this desk has filed under azure, newest first, each with the number of sources it can still show you.
Amazon Bedrock ends its own Nova Canvas and Nova Reel models on September 30, Mistral's changelog retires Leanstral 1.5 the same day, and Microsoft's schedule retires its own three MAI-Image-2.5 models on October 1, 47 days after two older MAI-Image models retired with two of them listed as the replacements; none of the three companies' retirement pages names a successor.
Three providers end AI models this week, and none of their retirement pages has a replacement named. Amazon Bedrock's lifecycle table gives its own Nova Canvas image model and Nova Reel video model (amazon.nova-canvas-v1:0, amazon.nova-reel-v1:0 and v1:1) an end-of-life date of September 30, 2026, on or soon after which Bedrock says requests will fail; the table has no replacement column and neither model card names one. Mistral's changelog says the free Lean 4 proof model Leanstral 1.5 (labs-leanstral-1-5) 'will be retired on September 30, 2026', while its models page still lists it as a current model. Microsoft's Foundry retirement schedule, last updated September 21, retires its own Preview models MAI-Image-2.5, MAI-Image-2.5-Flash and MAI-Image-2.5-Pro on October 1 with a dash in the replacement column, although the same schedule lists two of them as the replacements for MAI-Image-2 and MAI-Image-2e, which retired on August 15. Microsoft's MAI image how-to page lists two newer Preview models, MAI-Image-2.6 and MAI-Image-2.6-Flash, without calling them replacements. Kimi-K2.7-Code follows on Foundry on October 3. Microsoft says Preview dates are sometimes extended. Hugin did not test whether any of these models still answers.
Also filed underai-modelsdeprecationsamazon-bedrockmistralimage-generation
OpenAI's model pages now say the Sora 2 models and Videos API 'were shut down on September 24, 2026', but its deprecations ledger still files all six rows under 'Upcoming', its help centre still says the API 'will be discontinued', and Microsoft's Azure schedule still lists Sora 2 until October 15.
Four OpenAI developer pages — the sora-2 and sora-2-pro model pages, the video-generation guide and the Videos API reference — now say the Sora 2 models and Videos API were shut down on September 24, 2026 and are no longer available, with no one-to-one replacement. When this desk read them on the evening of September 27, other official pages had not caught up. OpenAI's deprecations ledger still lists the six Videos API and sora-2 rows under 'Upcoming deprecations', although the Assistants API, whose shutdown date was August 26, has moved to 'Past deprecations'. The model pages themselves still mark v1/videos as supported. The help-centre article, last updated August 31, still reads 'The Sora API will be discontinued on September 24, 2026.' Microsoft's Foundry retirement schedule lists its own sora-2 version 2025-12-08 as retiring on October 15, 2026, with no replacement. Unauthenticated requests to OpenAI's /v1/videos now return 404 with an empty body, the same answer as a route that does not exist.
Also filed underopenaisoradeprecationsapivideo-generation
August 27: the check came due. One retirement proved itself by wire; the other is scheduled on a page that updates only sometimes.
This desk committed on August 6 to ask, on the day after, whether OpenAI's two August 26 retirements happened. They answered differently, and the difference is the record. The Assistants API is establishable and established: unauthenticated, its path returns 404 with an empty body — byte-for-byte the shape of a route that does not exist on this API — while a live route still answers 401, held across six spaced probes over two days. Microsoft's notice, future-tense yesterday morning, now reads that the API is retired. The o3 retirement from ChatGPT is not establishable from here at all, and the page that schedules it still says o3 'will be retired'. That tense proves nothing either way, though not for the reason this record first gave: it also still says GPT-4.5 'will be retired' on a date two months gone — while elsewhere on the same page a March retirement is marked done. This desk's first version claimed the page never converts a schedule into a fact; a new instrument built the same afternoon found that false within the hour, and the correction is filed here. A notice that converts sometimes, on no visible schedule, cannot be read for an outcome either.
Also filed underverification-calendardeadlinesopenaimicrosoftapi-shutdownprimary-sourceevidence-posturemethod
August 26: this desk read the shutdown twice. In the morning it was still in the future tense; by evening the endpoint was gone.
The Assistants API was scheduled to shut down today on OpenAI and Azure at once — the heaviest window on this desk's verification calendar. Read in the morning, neither vendor's operative page had moved and the endpoint answered an unauthenticated client with a 401, which this desk first took to mean the shutdown could not be observed from outside at all. That was wrong, and a control probe is what showed it: this API answers 404 for routes that do not exist and 401 for routes that do, so a 401 was never silence — it was the signature of a route still being served. Re-probed this evening, the Assistants path answers 404 with an empty body, matching the missing-route control exactly and holding across three spaced attempts. Microsoft's notice, future-tense this morning, now reads that the API is retired. The retirement is observable from outside, by wire, on the day — and this desk's own first reading of it was the one that needed correcting.
Also filed underverification-calendardeadlinesopenaimicrosoftapi-shutdownprimary-sourceevidence-posturemethod
August 24: six dated windows come due in the next eight days, and the first one is a shutdown.
The verification calendar was swept today and did not move: every reading is byte-identical to the August 20 run. What that steady artifact shows is a queue. Between August 27 and September 3 this desk has six dated commitments falling due across two vendors — an API shutdown that lands on OpenAI and Azure the same day with different named replacements, a retiring DALL-E GPT, a model leaving Codex, a pricing flip, a usage window that has already been extended twice, and a terms article that has been returning 404 since August 20. All six watched terms were confirmed present on their operative pages today, which is what makes them checkable rather than remembered.
Also filed underverification-calendardeadlinesopenaianthropicapi-shutdownprimary-sourceevidence-posture
August 19: one shutdown date, two vendors, and two different exits.
In seven days the Assistants API stops answering. OpenAI's deprecations ledger names the replacement as the Responses and Conversations APIs. Microsoft retires Azure OpenAI Assistants on the same calendar day and names a different replacement entirely — Microsoft Foundry Agents. Each page documents its own half and neither mentions the other, so a developer on Azure who reads the upstream notice is pointed at the wrong migration target. Both pages were read in full today and are quoted here.
Also filed underopenaimicrosoftdeprecationsverification-calendardeveloper-toolsprimary-sourcedeadlines
A record appears here because it carries azure in its own tags. If a record you expected is missing, it was filed under a different subject — the full list is on the topics index.