TSG: OAuth metadata discovery behind a reverse proxy#1972
Merged
anuchandy merged 1 commit intomicrosoft:mainfrom Mar 10, 2026
Merged
TSG: OAuth metadata discovery behind a reverse proxy#1972anuchandy merged 1 commit intomicrosoft:mainfrom
anuchandy merged 1 commit intomicrosoft:mainfrom
Conversation
anuchandy
requested review from
JasonYeMSFT,
chidozieononiwu,
hallipr,
jairmyree,
jongio,
sandeep-sen and
weshaggard
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a troubleshooting section to the Azure MCP Server's TROUBLESHOOTING.md documenting how to fix OAuth Protected Resource Metadata URL scheme issues when the server runs behind a TLS-terminating reverse proxy (e.g., Azure Container Apps). The fix involves setting the AZURE_MCP_DANGEROUSLY_ENABLE_FORWARDED_HEADERS=true environment variable.
Changes:
- Added a new "OAuth metadata discovery behind a reverse proxy" section under "Remote MCP Server (preview)" explaining the problem and the environment variable fix.
anuchandy
force-pushed
the
tsg-oauth-metadata-reverse-proxy
branch
from
668bd65 to
5166d55
Compare
g2vinay
approved these changes
Mar 9, 2026
github-project-automation
bot
moved this from Untriaged
to In Progress
in Azure MCP Server
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?
Add troubleshooting section for AZURE_MCP_DANGEROUSLY_ENABLE_FORWARDED_HEADERS to fix OAuth Protected Resource Metadata returning wrong-scheme URLs when the server is behind a TLS-terminating reverse proxy.
[Any additional context, screenshots, or information that helps reviewers]GitHub issue number?
[Link to the GitHub issue this PR addresses]Pre-merge Checklist
servers/Azure.Mcp.Server/CHANGELOG.mdand/orservers/Fabric.Mcp.Server/CHANGELOG.mdfor product changes (features, bug fixes, UI/UX, updated dependencies)servers/Azure.Mcp.Server/README.mdand/orservers/Fabric.Mcp.Server/README.mddocumentationeng/scripts/Process-PackageReadMe.ps1. See Package README/servers/Azure.Mcp.Server/docs/azmcp-commands.mdand/or/docs/fabric-commands.md.\eng\scripts\Update-AzCommandsMetadata.ps1to update tool metadata in azmcp-commands.md (required for CI)ToolDescriptionEvaluatorand obtained a score of0.4or more and a top 3 ranking for all related test promptsconsolidated-tools.json/servers/Azure.Mcp.Server/docs/e2eTestPrompts.mdcrypto mining, spam, data exfiltration, etc.)/azp run mcp - pullrequest - liveto run Live Test Pipeline