-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: DefaultAzureCredential not working #7665
Comments
Able to repro |
Ah, the docs are missing details. You need these keys
in your environment |
This still does not seem to fix the issue. I get the exact same log output after setting these environment variables
|
* test(test_get_model_info.py): add unit test confirming router deployment updates global 'get_model_info' * fix(get_supported_openai_params.py): fix custom llm provider 'get_supported_openai_params' Fixes BerriAI#7668 * docs(azure.md): clarify how azure ad token refresh on proxy works Closes BerriAI#7665
@krrishdholakia I'm still hitting this issue. I've tried setting all 3 items you suggested to a blank string. I'm running on Windows Powershell. I'm happy to get on a call to debug if it helps |
Sure let's do that @WGlenn43 https://calendly.com/d/4mp-gd3-k5k/litellm-1-1-onboarding-chat |
Hm...this still doesn't create a passwordless experience. We exclusively use the 'DefaultAzureCredential()' method from the azure-identity library. When users create Azure OpenAI clients with this method, RBAC roles govern access. We don't want to create, communicate or manage either AOAI API keys OR Service Principal client_secrets. And really, there is no need if the DefaultAzureCredential() can be used. This is a huge deal for enterprise customers. Let's get aider in the hands of more enterprise GenAI devs. |
can you point me to how the azure openai client handles this @SeaDude |
What happened?
I tried to follow this guide. My exact setup for the yaml is:
Relevant log output
Are you a ML Ops Team?
Yes
What LiteLLM version are you on ?
v1.53.9
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: