docs(guardrails): document Entra ID auth for Azure Content Safety - #1393
Open
ssennettau wants to merge 2 commits into
Open
docs(guardrails): document Entra ID auth for Azure Content Safety#1393ssennettau wants to merge 2 commits into
ssennettau wants to merge 2 commits into
Conversation
The Azure Content Safety guardrails now accept a Microsoft Entra ID token when api_key is omitted, so document both credential types, what the identity needs, and the custom subdomain requirement. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
An Entra token reaches every Cognitive Services resource the identity can use, so LiteLLM only sends one to an Azure endpoint. Say so, and point gateway deployments at api_key instead Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ssennettau
marked this pull request as ready for review
September 10, 2026 15:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the Microsoft Entra ID option added to the Azure Content Safety guardrails in BerriAI/litellm#40420.
The page previously showed
api_keyas required. It now has an Authentication section with a tab for each credential type, and the Common Params entry forapi_keysays it is optional.The Entra ID tab covers what an operator has to get right: the custom subdomain endpoint, the Cognitive Services User role, which credential sources the chain accepts, and how to disable key based access once identity auth works.
No change to the Quick Start example, which keeps using an API key.
🤖 Generated with Claude Code