Skip to content

Commit 77f4d15

Browse files
Merge pull request #267163 from gojira/keijik/2024-02-retirements
Minor updates to model lifecycle docs
2 parents 3cd90f4 + 7b82f94 commit 77f4d15

File tree

4 files changed

+27
-25
lines changed

4 files changed

+27
-25
lines changed

articles/ai-services/openai/concepts/legacy-models.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,22 @@
11
---
2-
title: Azure OpenAI Service legacy models
2+
title: Azure OpenAI Service deprecated models
33
titleSuffix: Azure OpenAI
4-
description: Learn about the legacy models in Azure OpenAI.
4+
description: Learn about the deprecated models in Azure OpenAI.
55
ms.service: azure-ai-openai
66
ms.topic: conceptual
7-
ms.date: 07/06/2023
7+
ms.date: 02/26/2024
88
ms.custom: references_regions, build-2023, build-2023-dataai
99
manager: nitinme
10-
author: mrbullwinkle #ChrisHMSFT
11-
ms.author: mbullwin #chrhoder
10+
author: mrbullwinkle
11+
ms.author: mbullwin
1212
recommendations: false
1313
---
1414

15-
# Azure OpenAI Service legacy models
15+
# Azure OpenAI Service deprecated models
1616

17-
Azure OpenAI Service offers a variety of models for different use cases. The following models are not available for new deployments beginning July 6, 2023. Deployments created prior to July 6, 2023 remain available to customers until July 5, 2024. We recommend customers migrate to the replacement models prior to the July 5, 2024 retirement.
17+
Azure OpenAI Service offers a variety of models for different use cases. The following models were deprecated on July 6, 2023 and will be retired on July 5, 2024. These models are no longer available for new deployments. Deployments created prior to July 6, 2023 remain available to customers until July 5, 2024. We recommend customers migrate their applications to deployments of replacement models prior to the July 5, 2024 retirement.
18+
19+
At the time of retirement, deployments of these models will stop returning valid API responses.
1820

1921
## GPT-3.5
2022

articles/ai-services/openai/concepts/model-versions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ We want to make it easy for customers to stay up to date as models improve. Cus
2323

2424
When a customer deploys GPT-3.5-Turbo and GPT-4 on Azure OpenAI Service, the standard behavior is to deploy the current default version – for example, GPT-4 version 0314. When the default version changes to say GPT-4 version 0613, the deployment is automatically updated to version 0613 so that customer deployments feature the latest capabilities of the model.
2525

26-
Customers can also deploy a specific version like GPT-4 0314 or GPT-4 0613 and choose an update policy, which can include the following options:
26+
Customers can also deploy a specific version like GPT-4 0613 and choose an update policy, which can include the following options:
2727

2828
* Deployments set to **Auto-update to default** automatically update to use the new default version.
2929
* Deployments set to **Upgrade when expired** automatically update when its current version is retired.

articles/ai-services/openai/concepts/models.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,12 @@ Azure OpenAI Service is powered by a diverse set of models with different capabi
2727

2828
## GPT-4 and GPT-4 Turbo Preview
2929

30-
GPT-4 can solve difficult problems with greater accuracy than any of OpenAI's previous models. Like GPT-3.5 Turbo, GPT-4 is optimized for chat and works well for traditional completions tasks. Use the Chat Completions API to use GPT-4. To learn more about how to interact with GPT-4 and the Chat Completions API check out our [in-depth how-to](../how-to/chatgpt.md).
30+
GPT-4 is a large multimodal model (accepting text or image inputs and generating text) that can solve difficult problems with greater accuracy than any of OpenAI's previous models. Like GPT-3.5 Turbo, GPT-4 is optimized for chat and works well for traditional completions tasks. Use the Chat Completions API to use GPT-4. To learn more about how to interact with GPT-4 and the Chat Completions API check out our [in-depth how-to](../how-to/chatgpt.md).
31+
32+
GPT-4 Turbo with Vision is the version of GPT-4 that accepts image inputs. It is available as the `vision-preview` model of `gpt-4`.
3133

3234
- `gpt-4`
3335
- `gpt-4-32k`
34-
- `gpt-4-vision`
3536

