Skip to content

Commit ecd0e62

Browse files
authored
Update model-retirements.md
1 parent ae89107 commit ecd0e62

File tree

1 file changed

+14
-16
lines changed

1 file changed

+14
-16
lines changed

articles/ai-foundry/openai/concepts/model-retirements.md

Lines changed: 14 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -14,30 +14,28 @@ recommendations: false
1414

1515
# Azure OpenAI in Azure AI Foundry model deprecations and retirements
1616

17-
## Overview
18-
1917
Azure OpenAI models are continually refreshed with newer and more capable models. As part of this process, we deprecate and retire older models. This article provides information about models that are currently available, deprecated, and retired.
2018

2119
### Terminology
2220

23-
- **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.
21+
- **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.
2422
- **Retirement**: When a model is retired, it's no longer available for use. Azure OpenAI deployments of a retired model always return error responses.
2523

2624
## Notifications
2725

2826
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:
2927

30-
- We notify customers at model launch by programmatically designating a *not sooner than* retirement date. For preview models, it's between 90-120 days from launch. For generally available models, it's 365 days from launch.
31-
- We provide customers with at least 60 days notice before model retirement for generally available models.
32-
- We provide customers with least 30 days notice before preview model version upgrades.
28+
- 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.
29+
- We provide customers with at least 60 days' notice before model retirement for GA models.
30+
- We provide customers with least 30 days' notice before preview model version upgrades.
3331

3432
Retirements are done on a rolling basis, region by region. There's no schedule for when a specific region or SKU is upgraded.
3533

3634
### Notifications of upcoming retirements
3735

3836
Azure OpenAI notifies customers via two methods:
3937

40-
- **Azure Resource Health**: Anyone with **reader** permissions or higher can see Azure health alerts and configure personalized alerts via email, SMS, etc. See [Create Service Health alerts](/azure/service-health/alerts-activity-log-service-notifications-portal).
38+
- **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](/azure/service-health/alerts-activity-log-service-notifications-portal).
4139
- **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.
4240

4341
#### Azure Service Health filter configuration
@@ -46,27 +44,27 @@ The service is `azure OpenAI service`. (The casing reflects the current UX exper
4644

4745
Event types include:
4846

49-
- `Health advisories = Upgrade, Deprecation, & Retirement Notifications`.
47+
- `Health advisories = Upgrade, Deprecation, & Retirement Notifications.`
5048
- `Service issue = Outages`. (We recommend this event type only if you want to be notified of outages.)
5149

5250
If you want to receive SMS text-based alerts versus just emails, select **Create action group**. Then, under **Notification type**, select **Email/SMS message/Push/Voice** and configure your phone number.
5351

5452
## Model availability
5553

56-
See the following information for the availability of models:
54+
For the availability of models, see the following information:
5755

58-
- There is at least one year of model availability for generally available models after the release date of a model in at least one region worldwide
56+
- There is at least one year of model availability for GA models after the release date of a model in at least one region worldwide
5957
- 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.
60-
- Customers have 60 days to try out a new generally available model in at least one global or standard region before any upgrades happen to a newer generally available model.
58+
- 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.
6159

6260
### Considerations for Azure public cloud
6361

6462
Be aware of the following information:
6563

6664
- Not all model version combinations will be available in all regions.
6765
- Model version `N` and `N+1` might not always be available in the same region.
68-
- A generally available 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.
69-
- Preview model versions and generally available versions of the same model won't always be available to test together in the same region. There will be preview and generally available versions available to test in different regions.
66+
- A 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.
67+
- 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.
7068
- We reserve the right to limit future customers' use of a particular region to balance service quality for existing customers.
7169
- 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.
7270

@@ -75,13 +73,13 @@ Be aware of the following information:
7573
- Global standard deployments aren't available in government clouds.
7674
- Not all models or model versions available in commercial and public clouds will be available in government clouds.
7775
- 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 0125` and `gpt-4o (2024-05-13)`.
78-
- However, there's a 30-day overlap between new model versions, when more than two will be available. For example, `gpt-35-turbo 0125` or `gpt-4o (2024-05-13)` is updated to a future version, or for model family changes beyond version updates, such as when moving from `gpt-4 1106-preview` to `gpt-4o (2024-05-13)`.
76+
- However, there's a 30-day overlap between new model versions, when more than two will be available. For example, if `gpt-35-turbo 0125` or `gpt-4o (2024-05-13)` is updated to a future version. Another example is model family changes beyond version updates, like when moving from `gpt-4 1106-preview` to `gpt-4o (2024-05-13)`.
7977

8078
## Preparation for model retirements and version upgrades
8179

8280
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.
8381

84-
For more information on the model evaluation process, see the [Getting started with model evaluation](https://techcommunity.microsoft.com/t5/ai-azure-ai-services-blog/how-to-evaluate-amp-upgrade-model-versions-in-the-azure-openai/ba-p/4218880) guide.
82+
For more information on the model evaluation process, see the [Getting started with model evaluation](https://techcommunity.microsoft.com/t5/ai-azure-ai-services-blog/how-to-evaluate-amp-upgrade-model-versions-in-the-azure-openai/ba-p/4218880) blog post.
8583

8684
For information on the model upgrade process, see [How to upgrade to a new model or version](./model-versions.md).
8785

@@ -100,6 +98,6 @@ These models are currently available for use in Azure OpenAI.
10098

10199
## Retirement and deprecation history
102100

103-
To track individual updates to this article, refer to the [Git History](https://github.com/MicrosoftDocs/azure-ai-docs/commits/main/articles/ai-foundry/openai/includes/retirement/models.md)
101+
To track individual updates to this article, refer to the [Git history](https://github.com/MicrosoftDocs/azure-ai-docs/commits/main/articles/ai-foundry/openai/includes/retirement/models.md).
104102

105103
For a list of retired models, refer to the [retired models page](./legacy-models.md).

0 commit comments

Comments
 (0)