Skip to content
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

Azure Document Intelligence integration in LangChain #29865

Open
1 task done
stad121 opened this issue Feb 18, 2025 · 0 comments
Open
1 task done

Azure Document Intelligence integration in LangChain #29865

stad121 opened this issue Feb 18, 2025 · 0 comments

Comments

@stad121
Copy link

stad121 commented Feb 18, 2025

Privileged issue

  • I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create an issue here.

Issue Content

I'm currently exploring the Azure Document Intelligence integration in LangChain and noticed that authentication relies on providing an API key. However, in many enterprise environments, relying solely on API keys is not ideal due to security and compliance concerns.

Would it be possible to support alternative authentication methods, such as:

Azure Active Directory (AAD) tokens via az account get-access-token
Managed Identity Authentication (for Azure-hosted environments like VMs, Functions, or AKS)
Azure CLI-based authentication (similar to how the Azure SDKs allow it)
These authentication mechanisms align better with security best practices, enabling more seamless and secure integrations with enterprise applications.

I’d love to hear your thoughts on whether such an enhancement is feasible or if there are any existing workarounds. Thank you for your time, and I appreciate your consideration of this request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant