LLMIntel
OverviewLive demoCatalogCompareMCPPricingChangelogDocs
Start free
LLMIntel

A verified, normalized feed of AI model lifecycle events across every major provider, so a deprecation shows up on your roadmap instead of in your error logs. Plus runtime telemetry for what those models actually cost you.

Questions? support@llmintel.ai

Product
  • Pricing
  • Compare models
  • Azure OpenAI retirements
  • Dashboard
  • Changelog
  • Contact support
Developers
  • Quickstart
  • Model catalog
  • What’s retiring
  • MCP server
  • API reference
  • OpenAPI spec
  • Lifecycle RSS feed
  • @llmintel/telemetry
Free & open data

The model catalog is a normalized, machine-readable source of truth for AI model lifecycle events. It is free via the public API, and every record links to the primary provider source it came from.

© 2026 Alex Tsimbalistov. All rights reserved.
LLMIntel
OverviewLive demoCatalogCompareMCPPricingChangelogDocs
Start free
← All tracked models

Azure OpenAI model retirement dates

Azure publishes a retirement date for each model deployment and enforces it. When the date passes, requests to that deployment fail, and Azure may upgrade a deployment to a successor version on your behalf. That makes Azure retirements a scheduling problem rather than a judgement call: the date is known in advance, and the work is finding every deployment that depends on the model before the date arrives.

We track 76 Azure OpenAI models, 76 of them with a published retirement date. 21 need attention now.

Retiring or deprecated now

Deprecated models still answer but are superseded. Anything inside the 90-day window has a date attached and will stop answering on it.

Azure OpenAI models that are deprecated or retiring soon
ModelStateRetirementReplacement
gpt-chat-latest (2026-05-05)retiring2026-08-05 · past due—
gpt-chat-latest (2026-05-28)retiring2026-08-28 · past due—
sora-2 (2025-12-08)retiring2026-09-15 · past due—
gpt-chat-latest (2026-06-24)retiring2026-09-24 · in 6 days—
gpt-4o (2024-05-13)retiring2026-10-01 · in 13 daysazure/gpt-5.1
o3-mini (2025-01-31)retiring2026-10-01 · in 13 daysazure/o4-mini
gpt-4.1-nano (2025-04-14)retiring2026-10-14 · in 26 days—
gpt-4o-mini-transcribe (2025-03-20)retiring2026-10-15 · in 27 days—
gpt-4o-transcribe (2025-03-20)retiring2026-10-15 · in 27 days—
o4-mini (2025-04-16)retiring2026-10-16 · in 28 days—
o1 (2024-12-17)retiring2026-10-21 · in 33 daysazure/gpt-5.6-sol
o1-pro (2025-03-19)retiring2026-10-21 · in 33 daysazure/gpt-5.6-sol
o3 (2025-04-16)retiring2026-10-21 · in 33 daysazure/gpt-5.6-sol
codex-mini (2025-05-16)deprecated2026-11-15 · in 58 days—
gpt-audio-mini (2025-10-06)retiring2027-04-06 · in 200 days—
gpt-4.1 (2025-04-14)retiring2027-04-14 · in 208 days—
gpt-4.1-mini (2025-04-14)retiring2027-04-14 · in 208 days—
gpt-4o (2024-08-06)retiring2027-04-14 · in 208 daysazure/gpt-5.1
gpt-4o (2024-11-20)retiring2027-04-14 · in 208 daysazure/gpt-5.1
gpt-4o-mini (2024-07-18)retiring2027-04-14 · in 208 days—
gpt-4o-transcribe-diarize (2025-10-15)retiring2027-04-15 · in 209 days—

Already retired

These ids no longer answer. If one appears in your code or in something an assistant wrote for you, it is already broken.

Azure OpenAI models that are already retired
ModelStateRetirementReplacement
gpt-4o (2024-08-06-ev3)retired2026-03-31 · retiredazure/gpt-5.1
gpt-5-chat (2025-10-03)retired2026-05-13 · retiredazure/gpt-chat-latest
gpt-5.2-chat (2025-12-11)retired2026-05-13 · retiredazure/gpt-chat-latest
gpt-5-chat (2025-08-07)retired2026-06-29 · retiredazure/gpt-chat-latest
gpt-5.1-chat (2025-11-13)retired2026-06-29 · retiredazure/gpt-chat-latest
gpt-5.2-chat (2026-02-10)retired2026-06-29 · retiredazure/gpt-chat-latest
gpt-5.3-chat (2026-03-03)retired2026-06-29 · retiredazure/gpt-chat-latest
sora-2 (2025-10-06)retired2026-07-15 · retiredazure/sora-2-2025-12-08
gpt-realtime-mini (2025-10-06)retired2026-09-21 · retired—

Currently safe

Active, announced, or legacy with no imminent date. Legacy models are superseded but still served.

