
AI Model Shutdowns Are Announced Months Ahead. Who in Your Company Reads Them?
On Thursday, 19 November, Microsoft retired seven Azure OpenAI models: o1, o1-pro, o3, o3-deep-research, o3-pro, o3-mini and o4-mini. Under Microsoft's lifecycle policy, a retired model is removed from service and every request to it returns 410 Gone. Some deployments were switched to a newer model automatically. Others simply stopped answering.
None of this was a surprise to anyone who reads vendor documentation. The dates had been published for months, and more are coming: 30 November for Claude Sonnet 4.5 and three OpenAI developer tools, 11 December for GPT-5 and o3 on OpenAI's own API, and 11 January for a specific EU data residency option. The question for a company with 100 or 1,000 people is simpler and less technical: does anyone inside the business know which model their AI integrations call, and when that model goes away?
The dates between now and mid-January
The table below covers the items most likely to sit inside a mid-size company's integrations. It is not a complete list; every vendor publishes its own.
| Date | Platform | What stops | Vendor's suggested replacement |
|---|---|---|---|
| 19 Nov 2026 (passed) | Azure OpenAI in Microsoft Foundry | o1, o1-pro, o3, o3-deep-research, o3-pro | gpt-5.6-sol |
| 19 Nov 2026 (passed) | Azure OpenAI in Microsoft Foundry | o3-mini, o4-mini | gpt-5.6-terra |
| 30 Nov 2026 | Claude API, Microsoft Foundry and other Anthropic-operated platforms | Claude Sonnet 4.5 | claude-sonnet-5-5 |
| 30 Nov 2026 | OpenAI API | Agent Builder, the Evals dashboard and API, reusable prompt objects (/v1/prompts) | Agents SDK or ChatGPT Workspace Agents; Promptfoo; prompts kept in your own code |
| 11 Dec 2026 | OpenAI API | gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-pro, o3, o3-pro | gpt-6.1-sol, gpt-6.1-terra, gpt-6-luna |
| 11 Jan 2027 | OpenAI API | GPT-5.2, GPT-5.4 and GPT-5.4 mini with EU data residency on the fast or priority tier | Same models on standard processing, or the GPT-6.2 family |
Sources: Microsoft's model retirement schedule, OpenAI's deprecations page and Anthropic's model deprecations page. Anthropic's dates apply to the platforms it operates; Amazon Bedrock and the Google-managed listing on Google Cloud set their own schedules.
The loud failure and the quiet one
A retirement reaches a business in one of two ways, and they need different kinds of attention.
The loud way is an error. If a deployment on Azure is set to NoAutoUpgrade, Microsoft's deployment documentation says it stops working on the retirement date and the code has to be pointed at a different deployment. The same happens with any call to a shut-down model on OpenAI's or Anthropic's API. An invoice-reading step, a ticket classifier or a quote assistant just fails. Someone notices within hours because a process stops, and the fix is usually a day of developer time, assuming a developer is available and the original builder left notes.
The quiet way is the automatic upgrade. On Azure, deployments set to upgrade once the current version expires are moved to the vendor's default replacement when the old model retires. Nothing breaks, so nobody looks. But the model answering your requests is now a different one. It may format output differently, follow instructions more or less literally, write longer answers and bill at a different rate. Check what the replacement costs under your own agreement before the switch, not after the next invoice.
Anthropic's documentation shows a third, smaller trap: parameters can disappear too. From API version 2026-10-21, its API rejects temperature, top_p and top_k with a 400 error, so a migration can fail on a setting that was never a problem before.
My read is that the quiet failure is the more expensive one for a mid-size company. A broken integration gets fixed because it hurts. A slightly worse or slightly more expensive one can run for months, and when somebody finally asks why the AI assistant "got worse in November", the link to a vendor's retirement table is hard to make.
The EU detail that is easy to miss
Many European companies chose EU data residency for their OpenAI usage for GDPR reasons. On 18 November OpenAI gave notice that GPT-5.2, GPT-5.4 and GPT-5.4 mini, when used with EU data residency on the fast or priority tier, will be deprecated on 11 January 2027. The suggested path is the same models on standard processing or the newer GPT-6.2 family, according to the deprecations page.
This is narrow, and most companies will not be affected. But it shows something general: the configuration you picked for compliance reasons can have a shorter life than the default one. Whoever owns the integration should know which tier and which region it runs on, and not just which model.
The test tool is on the list as well
One line in OpenAI's table deserves a second look. On 30 November the Evals dashboard, API and graders shut down, and OpenAI points users to Promptfoo, an open-source testing tool. Evals is the feature many teams used to check whether a new model still gives acceptable answers. If your developer or vendor relied on it to approve model changes, the safety net disappears on the same day as several migrations become due.
The lesson is not specific to OpenAI. Tests that live inside one vendor's console belong to that vendor's roadmap. A set of real examples with the expected answers, kept in your own repository or even a shared spreadsheet, survives any vendor change.
A hypothetical example
Imagine a 180-person logistics company in Ruse. In spring 2025 an external developer built a small service on Azure that reads incoming customer emails, extracts the shipment number and sorts each message into one of six queues. It ran on o4-mini, with the deployment left on automatic upgrades. The developer moved on to other projects; the operations manager knows the tool as "the email sorter".
On 19 November the deployment moved to gpt-5.6-terra. Nothing failed. Over the following weeks the team notices that more emails land in "urgent", and finance sees a higher Azure line on the December invoice. Both have explanations, but nobody connects either one to a model change, because nobody in the company knew there had been one.
Nothing in this scenario requires a mistake by anyone. It only requires that the model name lived in the developer's head and nowhere else.
One question to send this week
Vendors give long notice. OpenAI promises at least six months for generally available models, though preview models can go with as little as two weeks. Anthropic gives at least 60 days. Microsoft states that retirement dates are not extendable. The information exists; the gap is inside the company.
So the practical step is a single message to whoever built or runs each AI integration, whether that is an internal developer, an agency or a SaaS vendor: which model and version does it call, on which platform and region, and what is the shutdown date? Ask them to add what happens on that date: automatic switch, error, or manual migration. Anthropic customers can answer part of this from the Console usage export, which breaks usage down by API key and model; OpenAI's model list exposes a shutdown_date field for the same purpose.
Then put each date in the calendar of a named person, 30 days early, together with the twenty or so real examples that should be re-run before the switch. That is the whole discipline of running AI after go-live, and it is cheaper than one week of a quietly misrouted inbox. If no one in the company is in a position to own this, it is the kind of work our AI Ops service covers, but the question above is worth asking either way.


