// AI Platform Drift

Azure Foundry extends four gpt-chat-latest preview retirement dates by 41 to 104 days

Azure Foundry model retirement schedule · published 2026-10-15 11:34 UTC
CORRECTED 2026-10-18 23:27 UTC — [CORRECTION · headline] Original: “extends gpt-chat-latest retirement dates 2–3 months” Fact: The four retirement dates moved by 104, 102, 54 and 41 days; none moved by 2 to 3 months. / [CORRECTION · WHY IT MATTERS] Original: “you now have 2–3 additional months” Fact: The added time is 41 to 104 days depending on the version. / Checked against the captured diff and the live retirement schedule on 2026-10-18.
Stood 83h 53m · cause arithmetic · every correction ↗
WORTH KNOWING VERIFY_ONLY MODELDEPRECATION
WHAT CHANGEDFour gpt-chat-latest preview versions had their retirement dates pushed back: 2026-05-05 now retires 2026-11-17 (was 2026-08-05), 2026-05-28 now retires 2026-12-08 (was 2026-08-28), 2026-06-24 now retires 2026-11-17 (was 2026-09-24), and 2026-08-06 now retires 2027-01-12 (was 2026-12-02). A new version 2026-10-07 was added with retirement date 2027-05-18.
WHY IT MATTERSIf you scheduled migration work based on the original retirement dates, you now have 41 to 104 more days, depending on the version: 104 days for 2026-05-05, 102 for 2026-05-28, 54 for 2026-06-24 and 41 for 2026-08-06. If you pinned to a specific preview version expecting it to retire in August or September, that version will remain available longer than planned.
WHAT TO DOCheck your deployment manifests and migration calendar for any gpt-chat-latest preview versions listed above. If you have work scheduled around the old retirement dates, adjust timelines to reflect the new dates or keep the original schedule to migrate sooner.
Original text (as first published, superseded)
HEADLINEAzure Foundry extends gpt-chat-latest retirement dates 2–3 months
WHY IT MATTERSIf you scheduled migration work based on the original retirement dates, you now have 2–3 additional months. If you pinned to a specific preview version expecting it to retire in August or September, that version will remain available longer than planned.
TRIAGE SIGNALsunset dates pushed 2–3 months later across existing entries
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-chat-latest
 2026-05-05
 Preview
-2026-08-05
+2026-11-17
 —
 
 gpt-chat-latest
 2026-05-28
 Preview
-2026-08-28
+2026-12-08
 —
 
 gpt-chat-latest
 2026-06-24
 Preview
-2026-09-24
+2026-11-17
 —
 
 gpt-chat-latest
 2026-08-06
 Preview
-2026-12-02
+2027-01-12
 —
 
+gpt-chat-latest
+2026-10-07
+Preview
+2027-05-18
+—
+
 gpt-image-1
 2025-04-15
 Preview
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, not independent arithmetic verification. A wrong figure in them has been corrected (config/corrected-text.yaml); the model's wording is kept, struck through, under the original text, and in data.json under original.triage.
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningModel retirement schedule changes directly affect deployment planning and migration timelines for dependent services.
signalsretirement dates extended on multiple model versions · new model version added with future retirement date · sunset dates pushed 41 to 104 days later across existing entries · gpt-chat-latest 2026-10-07 added with 2027-05-18 retirement
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)