Azure OpenAI models with no imminent retirement
ModelStateRetirementReplacement
gpt-4o-mini-transcribe (2025-12-15)active2027-06-15 · in 270 days—
gpt-4o-mini-tts (2025-03-20)active2026-10-15 · in 27 days—
gpt-4o-mini-tts (2025-12-15)active2027-06-15 · in 270 days—
gpt-5 (2025-08-07)active2027-02-09 · in 144 days—
gpt-5-codex (2025-09-15)active2027-03-17 · in 180 days—
gpt-5-mini (2025-08-07)active2027-02-09 · in 144 days—
gpt-5-nano (2025-08-07)active2027-02-09 · in 144 days—
gpt-5-pro (2025-10-06)active2027-04-07 · in 201 days—
gpt-5.1 (2025-11-13)active2027-05-15 · in 239 days—
gpt-5.1-codex (2025-11-13)active2027-05-15 · in 239 days—
gpt-5.1-codex-max (2025-12-04)active2027-05-18 · in 242 days—
gpt-5.1-codex-mini (2025-11-13)active2027-05-15 · in 239 days—
gpt-5.2 (2025-12-11)active2027-06-08 · in 263 days—
gpt-5.2-codex (2026-01-14)active2027-07-13 · in 298 days—
gpt-5.3-codex (2026-02-24)active2027-08-24 · in 340 days—
gpt-5.4 (2026-03-05)active2027-09-02 · in 349 days—
gpt-5.4-mini (2026-03-17)active2027-09-21 · in 368 days—
gpt-5.4-nano (2026-03-17)active2027-09-21 · in 368 days—
gpt-5.4-pro (2026-03-05)active2027-09-07 · in 354 days—
gpt-5.5 (2026-04-24)active2027-10-26 · in 403 days—
gpt-5.6-luna (2026-07-09)active2028-01-11 · in 480 days—
gpt-5.6-sol (2026-07-09)active2028-01-11 · in 480 days—
gpt-5.6-terra (2026-07-09)active2028-01-11 · in 480 days—
gpt-audio (2025-08-28)active2027-03-02 · in 165 days—
gpt-audio-1.5 (2026-02-23)active2027-08-24 · in 340 days—
gpt-audio-mini (2025-12-15)active2027-06-15 · in 270 days—
gpt-chat-latest (2026-08-06)announced2026-12-02 · in 75 days—
gpt-image-1 (2025-04-15)active2026-10-23 · in 35 days—
gpt-image-1-mini (2025-10-06)active2027-04-07 · in 201 days—
gpt-image-1.5 (2025-12-16)active2027-06-16 · in 271 days—
gpt-image-2 (2026-04-21)active2027-10-21 · in 398 days—
gpt-realtime (2025-08-28)active2027-03-02 · in 165 days—
gpt-realtime-1.5 (2026-02-23)active2027-08-24 · in 340 days—
gpt-realtime-2 (2026-05-06)active2026-08-31 · past due—
gpt-realtime-2.1 (2026-07-07)active2027-06-25 · in 280 days—
gpt-realtime-2.1-mini (2026-07-07)active2027-06-25 · in 280 days—
gpt-realtime-mini (2025-12-15)active2026-12-15 · in 88 days—
o3-deep-research (2025-06-26)active2026-12-26 · in 99 days—
o3-pro (2025-06-10)active2026-12-17 · in 90 days—
text-embedding-3-large (1)active2028-02-09 · in 509 days—
text-embedding-3-small (1)active2028-02-09 · in 509 days—
text-embedding-ada-002 (1)active2028-02-09 · in 509 days—
text-embedding-ada-002 (2)active2028-02-09 · in 509 days—
tts (001)active2026-12-15 · in 88 days—
tts-hd (001)active2026-12-15 · in 88 days—
whisper (001)active2026-12-15 · in 88 days—

Find out which of these you are paying for

A list of dates only helps once you know which of these models your own traffic hits. One line of code meters the models your app actually calls, then reports the monthly spend sitting on each retiring id and what the move to its replacement costs.

See it on sample trafficStart free

Other providers

OpenAIAnthropic ClaudeAWS BedrockGoogle Gemini and Vertex AICohere

Source: Microsoft Learn — Azure OpenAI model retirement schedule. Every record links the page it was parsed from and keeps Azure AI Foundry’s own wording, so a normalization decision stays checkable.

LLMIntel

A verified, normalized feed of AI model lifecycle events across every major provider, so a deprecation shows up on your roadmap instead of in your error logs. Plus runtime telemetry for what those models actually cost you.

Questions? support@llmintel.ai

Product
  • Pricing
  • Compare models
  • Azure OpenAI retirements
  • Dashboard
  • Changelog
  • Contact support
Developers
  • Quickstart
  • Model catalog
  • What’s retiring
  • MCP server
  • API reference
  • OpenAPI spec
  • Lifecycle RSS feed
  • @llmintel/telemetry
Free & open data

The model catalog is a normalized, machine-readable source of truth for AI model lifecycle events. It is free via the public API, and every record links to the primary provider source it came from.

© 2026 Alex Tsimbalistov. All rights reserved.