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 79 Azure OpenAI models, 79 of them with a published retirement date. 27 need attention now.
Deprecated models still answer but are superseded. Anything inside the 90-day window has a date attached and will stop answering on it.
| Model | State | Retirement | Replacement |
|---|---|---|---|
| codex-mini (2025-05-16) | retiring | 2026-11-15 · in 13 days | — |
| gpt-chat-latest (2026-05-05) | retiring | 2026-11-17 · in 15 days | — |
| gpt-chat-latest (2026-06-24) | retiring | 2026-11-17 · in 15 days | — |
| o1 (2024-12-17) | retiring | 2026-11-19 · in 17 days | azure/gpt-5.6-sol |
| o1-pro (2025-03-19) | retiring | 2026-11-19 · in 17 days | azure/gpt-5.6-sol |
| o3 (2025-04-16) | retiring | 2026-11-19 · in 17 days | azure/gpt-5.6-sol |
| o3-deep-research (2025-06-26) | retiring | 2026-11-19 · in 17 days | azure/gpt-5.6-sol |
| o3-mini (2025-01-31) | retiring | 2026-11-19 · in 17 days | azure/gpt-5.6-terra |
| o3-pro (2025-06-10) | retiring | 2026-11-19 · in 17 days | azure/gpt-5.6-sol |
| o4-mini (2025-04-16) | retiring | 2026-11-19 · in 17 days | azure/gpt-5.6-terra |
| gpt-chat-latest (2026-05-28) | retiring | 2026-12-08 · in 36 days | — |
| gpt-4o (2024-05-13) | retiring | 2026-12-09 · in 37 days | azure/gpt-5.6-sol |
| gpt-realtime-mini (2025-12-15) | retiring | 2026-12-15 · in 43 days | — |
| tts (001) | retiring | 2026-12-15 · in 43 days | — |
| tts-hd (001) | retiring | 2026-12-15 · in 43 days | — |
| whisper (001) | retiring | 2026-12-15 · in 43 days | — |
| gpt-image-1.5 (2025-12-16) | retiring | 2026-12-16 · in 44 days | — |
| gpt-chat-latest (2026-08-06) | retiring | 2027-01-12 · in 71 days | — |
| gpt-realtime-2 (2026-05-06) | retiring | 2027-01-20 · in 79 days | azure/gpt-realtime-2.1 |
| gpt-audio-mini (2025-10-06) | retiring | 2027-04-06 · in 155 days | — |
| gpt-4.1 (2025-04-14) | retiring | 2027-04-14 · in 163 days | — |
| gpt-4.1-mini (2025-04-14) | retiring | 2027-04-14 · in 163 days | — |
| gpt-4.1-nano (2025-04-14) | retiring | 2027-04-14 · in 163 days | — |
| gpt-4o (2024-08-06) | retiring | 2027-04-14 · in 163 days | azure/gpt-5.1 |
| gpt-4o (2024-11-20) | retiring | 2027-04-14 · in 163 days | azure/gpt-5.1 |
| gpt-4o-mini (2024-07-18) | retiring | 2027-04-14 · in 163 days | — |
| gpt-4o-transcribe-diarize (2025-10-15) | retiring | 2027-04-15 · in 164 days | — |
These ids no longer answer. If one appears in your code or in something an assistant wrote for you, it is already broken.
| Model | State | Retirement | Replacement |
|---|---|---|---|
| gpt-4o (2024-08-06-ev3) | retired | 2026-03-31 · retired | azure/gpt-5.1 |
| gpt-5-chat (2025-10-03) | retired | 2026-05-13 · retired | azure/gpt-chat-latest |
| gpt-5.2-chat (2025-12-11) | retired | 2026-05-13 · retired | azure/gpt-chat-latest |
| gpt-5-chat (2025-08-07) | retired | 2026-06-29 · retired | azure/gpt-chat-latest |
| gpt-5.1-chat (2025-11-13) | retired | 2026-06-29 · retired | azure/gpt-chat-latest |
| gpt-5.2-chat (2026-02-10) | retired | 2026-06-29 · retired | azure/gpt-chat-latest |
| gpt-5.3-chat (2026-03-03) | retired | 2026-06-29 · retired | azure/gpt-chat-latest |
| sora-2 (2025-10-06) | retired | 2026-07-15 · retired | azure/sora-2-2025-12-08 |
| gpt-realtime-mini (2025-10-06) | retired | 2026-09-21 · retired | — |
| gpt-4o-mini-transcribe (2025-03-20) | retired | 2026-10-15 · retired | — |
| gpt-4o-mini-tts (2025-03-20) | retired | 2026-10-15 · retired | — |
| gpt-4o-transcribe (2025-03-20) | retired | 2026-10-15 · retired | — |
| sora-2 (2025-12-08) | retired | 2026-10-15 · retired | — |
| gpt-image-1 (2025-04-15) | retired | 2026-10-23 · retired | — |
Active, announced, or legacy with no imminent date. Legacy models are superseded but still served.
| Model | State | Retirement | Replacement |
|---|---|---|---|
| gpt-4o-mini-transcribe (2025-12-15) | active | 2027-06-15 · in 225 days | — |
| gpt-4o-mini-tts (2025-12-15) | active | 2027-06-15 · in 225 days | — |
| gpt-5 (2025-08-07) | active | 2027-02-09 · in 99 days | — |
| gpt-5-codex (2025-09-15) | active | 2027-03-17 · in 135 days | — |
| gpt-5-mini (2025-08-07) | active | 2027-02-09 · in 99 days | — |
| gpt-5-nano (2025-08-07) | active | 2027-02-09 · in 99 days | — |
| gpt-5-pro (2025-10-06) | active | 2027-04-07 · in 156 days | — |
| gpt-5.1 (2025-11-13) | active | 2027-05-15 · in 194 days | — |
| gpt-5.1-codex (2025-11-13) | active | 2027-05-15 · in 194 days | — |
| gpt-5.1-codex-max (2025-12-04) | active | 2027-05-18 · in 197 days | — |
| gpt-5.1-codex-mini (2025-11-13) | active | 2027-05-15 · in 194 days | — |
| gpt-5.2 (2025-12-11) | active | 2027-06-08 · in 218 days | — |
| gpt-5.2-codex (2026-01-14) | active | 2027-07-13 · in 253 days | — |
| gpt-5.3-codex (2026-02-24) | active | 2027-08-24 · in 295 days | — |
| gpt-5.4 (2026-03-05) | active | 2027-09-02 · in 304 days | — |
| gpt-5.4-mini (2026-03-17) | active | 2027-09-21 · in 323 days | — |
| gpt-5.4-nano (2026-03-17) | active | 2027-09-21 · in 323 days | — |
| gpt-5.4-pro (2026-03-05) | active | 2027-09-07 · in 309 days | — |
| gpt-5.5 (2026-04-24) | active | 2027-10-26 · in 358 days | — |
| gpt-5.6-luna (2026-07-09) | active | 2028-01-11 · in 435 days | — |
| gpt-5.6-sol (2026-07-09) | active | 2028-01-11 · in 435 days | — |
| gpt-5.6-terra (2026-07-09) | active | 2028-01-11 · in 435 days | — |
| gpt-audio (2025-08-28) | active | 2027-03-02 · in 120 days | — |
| gpt-audio-1.5 (2026-02-23) | active | 2027-08-24 · in 295 days | — |
| gpt-audio-mini (2025-12-15) | active | 2027-06-15 · in 225 days | — |
| gpt-chat-latest (2026-10-07) | active | 2027-05-18 · in 197 days | — |
| gpt-image-1-mini (2025-10-06) | active | 2027-04-07 · in 156 days | — |
| gpt-image-2 (2026-04-21) | active | 2027-10-21 · in 353 days | — |
| gpt-image-2.5-flare (2026-09-09) | active | 2027-09-09 · in 311 days | — |
| gpt-image-2.5-sunburst (2026-09-09) | active | 2027-09-09 · in 311 days | — |
| gpt-realtime (2025-08-28) | active | 2027-03-02 · in 120 days | — |
| gpt-realtime-1.5 (2026-02-23) | active | 2027-08-24 · in 295 days | — |
| gpt-realtime-2.1 (2026-07-07) | active | 2027-06-25 · in 235 days | — |
| gpt-realtime-2.1-mini (2026-07-07) | active | 2027-06-25 · in 235 days | — |
| text-embedding-3-large (1) | active | 2028-02-09 · in 464 days | — |
| text-embedding-3-small (1) | active | 2028-02-09 · in 464 days | — |
| text-embedding-ada-002 (1) | active | 2028-02-09 · in 464 days | — |
| text-embedding-ada-002 (2) | active | 2028-02-09 · in 464 days | — |
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.
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.