Azure Foundry model retirement schedule

WORTH KNOWING MODELDEPRECATION Azure Foundry model retirement schedule · 2026-09-23 21:12 UTC

gpt-realtime-2 retirement date removed, gpt-realtime-2.1 added

DOCheck your deployment configs for gpt-realtime-2 references.

WHAT CHANGEDThe retirement date of 2026-08-31 was removed from gpt-realtime-2 (preview model launched 2026-05-06). A new model version gpt-realtime-2.1 was added to the schedule with a launch date of 2026-07-07 and no stated retirement date.

WHY IT MATTERSIf you are using gpt-realtime-2 and planned migration work around the August 31 deadline, that deadline no longer exists. The model remains in preview with no published end-of-life, which means the retirement timeline is now undefined.

WHAT TO DOCheck your deployment configs for gpt-realtime-2 references. If you scheduled migration work for before August 31, deprioritize it until a new retirement date is published or evaluate whether to migrate to gpt-realtime-2.1 based on your release criteria for preview models.

CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 gpt-realtime-2
 2026-05-06
 Preview
-2026-08-31
 —
+gpt-realtime-2.1
 
 gpt-realtime-2.1
 2026-07-07
@@
 Suggest a fix?
 
 Last updated on
-2026-09-14
+2026-09-21

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.92, needed 0.45
triage reasoning	New model version added to retirement schedule; prior version's end-of-preview date removed.
signals	model version added (gpt-realtime-2.1) · retirement date removed from gpt-realtime-2 · new model row inserted into retirement schedule · date change in footer (2026-09-14 → 2026-09-21)
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

WORTH KNOWING MODEL Azure Foundry model retirement schedule · 2026-09-21 23:43 UTC

gpt-realtime-2.1 and mini moved to GA on 2026-07-07

DOIf you are using either model in production, verify your deployment is receiving GA-level support and SLA coverage.

WHAT CHANGEDgpt-realtime-2.1 and gpt-realtime-2.1-mini changed status from Preview to GA effective 2026-07-07. Both models have a retirement date of 2027-06-25.

WHY IT MATTERSGA status means these models now carry production SLA guarantees and support commitments that Preview versions do not. Any production workloads currently using these models are now covered under standard Azure support terms.

WHAT TO DOIf you are using either model in production, verify your deployment is receiving GA-level support and SLA coverage. If you were blocking production use pending GA status, that gate is now cleared.

CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 
 gpt-realtime-2.1
 2026-07-07
-Preview
+GA
 2027-06-25
 —
 
 gpt-realtime-2.1-mini
 2026-07-07
-Preview
+GA
 2027-06-25
 —

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.92, needed 0.45
triage reasoning	Preview-to-GA transition signals production-ready models with different support commitments and retirement timelines.
signals	model status change from Preview to GA · two models affected · GA status affects support SLA and production readiness
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

WORTH KNOWING DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-09-21 23:43 UTC

gpt-4.1-nano retirement extended to 2027-04-14

DOCheck your deployment manifests and infrastructure-as-code for references to gpt-4.1-nano.

WHAT CHANGEDThe retirement date for gpt-4.1-nano moved from 2026-10-14 to 2027-04-14, a six-month extension. The model entered Legacy status on 2025-04-14.

WHY IT MATTERSIf you are running gpt-4.1-nano in production, you now have until mid-April 2027 to complete migration instead of mid-October 2026. This changes the timeline for any scheduled replacement work.

WHAT TO DOCheck your deployment manifests and infrastructure-as-code for references to gpt-4.1-nano. If found, update your migration plan to reflect the new 2027-04-14 deadline and communicate the revised timeline to stakeholders.

CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 gpt-4.1-nano
 2025-04-14
 Legacy
-2026-10-14
+2027-04-14
 —
 
 gpt-4o

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	Retirement deadline for gpt-4.1-nano moved from Oct 2026 to Apr 2027, affecting deployment planning.
signals	retirement date changed · sunset date extended by 6 months · model lifecycle impact
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

ACTION NEEDED DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-09-21 23:42 UTC

Azure retires gpt-4.1-nano and gpt-image-1.5 six months earlier than announced

DOAudit Azure deployments for gpt-4.1-nano and gpt-image-1.5.

WHAT CHANGEDgpt-4.1-nano retirement moved from 2027-04-14 to 2026-10-14. gpt-image-1.5 retirement moved from 2027-06-16 to 2026-12-16. Both dates accelerated by six months.

