What should we do?
Add a native implementation for the azureOpenAi provider discriminator using the official OpenAI Java SDK with an Azure-flavored client. Support both API key auth and the full Entra ID / Client Credentials path that the existing LangChain4j implementation supports today.
Requirements:
- Streaming-first internal driver, hardcoded capabilities, token usage, stop-reason mapping, error classification, JDK proxy transport — consistent with the openai/openaiCompatible implementation.
- Auth: apiKey AND clientCredentials (Entra ID via Azure SDK identity), same fields as today's
AzureAuthentication sealed type.
Why should we do it?
Day-one support for Azure OpenAI deployments via API key and Entra ID is a feature-parity requirement with the LangChain4j-backed implementation.
What should we do?
Add a native implementation for the
azureOpenAiprovider discriminator using the official OpenAI Java SDK with an Azure-flavored client. Support both API key auth and the full Entra ID / Client Credentials path that the existing LangChain4j implementation supports today.Requirements:
AzureAuthenticationsealed type.Why should we do it?
Day-one support for Azure OpenAI deployments via API key and Entra ID is a feature-parity requirement with the LangChain4j-backed implementation.