Skip to content

Commit 2696bcb

Browse files
committed
update
1 parent cc7a6d1 commit 2696bcb

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,10 @@ 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 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.
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 underlying deployment name you chose when you deployed the model.
115+
116+
> [!IMPORTANT]
117+
> When you access the model via the API in Azure OpenAI you will need to refer to the deployment name rather than the underlying model name in API calls. This is one of the [key differences](../how-to/switching-endpoints.md) between OpenAI and Azure OpenAI. OpenAI only requires the model name, Azure OpenAI always requires deployment name, even when using the model parameter. In our docs we often have examples where deployment names are represented as identical to model names to help indicate which model works with a particular API endpoint. Ultimately your deployment names can follow whatever naming convention is best for your use case.
115118
116119
<table>
117120
<tr>

0 commit comments

Comments
 (0)