WHY IT MATTERSAny deployments using these models will stop working on the new dates. Six months less migration runway means work scheduled for Q2 2027 must now complete by Q4 2026.

WHAT TO DOAudit Azure deployments for gpt-4.1-nano and gpt-image-1.5. If found, schedule migration to successor models before 2026-10-14 and 2026-12-16 respectively.

CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 gpt-4.1-nano
 2025-04-14
 Legacy
-2027-04-14
+2026-10-14
 —
 
 gpt-4o
@@
 gpt-image-1.5
 2025-12-16
 GA
-2027-06-16
+2026-12-16
 —
 
 gpt-image-2
@@
 Cohere-command-a-plus-05-2026
 1
 Preview
-2026-10-13
-—
+2026-10-16
+coherelabs-command-a-plus-05-2026-fp81, coherelabs-command-a-plus-05-2026-bf161, coherelabs-command-a-plus-05-2026-w4a41
 
 embed-v-4-0
 1
@@
 —
 —
 
+1 Available through the Hugging Face collection, for managed compute deployment.
+
 DeepSeek
 
 Model
@@
 Suggest a fix?
 
 Last updated on
-2026-09-02
+2026-09-14

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	Two model retirement dates moved forward by 6 months each, requiring engineering action.
signals	retirement date accelerated: gpt-4.1-nano from 2027-04-14 to 2026-10-14 (6 months earlier) · retirement date accelerated: gpt-image-1.5 from 2027-06-16 to 2026-12-16 (6 months earlier) · preview model date changed: Cohere-command-a-plus-05-2026 from 2026-10-13 to 2026-10-16 · model variant identifiers added for Cohere model · new deployment option noted for embed-v-4-0
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

ACTION NEEDED DEPRECATIONMODELAPI Azure Foundry model retirement schedule · 2026-09-12 03:31 UTC

Azure o1/o3 family retirement consolidated to 2026-11-19

DOGrep your codebase for model identifiers o1-pro, o3, o3-deep-research, o3-pro, o3-mini, o4-mini.

WHAT CHANGEDo1-pro, o3, o3-deep-research, and o3-pro moved from GA to Deprecated status. All o1/o3 models now retire 2026-11-19 (previously scattered between 2026-10-01 and 2026-12-26). o3-mini and o4-mini successor changed from o4-mini to gpt-5.6-terra. Fine-tuning retirement for o4-mini shifted from 2027-04-16 to 2027-05-19.

WHY IT MATTERSIf you are running o1-pro, o3, o3-deep-research, or o3-pro in production, they are now deprecated with 9 weeks until retirement. The consolidated sunset date means you cannot stagger migrations. The successor model change means existing migration plans targeting o4-mini must be rewritten to target gpt-5.6-terra or gpt-5.6-sol.

WHAT TO DOGrep your codebase for model identifiers o1-pro, o3, o3-deep-research, o3-pro, o3-mini, o4-mini. If any are in use, schedule migration to gpt-5.6-sol (for o1/o3 reasoning models) or gpt-5.6-terra (for o3-mini/o4-mini) before 2026-11-19. If you have fine-tuned o4-mini models, note the new training retirement date of 2027-05-19.

CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 o1
 2024-12-17
 Deprecated
-2026-10-21
+2026-11-19
 gpt-5.6-sol
 
 o1-pro
 2025-03-19
-GA
-2026-10-21
+Deprecated
+2026-11-19
 gpt-5.6-sol
 
 o3
 2025-04-16
-GA
-2026-10-21
+Deprecated
+2026-11-19
 gpt-5.6-sol
 
 o3-deep-research
 2025-06-26
-GA
-2026-12-26
-—
+Deprecated
+2026-11-19
+gpt-5.6-sol
 
 o3-mini
 2025-01-31
 Deprecated
-2026-10-01
-o4-mini
+2026-11-19
+gpt-5.6-terra
 
 o3-pro
 2025-06-10
-GA
-2026-12-17
-—
+Deprecated
+2026-11-19
+gpt-5.6-sol
 
 o4-mini
 2025-04-16
 Deprecated
-2026-10-16
-—
+2026-11-19
+gpt-5.6-terra
 
 sora-2
 2025-10-06
@@
 
 o4-mini
 2025-04-16
