Set AppConfigurationAudience based on Cloud configuration when creating App Configuration SDK clients#2287
Merged
alzimmermsft merged 1 commit intomicrosoft:release/azure/2.xfrom Mar 30, 2026
Conversation
…ng App Configuration SDK clients (microsoft#2279) * Set AppConfigurationAudience based on Cloud configuration when creating App Configuration SDK clients * Pass tenant to credential retrieval * Fix method typo
alzimmermsft
requested review from
jongio,
saikoumudi,
sandeep-sen,
wbreza and
xiangyan99
and removed request for
a team
vcolin7
approved these changes
Mar 30, 2026
github-project-automation
Bot
moved this from Untriaged
to In Progress
in Azure MCP Server
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes App Configuration authentication in sovereign clouds by configuring the Azure App Configuration SDK client’s AppConfigurationAudience based on Azure MCP’s cloud configuration.
Changes:
- Pass tenant context through App Configuration store lookup and credential creation.
- Configure
ConfigurationClientOptions.Audiencebased on the configured cloud (Public/China/US Gov). - Add a changelog entry documenting the bug fix.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| tools/Azure.Mcp.Tools.AppConfig/src/Services/AppConfigService.cs | Sets ConfigurationClientOptions.Audience from cloud config and threads tenant through client creation/query. |
| servers/Azure.Mcp.Server/changelog-entries/1774886640626.yaml | Records the bug fix in the server changelog entry format. |
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.
What does this PR do?
Fixes authentication issues with App Configuration tools where they weren't setting
AppConfigurationAudiencebased on the cloud configuration of Azure MCP, resulting in a mismatch audience issue.Now all App Configuration SDKs have
AppConfigurationAudienceconfigured based on which cloud is being interacted with.GitHub issue number?
[Link to the GitHub issue this PR addresses]Pre-merge Checklist
servers/Azure.Mcp.Server/README.mdand/orservers/Fabric.Mcp.Server/README.mddocumentationREADME.mdchanges running the script./eng/scripts/Process-PackageReadMe.ps1. See Package READMEToolDescriptionEvaluatorand obtained a score of0.4or more and a top 3 ranking for all related test promptsconsolidated-tools.jsonbreaking-changelabelservers/Azure.Mcp.Server/docs/azmcp-commands.md./eng/scripts/Update-AzCommandsMetadata.ps1to update tool metadata inazmcp-commands.md(required for CI)servers/Azure.Mcp.Server/docs/e2eTestPrompts.mdcrypto mining, spam, data exfiltration, etc.)/azp run mcp - pullrequest - liveto run Live Test Pipeline