timetobail
My stack

Azure OpenAI in Foundry Models · Forced move · Tracked since October 17, 2026 · Sources checked Oct 17

Time to bail on Azure OpenAI gpt-4o, gpt-4o-mini and gpt-4.1 family?

Time to Bail · Boarding pass

FromAzure OpenAI gpt-4o, gpt-4o-mini and gpt-4.1 family
ToYour pick

Act. You can stay.

These versions retire April 14, 2027. gpt-4o goes to gpt-5.1, which retires May 15, 2027.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Retirement date
Time left
178days
Status
Act

Azure OpenAI gpt-4o and gpt-4.1 models retire April 14, 2027

Microsoft retires gpt-4o (2024-08-06 and 2024-11-20), gpt-4o-mini, gpt-4.1, gpt-4.1-mini and gpt-4.1-nano in Azure OpenAI on April 14, 2027. gpt-4o moves to gpt-5.1; the others have no replacement listed yet.

Email me 7 days before Apr 14

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

What to do before April 14

Tick steps as you go. Your progress stays in this browser.

  1. List your deployments

    Check each gpt-4o, gpt-4o-mini and gpt-4.1 deployment: version, type and upgrade setting.

  2. Pick a target with a later date

    gpt-4o goes to gpt-5.1, but gpt-5.1 retires May 15, 2027. Compare newer models in the schedule.

  3. Move provisioned ones yourself

    Provisioned and NoAutoUpgrade deployments are not moved for you. Test, then switch traffic.

Email me 7 days before Apr 14

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
Retirement dateApril 14, 2027[1]
Models and versionsgpt-4o 2024-08-06 and 2024-11-20; gpt-4o-mini 2024-07-18; gpt-4.1, gpt-4.1-mini and gpt-4.1-nano 2025-04-14[1]
Replacement for gpt-4ogpt-5.1[1]
Replacement for gpt-4o-mini and the gpt-4.1 familyNone listed yet[1]
Careful: the gpt-4o pick retires soon aftergpt-5.1 (2025-11-13) retires May 15, 2027[1]
Older gpt-4o versiongpt-4o 2024-05-13 retires earlier, on December 9, 2026[1]
Fine-tuned deploymentsgpt-4o and gpt-4o-mini: October 1, 2027; gpt-4.1 family: October 14, 2027[1]
Standard, Global Standard and Data Zone StandardMicrosoft upgrades them automatically when a version retires, where a replacement is listed[2]
Provisioned deploymentsNot upgraded automatically[2]
Deployments set to NoAutoUpgradeStop working at retirement[2]
After retirementAll inference requests return 410 Gone[2]
Can you get more time?No. Microsoft says retirement dates are not extendable[2]
Deployments of these versionsRetire April 14, 2027; some move to a new model on their own[1]

After April 14, 2027 you will see

Requests to retired deployments of gpt-4o, gpt-4o-mini and the gpt-4.1 family that were not upgraded fail. Microsoft says inference returns an error.

410 Gone

Fix

  1. Deploy a newer model and point your app to it. For gpt-4o the schedule names gpt-5.1.
  2. Check dates with the Models API: read lifecycleStatus and deprecation.inference.

Source: [1] Model retirement schedule (Microsoft) · [2] Microsoft Foundry Models lifecycle and support policy (Microsoft)

Sources

Check it yourself. Every fact above links here.

  1. Model retirement schedule Microsoft · primary · checked Oct 17
  2. Microsoft Foundry Models lifecycle and support policy Microsoft · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on Azure OpenAI gpt-4o, gpt-4o-mini and gpt-4.1 family? Act. You can stay. These versions retire April 14, 2027. gpt-4o goes to gpt-5.1, which retires May 15, 2027.

On our scale this is Act: change a setting or plan before the date. You can stay.

Microsoft retires gpt-4o (2024-08-06 and 2024-11-20), gpt-4o-mini, gpt-4.1, gpt-4.1-mini and gpt-4.1-nano in Azure OpenAI on April 14, 2027. gpt-4o moves to gpt-5.1; the others have no replacement listed yet.

Here are the facts we checked:

  • Retirement date: April 14, 2027 (Microsoft)
  • Models and versions: gpt-4o 2024-08-06 and 2024-11-20; gpt-4o-mini 2024-07-18; gpt-4.1, gpt-4.1-mini and gpt-4.1-nano 2025-04-14 (Microsoft)
  • Replacement for gpt-4o: gpt-5.1 (Microsoft)
  • Replacement for gpt-4o-mini and the gpt-4.1 family: None listed yet (Microsoft)
  • Careful: the gpt-4o pick retires soon after: gpt-5.1 (2025-11-13) retires May 15, 2027 (Microsoft)
  • Older gpt-4o version: gpt-4o 2024-05-13 retires earlier, on December 9, 2026 (Microsoft)
  • Fine-tuned deployments: gpt-4o and gpt-4o-mini: October 1, 2027; gpt-4.1 family: October 14, 2027 (Microsoft)
  • Standard, Global Standard and Data Zone Standard: Microsoft upgrades them automatically when a version retires, where a replacement is listed (Microsoft)
  • Provisioned deployments: Not upgraded automatically (Microsoft)
  • Deployments set to NoAutoUpgrade: Stop working at retirement (Microsoft)
  • After retirement: All inference requests return 410 Gone (Microsoft)
  • Can you get more time?: No. Microsoft says retirement dates are not extendable (Microsoft)
  • Deployments of these versions: Retire April 14, 2027; some move to a new model on their own (Microsoft)

You can stay on Azure OpenAI in Foundry Models. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Microsoft is the main source for this page. Azure OpenAI in Foundry Models has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Deployments of these versions: Retire April 14, 2027; some move to a new model on their own.

The date to remember is April 14, 2027. Make the change before then.

What to do before April 14

  1. List your deployments. Check each gpt-4o, gpt-4o-mini and gpt-4.1 deployment: version, type and upgrade setting.
  2. Pick a target with a later date. gpt-4o goes to gpt-5.1, but gpt-5.1 retires May 15, 2027. Compare newer models in the schedule.
  3. Move provisioned ones yourself. Provisioned and NoAutoUpgrade deployments are not moved for you. Test, then switch traffic.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Azure OpenAI gpt-4o, gpt-4o-mini and gpt-4.1 family can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product