-No earlier than 2027-04-161
-2027-10-16
+No earlier than 2027-05-191
+2027-11-19
 
 1 For existing customers only. Otherwise, training retirement occurs at base model retirement.

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.98, needed 0.45
triage reasoning	Multiple model deprecations accelerated and status changes from GA to Deprecated affect deployment planning.
signals	multiple model deprecation dates shifted forward by ~30 days · models changed from GA to Deprecated status · o1-pro, o3, o3-deep-research, o3-pro transitioned from GA to Deprecated · successor model assignments changed (o3-mini now maps to gpt-5.6-terra instead of o4-mini) · training retirement dates shifted (2027-04-16 → 2027-05-19, 2027-10-16 → 2027-11-19) · consolidation: multiple models now share single sunset date 2026-11-19
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

WORTH KNOWING MODELDEPRECATION Azure Foundry model retirement schedule · 2026-09-10 20:30 UTC

Two image models added to retirement schedule, sunset 9 September 2027

DOCheck your image generation endpoints for references to gpt-image-2.5-flare or gpt-image-2.5-sunburst.

WHAT CHANGEDgpt-image-2.5-flare and gpt-image-2.5-sunburst reached GA on 9 September 2026 and are scheduled for retirement on 9 September 2027. Both models now appear on the Azure Foundry model retirement schedule.

WHY IT MATTERSIf you adopt either model after GA, you have exactly one year before forced migration. The retirement date is fixed at announcement, which is unusually short for a GA model lifecycle.

WHAT TO DOCheck your image generation endpoints for references to gpt-image-2.5-flare or gpt-image-2.5-sunburst. If you are evaluating these models, factor the 9 September 2027 cutoff into your adoption decision now.

CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 2027-10-21
 —
 
+gpt-image-2.5-flare
+2026-09-09
+GA
+2027-09-09
+—
+
+gpt-image-2.5-sunburst
+2026-09-09
+GA
+2027-09-09
+—
+
 gpt-realtime
 2025-08-28
 GA

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	New models with defined sunset dates added to retirement schedule; engineering teams must track these timelines.
signals	two new models added to retirement schedule · future sunset dates specified (2027-09-09) · GA status indicates production-ready models · retirement schedule is the core tracked artifact
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

WORTH KNOWING DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-09-03 03:20 UTC

Claude Fable 5.1 retires 5 December 2027

DOGrep your codebase and infrastructure-as-code for 'claude-fable-5-1' references.

WHAT CHANGEDAzure Foundry added a retirement date of 2027-12-05 for the claude-fable-5-1 model. The model is currently in Preview status.

WHY IT MATTERSAny code or configuration using claude-fable-5-1 by name will stop working after that date. Preview models typically have shorter lifespans than GA releases, and 15 months is the notice window.

WHAT TO DOGrep your codebase and infrastructure-as-code for 'claude-fable-5-1' references. If found, add a calendar reminder for Q3 2027 to migrate to whatever replaces it, or pin to claude-fable-5 if that model remains supported.

CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 claude-fable-5-1
 1
 Preview
+2027-12-05
 —
-—
 
 claude-fable-5
 1
@@
 Suggest a fix?
 
 Last updated on
-2026-08-27
+2026-09-02

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.92, needed 0.45
triage reasoning	New future date (2027-12-05) added to claude-fable-5-1 entry signals model retirement or sunset event.
signals	future date added to model entry · date format suggests retirement/sunset deadline · model lifecycle change · last-updated timestamp changed
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

ACTION NEEDED MODELDEPRECATION Azure Foundry model retirement schedule · 2026-09-01 20:40 UTC

claude-opus-4-1 retired August 5, 2026; upgrade path to claude-opus-5

DOGrep your codebase and infrastructure-as-code for 'claude-opus-4-1' and replace with 'claude-opus-5'.

WHAT CHANGEDclaude-opus-4-1 marked Retired with effective date 2026-08-05. claude-opus-5 added to supported models list. Two new preview models added: claude-fable-5-1 and claude-mythos-5-1.

WHY IT MATTERSAny code or configuration explicitly requesting claude-opus-4-1 will fail after August 5, 2026. If you are using version pinning or explicit model identifiers rather than latest-stable aliases, calls will return errors once the retirement date passes.

WHAT TO DOGrep your codebase and infrastructure-as-code for 'claude-opus-4-1' and replace with 'claude-opus-5'. Test the replacement in staging before August 5, 2026.

CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 2026-10-19
 —
 
+claude-opus-4-1
+—
+Retired
+2026-08-05
+claude-opus-5
+
 claude-haiku-4-5
 1
 GA
@@
 2026-10-19
 —
 
