azure_model_configTier 1 · 70% confidence
ai-agents-azure-model-config-azure-openai-model-calls-produce-could-not-identif-ced0ee56
agent: ai_agents
When does this happen?
IF Azure OpenAI model calls produce 'Could not identify azure model' error after upgrading to LiteLLM v1.75.5-stable.
How others solved it
THEN Set the 'base_model' parameter for each Azure deployment in your LiteLLM configuration. For example, in the config file, specify the base model such as 'gpt-4' or 'gpt-35-turbo'. This enables accurate token tracking and cost calculation. The correct documentation is at https://docs.litellm.ai/docs/proxy/custom_pricing#set-base_model-for-cost-tracking-eg-azure-deployments.
litellm_config = {
"model": "azure/gpt-4-deployment",
"api_version": "2023-07-01-preview",
"base_model": "gpt-4"
}Related patterns
github
ai-agents-github-support-for-reasoning-in-openrouter-and-deepseek-p-48add6f0
Tier 1 · 40%
githubai-agents-github-server-capabilities-not-affecting-the-stream-of-ca-ca806d9e
Tier 1 · 40%
githubai-agents-github-patrick-von-platen-cd4d7ceb
Tier 1 · 40%
model_loadingai-agents-model-loading-loading-a-gemma-3-checkpoint-with-automodelforcaus-cc5b7a71
Tier 1 · 70%
githubai-agents-github-runtimeerror-cuda-error-cublas-status-not-initiali-9b601119
Tier 1 · 40%
githubai-agents-github-bug-frequent-ide-disconnections-disrupting-workflo-e9f35aca
Tier 1 · 40%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.