docs(azure_ai): document entra id / oauth authentication

[devin-ai-integration]

Summary

Entra ID / OAuth auth for azure_ai was only shown as a service-principal snippet on the agents page, so users had no way to discover that Foundry deployments can authenticate without an API key. This adds an "Entra ID / OAuth authentication" section to the azure_ai provider page covering every credential type the provider accepts (service principal, pre-fetched azure_ad_token, OIDC federated token, username/password, managed identity / DefaultAzureCredential, and a custom azure_ad_token_provider), each with its environment variable fallback, plus azure_scope and the default https://cognitiveservices.azure.com/.default audience.

It also states which routes are covered (chat, embeddings, rerank, OCR including Document Intelligence, image generation and edits, agents) and that token providers are cached per credential set and scope. Code side is BerriAI/litellm#35415, which makes the remaining routes honor these credentials.

Examples are given for both the proxy config and the SDK; npm run build passes.

Link to Devin session: https://app.devin.ai/sessions/5df71ea3473e41b8913326682dab9d56
Requested by: @mateo-berri

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview	Jul 31, 2026 9:22pm