Menu

o3 retires on Azure 22 days before OpenAI's API. Same model, two shutdown dates.
📰

o3 retires on Azure 22 days before OpenAI's API. Same model, two shutdown dates.

DEV Community: azure·Versyka·about 1 hour ago
#vavTO1f8
#devtoazure#devto#dev#model#azure
Reading 0:00
15s threshold

Versyka

Posted on Nov 19

AI-assisted

Azure kills your o3 22 days before OpenAI does. Not December. Same model, two dates:

On OpenAI's API , o3-2025-04-16 shuts down on December 11, 2026 .

On Azure OpenAI , the o3 (2025-04-16) deployment retires on November 19, 2026 .

Also retiring on Azure on November 19:

Azure model (version) Suggested replacement

o1 (2024-12-17), o1-pro (2025-03-19) gpt-5.6-sol

o3 (2025-04-16), o3-pro (2025-06-10), o3-deep-research (2025-06-26) gpt-5.6-sol

o3-mini (2025-01-31), o4-mini (2025-04-16) gpt-5.6-terra

Why this catches teams

Most people track the model maker's deprecation page. But the cloud that hosts the model keeps its own calendar, with its own dates and its own replacements. Azure does, Amazon Bedrock does, Google Vertex AI does. Sometimes the cloud is later. This time it's three weeks earlier.

A second trap: on Azure, your code calls a deployment name you chose, not the model ID.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.