Update model retirement policies and terminology#724
Conversation
Clarified access restrictions for new customers regarding older model versions and added details on customer evaluation at the Azure subscription level.
|
@tkudo-ms : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 7aeb861: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
| - **Retirement**: When a model is retired, it's no longer available for use. Azure OpenAI deployments of a retired model always return error responses. | ||
|
|
||
| Example: | ||
| If a customer has deployed a model version in Subscription A before the deprecation date,and later creates a new Subscription B under the same tenant after the deprecation date,Subscription B is considered a new customer and cannot deploy the deprecated model version. |
There was a problem hiding this comment.
| If a customer has deployed a model version in Subscription A before the deprecation date,and later creates a new Subscription B under the same tenant after the deprecation date,Subscription B is considered a new customer and cannot deploy the deprecated model version. | |
| If a customer has deployed a model version in **Subscription A** before the deprecation date and later creates a new **Subscription B** under the same tenant after the deprecation date, **Subscription B** is considered a new customer and cannot deploy the deprecated model version. |
| ### 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. | ||
| - **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. For the purposes of this document, "customer" is evaluated at the Azure subscription level,based on whether that subscription has ever deployed the specific model version. |
There was a problem hiding this comment.
| - **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. For the purposes of this document, "customer" is evaluated at the Azure subscription level,based on whether that subscription has ever deployed the specific model version. | |
| - **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. For the purposes of this document, "customer" is evaluated at the Azure subscription level, based on whether that subscription has ever deployed the specific model version. |
|
@tkudo-ms Can you respond to the requested changes or let us know if you would like us to commit them? @mrbullwinkle - When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
4 participants
Clarified access restrictions for new customers regarding older model versions and added details on customer evaluation at the Azure subscription level.
Clarify that "New customers" and "existing customers" are evaluated at the Azure subscription level,based on whether the subscription has ever deployed the specific model version.
Add a short example to prevent ambiguity for tenants that regularly provision new subscriptions.