Skip to content

docs(guardrails): document Entra ID auth for Azure Content Safety - #1393

Open
ssennettau wants to merge 2 commits into
BerriAI:mainfrom
ssennettau:litellm_azure_content_safety_entra_id
Open

docs(guardrails): document Entra ID auth for Azure Content Safety#1393
ssennettau wants to merge 2 commits into
BerriAI:mainfrom
ssennettau:litellm_azure_content_safety_entra_id

Conversation

@ssennettau

Copy link
Copy Markdown

Documents the Microsoft Entra ID option added to the Azure Content Safety guardrails in BerriAI/litellm#40420.

The page previously showed api_key as required. It now has an Authentication section with a tab for each credential type, and the Common Params entry for api_key says 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

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>
@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
litellm Ready Ready Preview Sep 9, 2026 4:23pm UTC

Request Review

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>
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

Successfully merging this pull request may close these issues.

1 participant