Skip to content

Commit af5d9ed

Browse files
committed
Clarify OAuth identity passthrough options for Functions-hosted MCP server and emphasize the use of custom OAuth with Microsoft Entra app registration
1 parent 994a009 commit af5d9ed

1 file changed

Lines changed: 2 additions & 5 deletions

File tree

articles/azure-functions/functions-mcp-foundry-tools.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -106,12 +106,9 @@ To get the Application ID URI from the Azure portal:
106106

107107
### [OAuth identity](#tab/oauth-id)
108108

109-
OAuth identity passthrough prompts users to sign in and authorize access to your MCP server. Foundry Agent Service supports two OAuth options:
109+
OAuth identity passthrough prompts users to sign in and authorize access to your MCP server. For a Functions-hosted MCP server with built-in authentication, use custom OAuth with a Microsoft Entra app registration.
110110

111-
- **Managed OAuth**: Microsoft or the MCP server publisher manages the OAuth app. No credential setup is required.
112-
- **Custom OAuth**: You bring your own OAuth app registration, which can be a Microsoft Entra app or any OAuth-compliant provider.
113-
114-
For a Functions-hosted MCP server with built-in authentication, use custom OAuth with a Microsoft Entra app registration. To get the required credentials from the Azure portal:
111+
To get the required credentials from the Azure portal:
115112

116113
1. Go to your function app resource in the [Azure portal](https://portal.azure.com).
117114

0 commit comments

Comments
 (0)