What changed
Time to bail on Azure OpenAI gpt-5 models, version 2025-08-07? Act. You can stay. Version 2025-08-07 of these models retires February 9, 2027. Plan the move now.
On our scale this is Act: change a setting or plan before the date. You can stay.
Microsoft retires gpt-5, gpt-5-mini and gpt-5-nano in Azure OpenAI on February 9, 2027. This is version 2025-08-07. No replacement is listed yet.
Here are the facts we checked:
- Retirement date: February 9, 2027 (Microsoft)
- Models and version: gpt-5, gpt-5-mini and gpt-5-nano, version 2025-08-07 (Microsoft)
- Replacement: None listed yet (Microsoft)
- When Microsoft names a replacement: About 90 to 120 days before retirement (Microsoft)
- On the OpenAI API itself: The same 2025-08-07 snapshots shut down December 11, 2026 (OpenAI)
- 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 February 9, 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 February 9, 2027; some move to a new model on their own.
The date to remember is February 9, 2027. Make the change before then.
What to do before February 9
- List your gpt-5 deployments. Check each one: model, version, deployment type and upgrade setting.
- Plan the move for provisioned ones. Provisioned and NoAutoUpgrade deployments are not moved for you. Watch the schedule for the named replacement.
- 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