docs(azure_sentinel): document sovereign cloud authority and audience settings - #804
Merged
yucheng-berri merged 4 commits intoAug 7, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5 tasks
yucheng-berri
deleted the
litellm_lit5293_azure_sentinel_sovereign_cloud
branch
August 7, 2026 01:59
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.
TLDR
The Azure Sentinel page documents only the commercial-cloud setup, so there was nothing telling an Azure Government or Azure China operator that pointing
AZURE_SENTINEL_ENDPOINTat a sovereign ingestion endpoint is not enough on its ownAdds a "Sovereign clouds" section with the authority-host to audience table, plus rows for the two new settings,
AZURE_SENTINEL_AUTHORITY_HOSTandAZURE_SENTINEL_OAUTH_SCOPE, in both the Sentinel config table and the environment variable referenceMerge order
This has to merge before BerriAI/litellm#36137, not after.
test_env_keys.pychecks out this repo at its default branch and fails any env var read underlitellm/that is not mentioned anywhere in these docs, so the code PR'sdocumentationandcode-qualityjobs stay red until this lands