3637
You can see the token context length supported by each model in the [model summary table](#model-summary-table-and-region-availability).
3738

@@ -97,7 +98,6 @@ See [model versions](../concepts/model-versions.md) to learn about how Azure Ope
9798
> [!NOTE]
9899
> Version `0314` of `gpt-4` and `gpt-4-32k` will be retired no earlier than July 5, 2024. Version `0613` of `gpt-4` and `gpt-4-32k` will be retired no earlier than September 30, 2024. See [model updates](../how-to/working-with-models.md#model-updates) for model upgrade behavior.
99100
100-
101101
GPT-4 version 0125-preview is an updated version of the GPT-4 Turbo preview previously released as version 1106-preview. GPT-4 version 0125-preview completes tasks such as code generation more completely compared to gpt-4-1106-preview. Because of this, depending on the task, customers may find that GPT-4-0125-preview generates more output compared to the gpt-4-1106-preview. We recommend customers compare the outputs of the new model. GPT-4-0125-preview also addresses bugs in gpt-4-1106-preview with UTF-8 handling for non-English languages.
102102

103103
> [!IMPORTANT]
@@ -205,7 +205,7 @@ The following Embeddings models are available with [Azure Government](/azure/azu
205205
| Model ID | Feature Availability | Max Request (characters) |
206206
| --- | --- | :---: |
207207
| dalle2 | East US | 1,000 |
208-
| dalle3 | Sweden Central | 4,000 |
208+
| dall-e-3 | Sweden Central | 4,000 |
209209

210210
### Fine-tuning models
211211

articles/ai-services/openai/how-to/working-with-models.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -20,31 +20,31 @@ You can get a list of models that are available for both inference and fine-tuni
2020

2121
## Model updates
2222

23-
Azure OpenAI now supports automatic updates for select model deployments. On models where automatic update support is available, a model version drop-down will be visible in Azure OpenAI Studio under **Create new deployment** and **Edit deployment**:
23+
Azure OpenAI now supports automatic updates for select model deployments. On models where automatic update support is available, a model version drop-down is visible in Azure OpenAI Studio under **Create new deployment** and **Edit deployment**:
2424

2525
:::image type="content" source="../media/models/auto-update.png" alt-text="Screenshot of the deploy model UI of Azure OpenAI Studio." lightbox="../media/models/auto-update.png":::
2626

2727
You can learn more about Azure OpenAI model versions and how they work in the [Azure OpenAI model versions](../concepts/model-versions.md) article.
2828

2929
### Auto update to default
3030

31-
When **Auto-update to default** is selected your model deployment will be automatically updated within two weeks of a change in the default version. For a preview version, it will update automatically when a new preview version is available starting two weeks after the new preview version is released.
31+
When you set your deployment to **Auto-update to default**, your model deployment is automatically updated within two weeks of a change in the default version. For a preview version, it updates automatically when a new preview version is available starting two weeks after the new preview version is released.
3232

3333
If you're still in the early testing phases for inference models, we recommend deploying models with **auto-update to default** set whenever it's available.
3434

3535
### Specific model version
3636

37-
As your use of Azure OpenAI evolves, and you start to build and integrate with applications you might want to manually control model updates so that you can first test and validate that model performance is remaining consistent for your use case prior to upgrade.
37+
As your use of Azure OpenAI evolves, and you start to build and integrate with applications you might want to manually control model updates. You can first test and validate that your application behavior is consistent for your use case before upgrading.
3838

39-
When you select a specific model version for a deployment this version will remain selected until you either choose to manually update yourself, or once you reach the retirement date for the model. When the retirement date is reached the model will automatically upgrade to the default version at the time of retirement.
39+
When you select a specific model version for a deployment, this version remains selected until you either choose to manually update yourself, or once you reach the retirement date for the model. When the retirement date is reached the model will automatically upgrade to the default version at the time of retirement.
4040

41-
## Viewing deprecation dates
41+
## Viewing retirement dates
4242

4343
For currently deployed models, from Azure OpenAI Studio select **Deployments**:
4444

4545
:::image type="content" source="../media/models/deployments.png" alt-text="Screenshot of the deployment UI of Azure OpenAI Studio." lightbox="../media/models/deployments.png":::
4646

47-
To view deprecation/expiration dates for all available models in a given region from Azure OpenAI Studio select **Models** > **Column options** > Select **Deprecation fine tune** and **Deprecation inference**:
47+
To view retirement dates for all available models in a given region from Azure OpenAI Studio, select **Models** > **Column options** > Select **Deprecation fine tune** and **Deprecation inference**:
4848

4949
:::image type="content" source="../media/models/column-options.png" alt-text="Screenshot of the models UI of Azure OpenAI Studio." lightbox="../media/models/column-options.png":::
5050

@@ -54,28 +54,28 @@ You can check what model upgrade options are set for previously deployed models
5454

5555
:::image type="content" source="../media/how-to/working-with-models/deployments.png" alt-text="Screenshot of the deployments pane with a deployment name highlighted." lightbox="../media/how-to/working-with-models/deployments.png":::
5656

57-
This will open the **Properties** for the model deployment. You can view what upgrade options are set for your deployment under **Version update policy**:
57+
Selecting a deployment name opens the **Properties** for the model deployment. You can view what upgrade options are set for your deployment under **Version update policy**:
5858

5959
:::image type="content" source="../media/how-to/working-with-models/update-policy.png" alt-text="Screenshot of the model deployments property UI." lightbox="../media/how-to/working-with-models/update-policy.png":::
6060

6161
The corresponding property can also be accessed via [REST](../how-to/working-with-models.md#model-deployment-upgrade-configuration), [Azure PowerShell](/powershell/module/az.cognitiveservices/get-azcognitiveservicesaccountdeployment), and [Azure CLI](/cli/azure/cognitiveservices/account/deployment#az-cognitiveservices-account-deployment-show).
6262

6363
|Option| Read | Update |
6464
|---|---|---|
65-
| [REST](../how-to/working-with-models.md#model-deployment-upgrade-configuration) | Yes. If `versionUpgradeOption` is not returned it means it is `null` |Yes |
65+
| [REST](../how-to/working-with-models.md#model-deployment-upgrade-configuration) | Yes. If `versionUpgradeOption` is not returned, it means it is `null` |Yes |
6666
| [Azure PowerShell](/powershell/module/az.cognitiveservices/get-azcognitiveservicesaccountdeployment) | Yes.`VersionUpgradeOption` can be checked for `$null`| Yes |
6767
| [Azure CLI](/cli/azure/cognitiveservices/account/deployment#az-cognitiveservices-account-deployment-show) | Yes. It shows `null` if `versionUpgradeOption` is not set.| *No.* It is currently not possible to update the version upgrade option.|
6868

6969
There are three distinct model deployment upgrade options:
7070

7171
| Name | Description |
7272
|------|--------|
73-
| `OnceNewDefaultVersionAvailable` | Once a new version is designated as the default, the model deployment will automatically upgrade to the default version within two weeks of that designation change being made. |
74-
|`OnceCurrentVersionExpired` | Once the retirement date is reached the model deployment will automatically upgrade to the current default version. |
75-
|`NoAutoUpgrade` | The model deployment will never automatically upgrade. Once the retirement date is reached the model deployment will stop working. You will need to update your code referencing that deployment to point to a nonexpired model deployment. |
73+
| `OnceNewDefaultVersionAvailable` | Once a new version is designated as the default, the model deployment automatically upgrades to the default version within two weeks of that designation change being made. |
74+
|`OnceCurrentVersionExpired` | Once the retirement date is reached the model deployment automatically upgrades to the current default version. |
75+
|`NoAutoUpgrade` | The model deployment never automatically upgrades. Once the retirement date is reached the model deployment stops working. You need to update your code referencing that deployment to point to a nonexpired model deployment. |
7676

7777
> [!NOTE]
78-
> `null` is equivalent to `AutoUpgradeWhenExpired`. If the **Version update policy** option is not present in the properties for a model that supports model upgrades this indicates the value is currently `null`. Once you explicitly modify this value the property will be visible in the studio properties page as well as via the REST API.
78+
> `null` is equivalent to `AutoUpgradeWhenExpired`. If the **Version update policy** option is not present in the properties for a model that supports model upgrades this indicates the value is currently `null`. Once you explicitly modify this value, the property is visible in the studio properties page as well as via the REST API.
7979
8080
### Examples
8181

@@ -122,7 +122,7 @@ New-AzCognitiveServicesAccountDeployment -ResourceGroupName {ResourceGroupName}
122122

123123
# [REST](#tab/rest)
124124

125-
To query the current model deployment settings including the deployment upgrade configuration for a given resource use [`Deployments List`](/rest/api/cognitiveservices/accountmanagement/deployments/list?tabs=HTTP#code-try-0). If the value is null you won't see a `versionUpgradeOption` property.
125+
To query the current model deployment settings including the deployment upgrade configuration for a given resource use [`Deployments List`](/rest/api/cognitiveservices/accountmanagement/deployments/list?tabs=HTTP#code-try-0). If the value is null, you won't see a `versionUpgradeOption` property.
126126

127127
```http
128128
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}/deployments?api-version=2023-05-01

0 commit comments

Comments
 (0)