Edit

Share via


Azure OpenAI in Azure AI Foundry Models model deprecations and retirements

Overview

Azure OpenAI models are continually refreshed with newer and more capable models. As part of this process, we deprecate and retire older models. This document provides information about the models that are currently available, deprecated, and retired.

Terminology

  • Deprecation
    • When a model is deprecated, it's no longer available for new customers. It continues to be available for use by customers with 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 as follows for each deployment:

  1. At model launch, we programmatically designate a "not sooner than" retirement date (for preview models this is between 90-120 days from launch, for generally available (GA) models this is 365 days from launch).
  2. At least 60 days notice before model retirement for Generally Available (GA) models.
  3. At least 30 days notice before preview model version upgrades.

Retirements are done on a rolling basis, region by region. There is no schedule for when a specific region, or SKU will be upgraded.

Current models

Note

Not all models go through a deprecation period prior to retirement. Some models/versions only have a retirement date.

Fine-tuned models are subject to a different deprecation and retirement schedule from their equivalent base model.

These models are currently available for use in Azure OpenAI.

Text generation

Model Version Retirement date Replacement model
gpt-4.5-preview 2025-02-27 No Auto-upgrades
July 14, 2025
gpt-4.1 version: 2025-04-14
gpt-3.5-turbo-instruct 0914 No earlier than July 16, 2025
o1-preview 2024-09-12 July 28, 2025 o1
computer-use-preview 2025-03-11 No earlier than September 1, 2025
gpt-35-turbo 1106 No earlier than September 1, 2025 gpt-4.1-mini version: 2025-04-14
gpt-35-turbo 0125 No earlier than September 1, 2025 gpt-4.1-mini version: 2025-04-14
gpt-4 turbo-2024-04-09 No earlier than September 1, 2025 gpt-4o version: 2024-11-20
model router 2025-05-19 No earlier than September 1, 2025
gpt-4o 2024-05-13 No earlier than September 15, 2025 gpt-4.1 version: 2025-04-14
gpt-4o-mini 2024-07-18 No earlier than September 15, 2025 gpt-4.1-mini version: 2025-04-14
o1-mini 2024-09-12 No earlier than September 26, 2025
gpt-4o 2024-08-06 No earlier than October 15, 2025 gpt-4.1 version: 2025-04-14
o1 2024-12-17 No earlier than December 17, 2025
o3-mini 2025-01-31 No earlier than February 1, 2026
gpt-4o 2024-11-20 No earlier than March 1, 2026 gpt-4.1 version: 2025-04-14
gpt-4.1 2025-04-14 No earlier than April 11, 2026
gpt-4.1-mini 2025-04-14 No earlier than April 11, 2026
gpt-4.1-nano 2025-04-14 No earlier than April 11, 2026
o4-mini 2025-04-16 No earlier than April 11, 2026
o3 2025-04-16 No earlier than April 11, 2026

We notify all customers with these preview deployments at least 30 days before the start of the upgrades. We publish an upgrade schedule detailing the order of regions and model versions that we follow during the upgrades, and link to that schedule from here.

Tip

Will a model upgrade happen if the new model version is not yet available in that region?

Yes, even in cases where the latest model version is not yet available in a region, we automatically upgrade deployments during the scheduled upgrade window. For more information, see Azure OpenAI model versions.

Fine-tuned models

Fine-tuned models retire in two phases: training and deployment.

All fine-tuned models follow their equivalent base model for training retirement. Once retired, a given model is no longer available for fine tuning.

For fine-tuned models made generally available since gpt-4o-2024-08-06, deployment retirement occurs 1 year after training retirement. At deployment retirement, inference and deployment returns error responses.

Model Version Training retirement date Deployment retirement date
gpt-35-turbo 1106 At base model retirement At training retirement
gpt-35-turbo 0125 At base model retirement At training retirement
gpt-4o 2024-08-06 At base model retirement One year after training retirement
gpt-4o-mini 2024-07-18 At base model retirement One year after training retirement
gpt-4.1 2025-04-14 At base model retirement One year after training retirement
gpt-4.1-mini 2025-04-14 At base model retirement One year after training retirement
gpt-4.1-nano 2025-04-14 At base model retirement One year after training retirement
o4-mini 2025-04-16 At base model retirement One year after training retirement

Default model versions

Model Current default version New default version Default upgrade date
gpt-35-turbo 0301 0125 Deployments of versions 0301, 0613, and 1106 set to Auto-update to default will be automatically upgraded to version: 0125, starting on January 21, 2025.
gpt-4o 2024-08-06 - -

Model availability

  1. At least one year of model availability for GA models after the release date of a model in at least one region worldwide
  2. For global deployments, all future model versions starting with gpt-4o and gpt-4 0409 will be available with their (N) next succeeding model (N+1) for comparison together.
  3. 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.

Considerations for the Azure public cloud

Be aware of the following:

  1. All model version combinations will not be available in all regions.
  2. Model version N and N+1 might not always be available in the same region.
  3. GA model version N might upgrade to a future model version N+X in some regions based on capacity limitations, and without the new model version N+X separately 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.
  4. 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.
  5. We reserve the right to limit future customers using a particular region to balance service quality for existing customers.
  6. 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. See the terms of service for more information.

Special considerations for Azure Government clouds

  1. Global standard deployments won't be available in government clouds.
  2. Not all models or model versions available in commercial / public cloud will be available in government clouds.
  3. In the Azure Government clouds, we intend to support only one version of a given model at a time.
    1. For example only one version of gpt-35-turbo 0125 and gpt-4o (2024-05-13).
  4. There will however be a 30 day overlap between new model versions, where more than two will be available.
    1. For example if gpt-35-turbo 0125 or gpt-4o (2024-05-13) is updated to a future version, or
    2. for model family changes beyond version updates, such as when moving from gpt-4 1106-preview to gpt-4o (2024-05-13).

Who is notified of upcoming retirements

Azure OpenAI notifies customers via two methods:

  • Azure Resource Health - Anyone with reader permissions or above can see Azure health alerts, as well as configure personalized alerts via email, SMS, etc. See Create Service Health Alerts
  • Email - email notifications are automatically sent to subscription owners. Any individual with reader permissions may however configure their own alerts by following the guidance above.

How to get ready 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 guide.

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

Retirement and deprecation history

To track individual updates to this article refer to the Git History