+claude-fable-5-1
+1
+Preview
+—
+—
+
 claude-fable-5
 1
 Preview
 2027-12-05
 —
 
+claude-mythos-5-1
+1
+Preview
+—
+—
+
+claude-mythos-preview (gated research preview)
+—
+Preview
+2027-04-02
+—
+
 Cohere
 
 Model

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	Retirement date for existing model and new model versions affect deployment planning and API compatibility.
signals	model retirement date added (claude-opus-4-1, 2026-08-05) · new model versions added to supported list (claude-opus-5, claude-fable-5-1, claude-mythos-5-1) · model status changes (Retired, Preview) · future sunset dates present
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

ACTION NEEDED DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-08-29 05:59 UTC

Three MAI-Image-2.5 variants added to retirement schedule, sunset October 2026

DOGrep your codebase for 'MAI-Image-2.5', 'MAI-Image-2.5-Flash', and 'MAI-Image-2.5-Pro'.

WHAT CHANGEDMAI-Image-2.5, MAI-Image-2.5-Flash, and MAI-Image-2.5-Pro added to Azure Foundry retirement schedule. All three entered Preview on June 2 or June 19, 2026, and will be retired October 1, 2026. MAI-Image-2e status changed from Preview to Retired.

WHY IT MATTERSIf you are using or planning to use any MAI-Image-2.5 variant, you have a four-month window from preview to retirement. Code written against these models will break on October 1, 2026 unless migrated to a successor model.

WHAT TO DOGrep your codebase for 'MAI-Image-2.5', 'MAI-Image-2.5-Flash', and 'MAI-Image-2.5-Pro'. If found, schedule migration work to complete before October 1, 2026. If not using these models, no action required.

CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 2027-05-20
 —
 
+MAI-Image-2.5-Pro
+2026-06-19
+Preview
+2026-10-01
+—
+
+MAI-Image-2.5-Flash
+2026-06-02
+Preview
+2026-10-01
+—
+
+MAI-Image-2.5
+2026-06-02
+Preview
+2026-10-01
+—
+
 MAI-Image-2e
 2026-04-09
-Preview
+Retired
 2026-08-15
 MAI-Image-2.5-Flash

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	New models added with concrete deprecation and retirement dates; existing model status changed to Retired.
signals	new models added to retirement schedule · future deprecation dates (2026-06-02, 2026-06-19) · future sunset dates (2026-10-01) · model status change: Preview → Retired · three new model variants with defined lifecycle windows
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

ACTION NEEDED MODELAPIDEPRECATION Azure Foundry model retirement schedule · 2026-08-28 21:46 UTC

Azure Foundry splits Claude models into two hosting versions with new retirement dates

DOAudit your model identifiers to confirm which version (1 or 2) you are using.

WHAT CHANGEDAzure Foundry now offers Claude models in two versions: Version 1 (Anthropic infrastructure) and Version 2 (Azure infrastructure). Multiple models moved from Preview to GA status. claude-opus-4-1 was removed from the schedule (previously marked Retired 2026-08-05). New model claude-fable-5 added with retirement date 2027-12-05. claude-haiku-4-5 Preview variant removed; GA variants now exist for both Version 1 and Version 2, both retiring 2026-10-19.

WHY IT MATTERSIf you are calling Claude models by name without specifying version, your requests may now route to different infrastructure (Anthropic vs Azure) with potentially different latency, availability, or billing characteristics. The removal of claude-opus-4-1 from the schedule means any code still referencing it is calling a model that no longer appears in the official retirement timeline.

WHAT TO DOAudit your model identifiers to confirm which version (1 or 2) you are using. If you are calling claude-opus-4-1, verify whether it still responds or migrate to claude-opus-5 (GA, retires 2027-07-08). If you rely on claude-haiku-4-5, confirm whether you are on Version 1 or 2 and note the 2026-10-19 retirement date for both.

CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 
 Anthropic
 
+Microsoft Foundry offers Claude models in two versions:
+
+Version 1: Hosted on Anthropic infrastructure
+
+Version 2: Hosted on Azure
+
 Model
 Version
 Lifecycle
 Retirement date
 Replacement
 
-claude-haiku-4-5
+claude-sonnet-5
+2
+GA
+2027-06-30
 —
-Preview
-2026-10-19
+
+claude-sonnet-5
+1
+GA
+2027-06-30
 —
 
-claude-mythos-preview (gated research preview)
+claude-sonnet-4-6
+1
+GA
+2027-02-10
 —
