// AI Platform Drift

Azure gpt-4o retirement moved to 2026-12-09 with successor gpt-5.6-sol; gpt-4.1-nano retirement stands at 2027-04-14

Azure Foundry model retirement schedule · published 2026-09-24 05:30 UTC
CORRECTED 2026-10-18 15:04 UTC — Correction: The gpt-4.1-nano retirement date shown here (2026-10-14) is stale. The live Azure Foundry retirement schedule (https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule) now shows 2027-04-14, as RADAR re-captured in item 7403b787 on Oct 8, 2026. The source date has changed back and forth between these two values. The other facts here remain correct: gpt-4o retirement 2026-12-09 with successor gpt-5.6-sol.
Stood 585h 34m · cause source changed format · every correction ↗
ACTION NEEDED MIGRATE DEPRECATIONMODELAPI
WHAT CHANGEDOn the Azure Foundry model retirement schedule, gpt-4o retirement moved from 2026-10-01 to 2026-12-09 and its successor changed from gpt-5.1 to gpt-5.6-sol. gpt-4.1 and gpt-4.1-mini changed from Legacy to Deprecated and keep a 2027-04-14 retirement. gpt-4.1-nano's retirement date on the live schedule is 2027-04-14; the source has shown both 2026-10-14 and 2027-04-14 for it, and RADAR re-captured 2027-04-14 on 8 Oct 2026 (item 7403b787).
WHY IT MATTERSgpt-4o users have until 2026-12-09 and a named successor, gpt-5.6-sol. gpt-4.1-nano was not moved earlier on the current schedule, but its date has changed back and forth, so check the live schedule before planning around it.
WHAT TO DOGrep your codebase for 'gpt-4o' and 'gpt-4.1-nano' model references. If you use gpt-4o, plan the move to gpt-5.6-sol before 2026-12-09 and update any hardcoded successor references from gpt-5.1 to gpt-5.6-sol. If you use gpt-4.1-nano, confirm its date on the live Azure retirement schedule; it currently shows 2027-04-14.
Original text (as first published, superseded)
HEADLINEgpt-4.1-nano retirement accelerated by 6 months to October 2026
WHAT CHANGEDgpt-4.1-nano retirement date moved from 2027-04-14 to 2026-10-14. gpt-4.1 and gpt-4.1-mini status changed from Legacy to Deprecated but retain 2027-04-14 retirement. gpt-4o retirement extended from 2026-10-01 to 2026-12-09, successor changed from gpt-5.1 to gpt-5.6-sol.
WHY IT MATTERSAny code calling gpt-4.1-nano now has 6 fewer months to migrate. The accelerated timeline compresses testing and deployment windows for replacement models. Teams planning around the original April 2027 date must re-scope migration work.
WHAT TO DOGrep your codebase for 'gpt-4.1-nano' and 'gpt-4o' model references. If you use gpt-4.1-nano, schedule migration work to complete by 2026-10-14. If you use gpt-4o, update any hardcoded successor references from gpt-5.1 to gpt-5.6-sol.
ACT BY2026-10-14
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 
 gpt-4.1
 2025-04-14
-Legacy
+Deprecated
 2027-04-14
 —
 
 gpt-4.1-mini
 2025-04-14
-Legacy
+Deprecated
 2027-04-14
 —
 
 gpt-4.1-nano
 2025-04-14
-Legacy
-2027-04-14
+Deprecated
+2026-10-14
 —
 
 gpt-4o
 2024-05-13
 Deprecated
-2026-10-01
-gpt-5.1
+2026-12-09
+gpt-5.6-sol
 
 gpt-4o
 2024-08-06
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningDeprecation timelines and model retirement dates directly affect engineering planning and migration deadlines.
signalsstatus label changed from 'Legacy' to 'Deprecated' · retirement date accelerated for gpt-4.1-nano (2027-04-14 → 2026-10-14) · retirement date extended for gpt-4o (2026-10-01 → 2026-12-09) · model name changed in successor field (gpt-5.1 → gpt-5.6-sol)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)