Replies: 1 comment 1 reply
-
|
Great question - this naming is confusing at first. For your case (Azure OpenAI deployment in Sweden Central, data zone standard), use:
How the keys differ:
If your billing/pricing is region-specific, Example: model_list:
- model_name: my-gpt51
litellm_params:
model: azure/my-gpt51-deployment
api_base: ${AZURE_API_BASE}
api_key: ${AZURE_API_KEY}
api_version: "2025-01-01-preview"
model_info:
base_model: azure/eu/gpt-5.1If you want, I can open a docs PR with a short "which Azure base_model should I pick?" table to make this explicit. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I have deployed a GPT-5.1 with model version "2025-11-13" in an Azure Foundry in Sweden Central with the deployment type data zone standard. I wanted to add that model to our LiteLLM config but I am struggling to select the correct base_model so I can properly track quota, costs etc. In the current cost model map I found:
What is the difference between these base models? What would be the correct one for my gpt-5.1 in an EU region with data zone standard deployment? I guess "azure/eu/gpt-5.1"? Why is there no versioned one for the eu deployments?
Feedback: This is highly confusing, I struggled with this some time ago because there are also "azure/" and "azure_ai/" models (what is the difference there?)
Any tips / documentation / answers would be highly appreciated, thanks!
Beta Was this translation helpful? Give feedback.
All reactions