Skip to content

Commit 7b92e9e

Browse files
committed
update
1 parent 2be5aa4 commit 7b92e9e

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/ai-services/openai/how-to/switching-endpoints.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -111,10 +111,8 @@ client = AzureOpenAI(
111111

112112
## Keyword argument for model
113113

114-
OpenAI uses the `model` keyword argument to specify what model to use. Azure OpenAI has the concept of [deployments](create-resource.md?pivots=web-portal#deploy-a-model) and uses the `deployment_id` keyword argument to describe which model deployment to use. Azure OpenAI also supports the use of `engine` interchangeably with `deployment_id`. `deployment_id` corresponds to the custom name you chose for your model during model deployment. By convention in our docs, we often show `deployment_id`'s which match the underlying model name, but if you chose a different deployment name that doesn't match the model name you need to use that name when working with models in Azure OpenAI.
115-
116-
For OpenAI `engine` still works in most instances, but it's deprecated and `model` is preferred.
117-
114+
OpenAI uses the `model` keyword argument to specify what model to use. Azure OpenAI has the concept of unique model [deployments](create-resource.md?pivots=web-portal#deploy-a-model). When using Azure OpenAI `model=` should refer to the underling deployment name you chose when you deployed the model.
115+
118116
<table>
119117
<tr>
120118
<td> OpenAI </td> <td> Azure OpenAI </td>

0 commit comments

Comments
 (0)