Azure OpenAI has officially announced the retirement of GPT‑4o base model versions 2024‑05‑13 and 2024‑08‑06. These versions apply to base (non‑fine‑tuned) deployments, including those consumed through the Assistants API (Preview). After the retirement date, these GPT‑4o versions will no longer be deployable, callable, or operable in Azure OpenAI.
Retirement timeline and effective dates:
The final retirement date for GPT‑4o (2024‑05‑13 and 2024‑08‑06) is 31 March 2026. Azure subscriptions received formal notifications starting March 2026. From 31 March 2026 onward, any Assistant, chat, or workload pointing to these versions will fail unless migrated.
Fine‑tuning impact As of 31 March 2026, new fine‑tuning on GPT‑4o (2024‑05‑13 / 2024‑08‑06) is no longer allowed. However, existing fine‑tuned GPT‑4o deployments are allowed to continue running for an additional one‑year grace period (to help customers avoid sudden production outages). Even during this grace period, Microsoft strongly recommends migrating as early as possible.
Official replacement model for Assistants API:
The official replacement model for GPT‑4o in the Assistants API (Preview) is gpt‑5.1 version 2025‑11‑13. This model is the supported successor for agent‑style, tool‑using, threaded Assistant workloads, and it fully replaces GPT‑4o for this use case.
Assistants API compatibility gpt‑5.1 (2025‑11‑13) is fully supported by the Azure OpenAI Assistants API (Preview). It supports:
- Threaded conversations
- Tool and function calling
- File retrieval / vector context
- System + developer + user instruction layering
No migration away from the Assistants API itself is required—only the model deployment changes.
Upgrade behavior and requirements:
Azure does not auto‑upgrade GPT‑4o Assistant deployments to GPT‑5.1 by default. Customers must manually create a new deployment using:
- Model:
gpt‑5.1 - Version:
2025‑11‑13
You must then update your Assistant configuration or deployment reference to point to the new deployment. No Assistants API code changes are normally required.
Behavioral differences to expect When migrating from GPT‑4o to GPT‑5.1, expect stricter system‑message enforcement, more deterministic tool‑calling, and slightly different reasoning and verbosity patterns. Testing is strongly recommended for:
- Tool/function schemas
- JSON‑constrained outputs
- RAG and retrieval flows
These are behavior changes, not breaking API changes
Note:After 31 March 2026, GPT‑4o (2024‑05‑13 / 2024‑08‑06) deployments will stop working completely. Assistants referencing these deployments will return errors, and new fine‑tuning will remain blocked.
Recommended migration steps
- Create a new deployment using
gpt‑5.1 (2025‑11‑13) - Update Assistants to reference the new deployment
- Validate tool calls, retrieval, streaming, and system instructions
- Decommission GPT‑4o deployments before 31 March 2026
Reference:
I Hope this helps. Do let me know if you have any further queries.
If this answers your query, please do click Accept Answer and Yes for was this answer helpful.
Thank you!