timetobail
My stack

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

Time to bail on Azure OpenAI o1, o3, o3-mini and o4-mini deployments?

Time to Bail · Boarding pass

FromAzure OpenAI o1, o3, o3-mini and o4-mini deployments
ToYour pick

Act. You can stay.

These models retire November 19, 2026. gpt-4o 2024-05-13 follows on December 9, 2026.[1]

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

Gate closes
Retirement date
Time left
34days
Status
Act

Azure OpenAI o1, o3, o3-mini and o4-mini retire November 19, 2026

Microsoft retires o1, o3, o3-mini and o4-mini in Azure OpenAI on November 19, 2026, and gpt-4o version 2024-05-13 on December 9, 2026. Some deployments are upgraded for you; others stop working.

What to do before November 19

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

  1. List your deployments

    Check each Azure OpenAI deployment: model, version and deployment type.

  2. Move provisioned and pinned ones yourself

    Provisioned deployments and those set to never upgrade are not moved for you. Deploy gpt-5.6-sol or gpt-5.6-terra.

  3. Test the new model

    Even when Microsoft upgrades a deployment, run your prompts on the new model and check the output.

Facts we checked

Facts and their sources
Retirement dateNovember 19, 2026[1]
Models and versionso1 (2024-12-17), o3 (2025-04-16), o3-mini (2025-01-31), o4-mini (2025-04-16)[1]
Replacementso1 and o3 → gpt-5.6-sol; o3-mini and o4-mini → gpt-5.6-terra[1]
Also retiringgpt-4o version 2024-05-13 on December 9, 2026 → gpt-5.6-sol[1]
Standard, Global Standard and Data Zone StandardMicrosoft upgrades them automatically when a version retires[2]
Provisioned deploymentsNot upgraded automatically[2]
Deployments set to never upgradeStop working at retirement[2]
Deployments of these modelsRetire November 19, 2026; some move to a new model on their own[1]

Sources

Check it yourself. Every fact above links here.

  1. Azure OpenAI model retirement schedule Microsoft · primary · checked Oct 13
  2. Foundry Models lifecycle and support policy Microsoft · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Azure OpenAI o1, o3, o3-mini and o4-mini deployments? Act. You can stay. These models retire November 19, 2026. gpt-4o 2024-05-13 follows on December 9, 2026.

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

Microsoft retires o1, o3, o3-mini and o4-mini in Azure OpenAI on November 19, 2026, and gpt-4o version 2024-05-13 on December 9, 2026. Some deployments are upgraded for you; others stop working.

Here are the facts we checked:

  • Retirement date: November 19, 2026 (Microsoft)
  • Models and versions: o1 (2024-12-17), o3 (2025-04-16), o3-mini (2025-01-31), o4-mini (2025-04-16) (Microsoft)
  • Replacements: o1 and o3 → gpt-5.6-sol; o3-mini and o4-mini → gpt-5.6-terra (Microsoft)
  • Also retiring: gpt-4o version 2024-05-13 on December 9, 2026 → gpt-5.6-sol (Microsoft)
  • Standard, Global Standard and Data Zone Standard: Microsoft upgrades them automatically when a version retires (Microsoft)
  • Provisioned deployments: Not upgraded automatically (Microsoft)
  • Deployments set to never upgrade: Stop working at retirement (Microsoft)
  • Deployments of these models: Retire November 19, 2026; 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 models: Retire November 19, 2026; some move to a new model on their own.

The date to remember is November 19, 2026. Make the change before then.

What to do before November 19

  1. List your deployments. Check each Azure OpenAI deployment: model, version and deployment type.
  2. Move provisioned and pinned ones yourself. Provisioned deployments and those set to never upgrade are not moved for you. Deploy gpt-5.6-sol or gpt-5.6-terra.
  3. Test the new model. Even when Microsoft upgrades a deployment, run your prompts on the new model and check the output.

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 o1, o3, o3-mini and o4-mini deployments 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