Migrating off gpt-5-chat — retirement date and replacement
Source last checked: 2026-11-07.
Azure OpenAI is retiring gpt-5-chat on 2026-05-13. The provider’s documented replacement is gpt-chat-latest. This page is built from Azure OpenAI’s official deprecation notice and is rechecked weekly; the source link is below.
Past scheduled retirement. The published shutdown date has passed; this is a historical notice, not a live availability check.
When is gpt-5-chat being deprecated?
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| gpt-5-chat | Azure OpenAI | 2026-05-13 | gpt-chat-latest |
Source: Azure OpenAI deprecation notice
Test before switching
- Check the replacement's supported API endpoints and request parameters.
- Test your prompts, structured output, streaming and tool calls on staging.
- Compare quality, latency, pricing and rate limits on your workload.
- Keep a rollback path while the old model remains available.
Download retirement dates for your models.
What should I migrate gpt-5-chat to?
Azure OpenAI documents gpt-chat-latest as the successor. This is not a compatibility guarantee: request parameters, API endpoints, pricing, tool calls and output behaviour may differ. Check the linked provider documentation and run your own workload before switching.
We do not currently probe the Azure OpenAI API host, so no measured latency is shown here. View measured providers
Other Azure OpenAI models being retired
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| codex-mini | Azure OpenAI | 2026-11-15 | — not named |
| gpt-4.1 | Azure OpenAI | 2027-04-14 | — not named |
| gpt-4.1-mini | Azure OpenAI | 2027-04-14 | — not named |
| gpt-4.1-nano | Azure OpenAI | 2027-04-14 | — not named |
| gpt-4o | Azure OpenAI | 2027-04-14 | gpt-5.1 |
| gpt-4o-mini | Azure OpenAI | 2027-04-14 | — not named |
| gpt-4o-mini-transcribe | Azure OpenAI | 2027-06-15 | — not named |
| gpt-4o-mini-tts | Azure OpenAI | 2027-06-15 | — not named |
How is this calendar maintained?
Entries are pulled from provider documentation by an automated weekly job and every one carries a link to its source. Nothing is inferred from blog posts or social media. When a provider changes a date, the change appears here after the next run and is visible in the changelog. The full calendar across all providers is on the deprecations page, and this provider’s own list is at Azure OpenAI deprecations.