-Preview
-2027-04-02
+
+claude-sonnet-4-5
+1
+GA
+2026-10-19
 —
 
-claude-opus-4-1
+claude-opus-5
+2
+GA
+2027-07-08
 —
-Retired
-2026-08-05
+
 claude-opus-5
+1
+GA
+2027-07-08
+—
 
-claude-opus-4-5
+claude-opus-4-8
+2
+GA
+2027-09-01
 —
-Preview
-2026-10-19
-—
 
-claude-opus-4-6
+claude-opus-4-8
+1
+GA
+2027-09-01
 —
-Preview
-2027-02-02
-—
 
 claude-opus-4-7
-—
-Preview
+1
+GA
 2027-04-06
 —
 
-claude-sonnet-4-5
+claude-opus-4-6
+1
+GA
+2027-02-02
 —
-Preview
+
+claude-opus-4-5
+1
+GA
 2026-10-19
 —
 
-claude-sonnet-4-6
+claude-haiku-4-5
+1
+GA
+2026-10-19
 —
+
+claude-haiku-4-5
+2
+GA
+2026-10-19
+—
+
+claude-fable-5
+1
 Preview
-2027-02-10
+2027-12-05
 —
 
 Cohere
@@
 Suggest a fix?
 
 Last updated on
-2026-08-26
+2026-08-27

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	Retirement dates shifted, model availability split by hosting, lifecycle statuses upgraded, breaking changes to model roster.
signals	multiple retirement dates changed · model lifecycle statuses changed (Preview→GA) · new model versions introduced (Version 1 vs Version 2 hosting split) · models removed from list (claude-haiku-4-5 Preview variant gone) · new model added (claude-fable-5) · retirement date accelerated (claude-opus-4-1 from 2026-08-05 now absent) · structural change: dual-version hosting model introduced
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

WORTH KNOWING DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-08-25 06:49 UTC

Sora-2 preview retirement delayed one month to 15 October 2026

DOCheck your migration schedule for sora-2.

WHAT CHANGEDThe retirement date for the sora-2 preview model moved from 15 September 2026 to 15 October 2026.

WHY IT MATTERSIf you planned migration work around the September deadline, you now have four additional weeks. If you already migrated, the extension changes nothing.

WHAT TO DOCheck your migration schedule for sora-2. If you have not started and the September date was tight, you can defer by up to four weeks. If you already migrated or the date was not a constraint, no action needed.

CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 sora-2
 2025-12-08
 Preview
-2026-09-15
+2026-10-15
 —
 
 text-embedding-3-large

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	Sora-2 preview retirement date pushed from September to October 2026. Teams relying on this model need to know the new deadline.
signals	future date changed · retirement/sunset date extended by one month · model lifecycle milestone altered
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

WORTH KNOWING DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-08-20 01:15 UTC

gpt-4.1-nano retirement extended six months to 2027-04-14

DOCheck your migration backlog for gpt-4.1-nano work scheduled before 2027-04-14.

WHAT CHANGEDAzure Foundry moved gpt-4.1-nano retirement from 2026-10-14 to 2027-04-14. The model's status label changed from 'Deprecated' to 'Legacy' on 2025-04-14. Three other models (gpt-4.1, gpt-4.1-mini, gpt-4o) also changed to 'Legacy' status with 2027-04-14 retirement dates.

WHY IT MATTERSIf you planned migration work around the October 2026 deadline, you now have six additional months. Teams that deprioritized gpt-4.1-nano migration because of the tight timeline can reschedule without urgency.

WHAT TO DOCheck your migration backlog for gpt-4.1-nano work scheduled before 2027-04-14. If you deferred it due to the October deadline, update the target date and reprioritize against other work.

CONFIDENCE 95% 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
-Deprecated
+Legacy
 2027-04-14
 —
 
 gpt-4.1-mini
 2025-04-14
-Deprecated
+Legacy
 2027-04-14
 —
 
 gpt-4.1-nano
 2025-04-14
-Deprecated
-2026-10-14
+Legacy
+2027-04-14
 —
 
 gpt-4o
@@
 
 gpt-4o
 2024-11-20
-Deprecated
+Legacy
 2027-04-14
 gpt-5.1

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.92, needed 0.45
triage reasoning	Model retirement dates extended and status reclassified; affects deployment planning and migration timelines.
signals	status label changed from 'Deprecated' to 'Legacy' · gpt-4.1-nano retirement date extended from 2026-10-14 to 2027-04-14 · multiple models affected · sunset dates are future dates paired with retirement timeline
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

