Model availability
For the availability of models, see the following information:- Generally Available (GA) model versions will be available for a minimum of 12 months.
- After 12 months, existing customers may continue to use older model versions for an additional six months.
- New customers who have never deployed the older model version will no longer have access after 12 months.
- For global deployments, all future model versions starting with
gpt-4oandgpt-4 0409will be available with their (N) next succeeding model (N+1) for comparison together. - Customers have 60 days to try out a new GA model in at least one global or standard region before any upgrades happen to a newer GA model.
Terminology
- Deprecation: When a model is deprecated, it’s no longer available for new customers. It continues to be available for use by customers who have existing deployments until the model is retired.
- Retirement: When a model is retired, it’s no longer available for use. Azure OpenAI deployments of a retired model always return error responses.
Notifications
Azure OpenAI notifies customers of active Azure OpenAI deployments for models with upcoming retirements. We notify customers of upcoming retirements for each deployment in the following ways:- We notify customers at model launch by programmatically designating a not sooner than retirement date. For preview models, it’s 90-120 days from launch. For generally available (GA) models, it’s 365 days from launch.
- We provide customers with at least 60 days’ notice before model retirement for GA models.
- We provide customers with least 30 days’ notice before preview model version upgrades.
Notifications of upcoming retirements
Azure OpenAI notifies customers via two methods:- Azure Resource Health: Anyone with reader permissions or higher can see Azure health alerts and configure personalized alerts via email and SMS. See Create Service Health alerts.
- Email: Email notifications are automatically sent to subscription owners. However, any individual with reader permissions can configure their own alerts by following the previous guidance.
Azure Service Health filter configuration
The service isazure OpenAI service. (The casing reflects the current UX experience.)
Event types include:
Health advisories = Upgrade, Deprecation, & Retirement Notifications.Service issue = Outages. (We recommend this event type only if you want to be notified of outages.)
Considerations for Azure public cloud
Be aware of the following information:- Not all model version combinations will be available in all regions.
- Model version
NandN+1might not always be available in the same region. - A GA model version
Nmight upgrade to a future model versionN+Xin some regions based on capacity limitations, and without the new model versionN+Xseparately being available to test in the same region. The new model version will be available to test in other regions before any upgrades are scheduled. - Preview model versions and GA versions of the same model won’t always be available to test together in the same region. There will be preview and GA versions available to test in different regions.
- We reserve the right to limit future customers’ use of a particular region to balance service quality for existing customers.
- As always at Microsoft, security is of the utmost importance. If a model or model version is found to have compliance or security issues, we reserve the right to invoke the need to do emergency retirements. Refer to the terms of service for more information.
Special considerations for Azure Government clouds
- Global standard deployments aren’t available in government clouds.
- Not all models or model versions available in commercial and public clouds will be available in government clouds.
- In Azure Government clouds, we intend to support only one version of a given model at a time. For example, only one version of
gpt-35-turbo 0125andgpt-4o (2024-05-13). - However, there’s a 30-day overlap between new model versions, when more than two will be available. For example, if
gpt-35-turbo 0125orgpt-4o (2024-05-13)is updated to a future version. Another example is model family changes beyond version updates, like when moving fromgpt-4 1106-previewtogpt-4o (2024-05-13).
Preparation for model retirements and version upgrades
To prepare for model retirements and version upgrades, we recommend that customers test their applications with the new models and versions and evaluate their behavior. We also recommend that customers update their applications to use the new models and versions before the retirement date. For more information on the model evaluation process, see the Getting started with model evaluation blog post. For information on the model upgrade process, see How to upgrade to a new model or version. For more information on how to manage model upgrades and migrations for provisioned deployments, see Managing models on provisioned deployment types.Current models
Not all models go through a deprecation period before retirement. Some models or versions only have a retirement date.Fine-tuned models are subject to a different deprecation and retirement schedule from their equivalent base model.
- Text generation
- Audio
- Image and video
- Embedding
Text generation
| Model Name | Model Version1 | Lifecycle Status | Deprecation Date (No New Customers) | Retirement Date | Replacement Model |
|---|---|---|---|---|---|
gpt-5-chat | 2025-08-07 | Preview | n/a | 2026-04-15 | gpt-5.3-chat |
gpt-5-chat | 2025-10-03 | Preview | n/a | 2026-04-15 | gpt-5.3-chat |
gpt-5.3-chat | 2025-12-11 | Preview | n/a | 2026-06-01 | |
gpt-4o | 2024-05-13 | Generally Available | 2025-05-13 | Standard deployment type retires on 2026-03-31, with auto-upgrades scheduled to start on 2026-03-09. For other deployment types, including ALL Provisioned, Global Standard, and Data Zone Standard, the retirement date has been moved to 2026-10-01. | gpt-5.1 |
gpt-4o | 2024-08-06 | Generally Available | 2025-08-06 | Standard deployment type retires on 2026-03-31, with auto-upgrades scheduled to start on 2026-03-09. For other deployment types, including ALL Provisioned, Global Standard, and Data Zone Standard, the retirement date has been moved to 2026-10-01. | gpt-5.1 |
gpt-4o | 2024-11-20 | Generally Available | 2025-11-20 | 2026-10-01 | gpt-5.1 |
gpt-4o-mini | 2024-07-18 | Generally Available | 2025-07-18 | Standard deployment type retires on 2026-03-31, with auto-upgrades scheduled to start on 2026-03-09. For other deployment types, including ALL Provisioned, Global Standard, and Data Zone Standard, the retirement date has been moved to 2026-10-01. | gpt-4.1-mini |
gpt-4.1 | 2025-04-14 | Generally Available | 2026-04-14 | 2026-10-14 | gpt-5 |
gpt-4.1-mini | 2025-04-14 | Generally Available | 2026-04-14 | 2026-10-14 | gpt-5-mini |
gpt-4.1-nano | 2025-04-14 | Generally Available | 2026-04-14 | 2026-10-14 | gpt-5-nano |
computer-use-preview | 2025-03-11 | Preview | n/a | No earlier than 2026-04-14 | |
o1 | 2024-12-17 | Generally Available | 2025-12-17 | 2026-07-15 | o3 |
o1-pro | 2025-03-19 | Generally Available | 2026-03-19 | 2026-09-18 | o3-pro |
o3-mini | 2025-01-31 | Generally Available | 2026-01-31 | 2026-08-02 | o4-mini |
o3 | 2025-04-16 | Generally Available | 2026-04-16 | 2026-10-16 | |
o3-pro | 2025-06-10 | Generally Available | 2026-06-10 | 2026-12-10 | |
o3-deep-research | 2025-06-26 | Generally Available | 2026-06-26 | 2026-12-26 | |
o4-mini | 2025-04-16 | Generally Available | 2026-04-16 | 2026-10-16 | |
codex-mini | 2025-05-16 | Generally Available | 2026-05-16 | 2026-11-15 | |
model-router | 2025-11-18 | Generally Available | 2026-11-18 | 2027-05-20 | |
gpt-5-mini | 2025-08-07 | Generally Available | 2026-08-07 | 2027-02-06 | |
gpt-5-nano | 2025-08-07 | Generally Available | 2026-08-07 | 2027-02-06 | |
gpt-5-codex | 2025-09-15 | Generally Available | 2026-09-15 | 2027-03-17 | |
gpt-5-pro | 2025-10-06 | Generally Available | 2026-10-06 | 2027-04-07 | |
gpt-5.1 | 2025-11-13 | Generally Available | 2026-11-13 | 2027-05-15 | |
gpt-5.1-codex | 2025-11-13 | Generally Available | 2026-11-13 | 2027-05-15 | |
gpt-5.1-codex-mini | 2025-11-13 | Generally Available | 2026-11-13 | 2027-05-15 | |
gpt-5.1-chat | 2025-11-13 | Preview | n/a | No earlier than 2026-03-31 | |
gpt-5.2 | 2025-12-11 | Generally Available | No earlier than 2026-12-12 | No earlier than 2027-05-12 | |
gpt-5.2-chat | 2025-12-11 | Preview | n/a | No earlier than 2026-04-01 | |
gpt-5.2-codex | 2026-01-14 | Generally Available | 2027-01-14 | 2027-07-14 | gpt-5.3-codex |
gpt-5.3-codex | 2026-02-24 | Generally Available | 2027-02-25 | 2027-08-25 | |
gpt-5.4 | 2026-03-05 | Generally Available | 2027-03-05 | 2027-09-05 | |
gpt-5.4-pro | 2026-03-05 | Generally Available | 2027-03-05 | 2027-09-05 |
Fine-tuned models
Fine-tuned models retire in two phases: training and deployment. Unless explicitly stated, training retires no earlier than the base model retirement date. After a model is retired for training, it’s no longer available for fine-tuning but any models you’ve trained remain available for deployment. At deployment retirement, inference and deployment return error responses.| Model | Version | Training retirement date | Deployment retirement date |
|---|---|---|---|
gpt-4o | 2024-08-06 | No earlier than 2027-04-011 | 2027-10-01 |
gpt-4o-mini | 2024-07-18 | No earlier than 2027-04-011 | 2027-10-01 |
gpt-4.1 | 2025-04-14 | No earlier than 2027-04-141 | 2027-10-14 |
gpt-4.1-mini | 2025-04-14 | No earlier than 2027-04-141 | 2027-10-14 |
gpt-4.1-nano | 2025-04-14 | No earlier than 2027-04-141 | 2027-10-14 |
o4-mini | 2025-04-16 | Base model retirement | One year after training retirement |
Default model versions
| Model | Current default version | New default version | Default upgrade date |
|---|---|---|---|
gpt-4o | 2024-08-06 | - | - |