You need to add Fabrikam Inc.

PartsOps per-user authentication → OAuth 2.0; WarrantyRules shared team credential → API key; Tool-selection context → Configure a server description that explains the MCP server ' s role.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The authentication choices must follow the identity requirements of each server. PartsOps performs attributable actions, including parts-request creation, so OAuth 2.0 is the appropriate mechanism for individual users to authorize access without sharing their credentials with the agent. That preserves user context and supports accountability for each transaction. WarrantyRules is explicitly read-only and uses a key shared by the agent team; it should therefore be configured with API-key authentication using the required header or query parameter. Applying the same authentication method to both servers would contradict the stated server designs. Authentication alone does not tell the orchestrator when a server is relevant. A concise, discriminating server description should identify PartsOps as the source for availability checks and parts-request creation and WarrantyRules as the source for warranty validation. Copilot Studio uses the names and descriptions of agents, topics, tools, and knowledge sources during generative orchestration. Accurate metadata reduces accidental calls, prevents the wrong server from handling a request, and makes the multi-agent plan more predictable during testing. Study Guide alignment: Integrate and extend agents in Copilot Studio > Add tools to agents > Configure MCP tools.

===============