WORTH KNOWING MODELDEPRECATION Azure Foundry model retirement schedule · 2026-08-19 18:36 UTC

DeepSeek-V4-Flash-0731 preview ends 2026-12-03, GA 2026-07-31

DOCheck if any code or configs reference DeepSeek-V4-Flash-0731 in preview.

WHAT CHANGEDAzure added DeepSeek-V4-Flash-0731 to the retirement schedule. The model enters GA on 2026-07-31 and preview access ends on 2026-12-03.

WHY IT MATTERSIf you are testing this model in preview, you have until 2026-12-03 to migrate to the GA version or switch models. Preview endpoints will stop working after that date.

WHAT TO DOCheck if any code or configs reference DeepSeek-V4-Flash-0731 in preview. If so, schedule migration to the GA version before 2026-12-03.

CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 2026-04-23
 GA
 2028-02-20
+DeepSeek-V4-Flash-0731
+
+DeepSeek-V4-Flash-0731
+2026-07-31
+Preview
+2026-12-03
 —
 
 DeepSeek-V4-Pro
@@
 Suggest a fix?
 
 Last updated on
-2026-08-17
+2026-08-19

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	New model added to public retirement schedule with defined preview and GA dates.
signals	new model added to retirement schedule · model name: DeepSeek-V4-Flash-0731 · preview end date: 2026-12-03 · GA date: 2026-07-31 · retirement schedule table expanded
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)

ACTION NEEDED DEPRECATIONMODELAPI Azure Foundry model retirement schedule · 2026-08-18 01:15 UTC

Four Azure Foundry models retired, MAI-Transcribe-1 retiring 15 September 2026

DOGrep your codebase for 'DeepSeek-R1', 'MAI-Image-2', 'Stable-Diffusion-3.5-Large', 'Stable-Image-Core', 'Stable-Image-Ultra', and 'MAI-Transcribe-1'.

WHAT CHANGEDDeepSeek-R1, MAI-Image-2, Stable-Diffusion-3.5-Large, Stable-Image-Core, and Stable-Image-Ultra moved from Legacy/Preview/Deprecated to Retired status between 31 July and 15 August 2026. MAI-Transcribe-1 added to retirement schedule with cutoff date 15 September 2026. MAI-Transcribe-1.5 added as successor model.

WHY IT MATTERSRetired models are no longer callable via API. Any code still referencing DeepSeek-R1, MAI-Image-2, or the three Stable models will fail. MAI-Transcribe-1 stops working in 28 days.

WHAT TO DOGrep your codebase for 'DeepSeek-R1', 'MAI-Image-2', 'Stable-Diffusion-3.5-Large', 'Stable-Image-Core', 'Stable-Image-Ultra', and 'MAI-Transcribe-1'. Remove or replace references before 15 September 2026 for MAI-Transcribe-1; the other five are already dead.

CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5

Show the reasoning — raw diff, triage verdict, confidence

RAW DIFF

 
 DeepSeek-R1
 1
-Legacy
+Retired
 2026-08-13
 DeepSeek-V4-Pro
 
@@
 
 MAI-Image-2
 2026-02-20
-Preview
+Retired
 2026-08-15
 MAI-Image-2.5
 
+MAI-Transcribe-1
+2026-01-23
+Preview
+2026-09-15
+MAI-Transcribe-1.5
+
 Mistral AI
 
 Model
@@
 
 Stable-Diffusion-3.5-Large
 1
-Deprecated
+Retired
 2026-07-31
 —
 
 Stable-Image-Core
 1
-Deprecated
+Retired
 2026-07-31
 —
 
 Stable-Image-Ultra
 1
-Deprecated
+Retired
 2026-07-31
 —
 
@@
 Suggest a fix?
 
 Last updated on
-2026-07-24
+2026-08-17

HOW IT WAS JUDGED

triage verdict	MATERIAL at 0.95, needed 0.45
triage reasoning	Multiple models moved to Retired status with concrete sunset dates. New models added to retirement schedule.
signals	status label changes from Legacy/Preview/Deprecated to Retired · retirement dates present (2026-07-31, 2026-08-13, 2026-08-15, 2026-09-15) · new model entries added (MAI-Transcribe-1, MAI-Transcribe-1.5) · multiple models transitioned to final retirement state · documentation timestamp updated
suppression	—
triage model	anthropic/claude-haiku-4.5 ($0.00000)
writer model	anthropic/claude-sonnet-4.5 ($0.00000)