Repository navigation
Advertise Agent Identity authentication for Enterprise MCP - #263
Merged
Linda Li (lindazqli) merged 1 commit intoOct 13, 2026
Conversation
Keep OAuth passthrough and set the Enterprise MCP resource audience. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 252b43c2-7c23-4729-ab4f-5e59c59e46d0
Linda Li (lindazqli)
approved these changes
Oct 13, 2026
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.
Add
authSchemas: ["OAuth2", "AgentIdentity"]and setaudiencetoapi://e8c77dc2-69b3-43f4-bc51-3213c9d915b4in the Enterprise MCP catalog manifest. Keep the existing OAuth authorization-code configuration unchanged.This follows the registry schema and the existing Sentinel pattern for offering OAuth and Agent Identity together. The audience uses the Enterprise MCP resource identifier without
/.default.Scope: catalog metadata. End-to-end Agent User authentication still depends on Foundry acquiring a delegated Agent User token and Enterprise MCP accepting it. This change doesn't implement or verify that runtime exchange.
Validation: checked the changed manifest with
python -m check_jsonschema --schemafile partners\server-schema.json partners\servers\enterprise-mcp-server.jsonand rangit diff --check.