bugfix - fixed content safety client creation w/ APIM & managed identity#633
Merged
paullizer merged 1 commit intomicrosoft:Developmentfrom Jan 23, 2026
Merged
Conversation
…erly when using APIM or managed identity
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request fixes a bug in the content safety client initialization logic that prevented the client from being created when using managed identity or APIM authentication. The original code incorrectly required both the endpoint AND the API key to be present, blocking scenarios where authentication is handled via managed identity or APIM subscription keys.
Changes:
- Removed the
and safety_keycondition from the content safety client initialization check, allowing the client to be created with only the endpoint present - This enables proper client creation for all three authentication methods: API key, managed identity, and APIM
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.
A logic bug in config.py prevents the content_safety_client from being created unless a content safety API key is present in the settings because the if condition required both the endpoint and the key before continuing to client creation:
simplechat/application/single_app/config.py
Line 648 in cebd8f7
This bugfix simply removes the "and safety_key" from the condition so the clients can be created properly whether the authentication uses API key, managed identity, or APIM.
Tested using the prompt from Microsoft's docs here: https://microsoft.github.io/TechExcel-Operationalize-LLMs-with-LLMOps-automation/docs/01_intro_to_llms/01_03.html#:~:text=and%20select%20Run-,Test,-.
Behavior before change:

Behavior after change:
